This release marks the deprecation of the upstream @fabric8io Maven Plugin, please migrate your current applications [2].
JKube is the successor to the deprecated Fabric8 Maven Plugin, please check our migration guide [2] if you come from FMP.
This release marks the deprecation of the upstream project [3].
Using this release:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>kubernetes-maven-plugin</artifactId>
<version>1.0.0</version
</plugin>
(Check Maven Central [1] for the rest of artifacts)
These are the features and fixes included in 1.0.0:
- Fix #351: Fix AutoTLSEnricher - add annotation + volume config to resource [4]
- Fix #344: Fix documentation for `jkube.openshift.imageChangeTriggers` [5]
- Fix #290: Bump Fabric8 Kubernetes Client to v4.10.3 [6]
- Fix #273: Added new parameter to allow for custom _app_ name [7]
- Fix #329: Vert.x generator and enricher applicable when `io.vertx` dependencies present [8]
- Fix #334: Build strategy picked up from XML configuration and properties [9]
- Fix #342: Maven Quickstart for Spring-Boot with complete Camel integration [10]
- Fix #336: Fix pull from insecure registries and pull registry authentication for JIB [11]
- Fix #332: OpenShift build resources are deleted (as long as build config manifest is available) [12]
- Fix #350: Prevents default docker configuration overwriting XML assembly configuration [13]
- Fix #340: Exclude the main artifact from Docker build when Fat Jar is detected (JavaExecGenerator) [14]
- Fix #341: JKube doesn't add ImageChange triggers in DC when merging from a deployment fragment [15]
- Fix #326: Add default `/metrics` path for `
prometheus.io/path` annotation [16]
(Sort of [redundant](
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config), this makes it explicit)
- Fix #339: Https should be considered default while converting tcp urls [17]
- Fix #362: Quarkus supports S2I builds both for JVM and native mode [18]
- Fix #297: Added missing documentation for WatchMojo configuration parameters [19]
- Fix #371: WebAppGenerator path configuration is no longer ignored [20]
