1.0.1

Bug Fixes

• fix(jvm): Integration do not shutdown gracefully when jvm.print-command is set (#1558, @astefanutti)
• Knative YAML integrations are now parsed correctly for metadata discovery (#1540, @lburgazzoli)
• Camel K 1.0.x can be now installed with kamel install on OLM-enabled clusters (#1527, @ipolyzos)
• fix: JVM trait overrides other traits JVM arguments (#1528, @astefanutti)

1.0.0

New Features

• camel-k supports OpenAPI v2 and v3
  rest-dsl trait has been renamed to openapi (#1330, @lburgazzoli)
• Add spectrum super-fast builder for dev clusters (#1306, @nicolaferraro)
• feat: Support Buildah builds on OpenShift with internal registry auto-configuration
  chore: Upgrade Buildah to version 1.14.0 (#1295, @astefanutti)
• Integrations can directly reference dependent projects on Github via Jitpack (#1491, @lburgazzoli)
• Added full support for Knative 0.14 (#1437, @nicolaferraro)
• Prometheus can be configured with a custom exporter config (#1397, @nicolaferraro)
• Modeline options can now be used to specify CLI flags directly in source files (#1455, @nicolaferraro)
• Camel K CLI is also available on homebrew and linuxbrew (#1454, @ipolyzos)
• Integrations now report a Ready condition in the status (#1438, @nicolaferraro)
• Added a tracing trait that automatically discovers Jaeger collectors (#1492, @nicolaferraro)
• Camel K Go APIs and clients are now two independent modules with no transitive dependencies (#1464, @nicolaferraro)
• Cron endpoints now work on the Quarkus runtime (#1460, @nicolaferraro)
• The 3scale trait can be used to inject 3scale API management annotations for auto-discovery (#1351, @nicolaferraro)
• Camel YAML/JSON DSL can now be inlined with the integration custom resource (#1472, @nicolaferraro)
• Only user-relevant CRDs are now shown in the OpenShift dev console (#1461, @nicolaferraro)
• Dynamic event types can be used when targeting the knative broker (#1458, @nicolaferraro)
• Builds are now much faster on Minikube (#1434, @nicolaferraro)
• Nighly build releases will be available from the release page from now on (#1373, @nicolaferraro)

Bug Fixes

• Improved stability of Knative services by removing code that interfered with Knative controllers (#1372, @nicolaferraro)
• Fixed permission issue about events patches that polluted the operator logs in RC2 (#1344, @nicolaferraro)
• Uninstall does no longer remove cluster-wide resources unless explicitly stated (#1378, @nicolaferraro)
• The Camel K operator can now manage Prometheus servicemonitors without requiring additional permissions (#1383, @nicolaferraro)
• Fixed issue in helm chart that prevented Camel K installation in multiple namespaces (#1448, @nicolaferraro)
• Redeployed integrations were keeping wrong information from previous runs (#1447, @nicolaferraro)
• fix: Prometheus scraping now works with Knative Serving (#1478, @astefanutti)

Other Notable Changes

• Upgrade Operator SDK to version 0.17.1 (#1482, @astefanutti)
• Switch to Java 11 as minimum java version
  Expose http services through the platform-http service (#1381, @lburgazzoli)
• CLI download links are now published after installing from operator Hub on OpenShift (#1380, @nicolaferraro)
• fix(jvm): Bind all interfaces to restore remote debugging with newer JDK versions (#1500, @astefanutti)
• feat: Add an option to print the JVM command in integration logs (#1496, @astefanutti)

Release 1.0.0-nightly.202005130003

Apache Camel K nightly build for testing (unstable).

To test it, download the client for your OS and run:

kamel install --olm=false --maven-repository=https://repository.apache.org/content/repositories/snapshots@id=apache-snapshots@snapshots

Release 1.0.0-nightly.202005060045

Apache Camel K nightly build for testing (unstable).

To test it, download the client for your OS and run:

kamel install --olm=false --maven-repository=https://repository.apache.org/content/repositories/snapshots@id=apache-snapshots@snapshots

Release 1.0.0-nightly.202004171040

Apache Camel K nightly build for testing (unstable).

To test it, download the client for your OS and run:

kamel install --olm=false --maven-repository=https://repository.apache.org/content/repositories/snapshots@id=apache-snapshots@snapshots

Release 1.0.0-nightly.202003261646

Apache Camel K nightly build for testing (unstable).

To test it, download the client for your OS and run:

kamel install --olm=false --maven-repository=https://repository.apache.org/content/repositories/snapshots@id=apache-snapshots@snapshots

1.0.0-RC2

New Features

• Property files can now be linked to the integration without manually creating an external configmap (#1244, @nicolaferraro)
• Periodic integrations are automatically translated into Kubernetes CronJobs (#1197, @nicolaferraro)
• Camel K 1.0.0-RC2 will be also available for install via Helm (#1287, @nicolaferraro)
• A kamel init command has been added to quickly scaffold integration files (e.g. kamel init Example.java) (#1219, @nicolaferraro)
• feat(jolokia): Support auto-configuration for OpenShift 4
  feat(jolokia): Automatically adds the camel-management dependency (#1193, @astefanutti)
• Camel master component is automatically configured to do leader election using Kubernetes resources (#1274, @nicolaferraro)
• feat: Support any Java base images (#1215, @astefanutti)
• feat(build): Buildah support (#1259, @astefanutti)
• Kubernetes events are generated to track the status of an integration (#1228, @nicolaferraro)
• The kamel install and run commands provide a --save flag to store the command line parameters to the default configuration file (#1217, @nicolaferraro)

Bug Fixes

• Some commands like kamel version threw an error if executed without connection to a cluster (#1241, @nicolaferraro)
• Fixed x509 certificate errors for Knative serving services on OpenShift (#1269, @nicolaferraro)

Other Notable Changes

• feat(trait): Unified JVM trait (#1226, @astefanutti)
• chore(dev): Upgrade Operator SDK to version 0.15.0 (#1224, @astefanutti)
• Operator is installed via OLM (Operator Lifecycle Manager) when available. (#1260, @nicolaferraro)
• Code rebased on Knative 0.12.x (#1271, @nicolaferraro)
• chore(build): Upgrade Kaniko to version 0.17.1 (#1253, @astefanutti)
• fix(install): Check permission to create OpenShift ConsoleCLIDownload resource (#1248, @astefanutti)
• fix(dev): Use go-homedir package instead of os/user to retrieve user home directory (#1211, @astefanutti)
• fix(jolokia): Order consistently Jolokia agent options when encoded as environment variable (#1198, @astefanutti)

1.0.0-RC1

New Features

• Added support for pushing images to authenticated external docker registries (such as Docker Hub or Github Packages) (#1084, @nicolaferraro)
• IntegrationPlatform specification does no longer contain default values in order to ease upgrades (#1127, @nicolaferraro)
• All traits are automatically documented on the Camel K website (see https://camel.apache.org/camel-k/latest/) (#1068, @nicolaferraro)
• feat(build): Task-based builds
  fix(build): Use EmptyDir volumes for Kaniko builds when caching is disabled
  fix(build): Disable Kaniko cache by default (#1121, @astefanutti)
• If an integration platform is not provided, a default one will be created whenever possible (OpenShift) (#1117, @nicolaferraro)
• Default values for the kamel CLI can now be configured through a configuration file and/or environment variables. (#1133, @lburgazzoli)
• Camel K Kubernetes Custom Resource APIs promoted to "v1" (#1160, @nicolaferraro)

Bug Fixes

• Knative profile detection has been deferred to when the integration runs, in order to allow Camel K and Knative to be installed in any order (#1151, @nicolaferraro)

Other Notable Changes

• fix(OpenAPI): Use catalog runtime version to generate OpenAPI project (#1096, @astefanutti)
• Upgrade Operator SDK to version 0.13.0 (#1153, @astefanutti)
• Use JSON merge patch to reconcile Camel K custom resource statuses (#1110, @astefanutti)
• Better report build progress (#1064, @astefanutti)
• Support for Knative 0.9+ (codebase compiled with Knative 0.10.0 API). Dropped compatibility with Knative 0.8.x. (#1123, @nicolaferraro)
• feat: Generic patching of integration resources in running phase (#1100, @astefanutti)
• Upgrade to Camel K Runtime 1.0.9
  Upgrade to Camel Quarkus 1.0.0-M1
  Upgrade to Kaniko 0.14.0 (#1167, @nicolaferraro)

1.0.0-M4

New Features

• A Go client for interacting with Camel K Kubernetes resources is now available (#1051, @nicolaferraro)
• Initial Quarkus support (JVM mode) (#1013, @astefanutti)

Bug Fixes

• Fixed "kamel" CLI to authenticate via user credentials, if available, in containerized IDEs (#1054, @nicolaferraro)

Other Notable Changes

• Remove support for loading compiled java classes (#1052, @lburgazzoli)
• Upgrade Operator SDK to version 0.12.0 (#1043, @astefanutti)
• Report runtime version from Camel catalog into integration and kit statuses (#1044, @astefanutti)
• chore(dev): Require Go version 1.13 (#1040, @astefanutti)

1.0.0-M3

New Features

• Added support for Knative Broker/Trigger model and explicit source/sink selection (#1012, @nicolaferraro)
• Integration custom resource allows to specify the runtime loader to use for each source (#1007, @nicolaferraro)

Bug Fixes

• Knative permissions are now correctly configured when the operator is in global mode (#1019, @nicolaferraro)
• Do not install default integration platform when --global option is set
  Fix Kaniko cache warmer multi-tenancy per namespace (#992, @astefanutti)

Other Notable Changes

• Upgrade Operator SDK to version 0.11.0 (#1017, @astefanutti)
• Handle traits update conflicts to integration owned resources gracefully (#1000, @astefanutti)
• Auto cross-compile operator image binary from non-Linux local OS (#987, @astefanutti)
• fix: Avoid updating Deployment replicas in default configuration (#1003, @astefanutti)
• perf: Enqueue ReplicaSet updates only when replicas changed (#1002, @astefanutti)