nicolaferraro commented on issue #1273: Release 1.0.0-RC2
URL: https://github.com/apache/camel-k/issues/1273#issuecomment-590474155
 
 
   ## New Features
   
   - Property files can now be linked to the integration without manually 
creating an external configmap 
([#1244](https://github.com/apache/camel-k/pull/1244), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - Periodic integrations are automatically translated into Kubernetes 
CronJobs ([#1197](https://github.com/apache/camel-k/pull/1197), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - Camel K 1.0.0-RC2 will be also available for install via Helm 
([#1287](https://github.com/apache/camel-k/pull/1287), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - A kamel init command has been added to quickly scaffold integration files 
(e.g. kamel init Example.java) 
([#1219](https://github.com/apache/camel-k/pull/1219), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - feat(jolokia): Support auto-configuration for OpenShift 4
     feat(jolokia): Automatically adds the camel-management dependency 
([#1193](https://github.com/apache/camel-k/pull/1193), 
[@astefanutti](https://github.com/astefanutti))
   - Camel master component is automatically configured to do leader election 
using Kubernetes resources 
([#1274](https://github.com/apache/camel-k/pull/1274), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - feat: Support any Java base images 
([#1215](https://github.com/apache/camel-k/pull/1215), 
[@astefanutti](https://github.com/astefanutti))
   - feat(build): Buildah support 
([#1259](https://github.com/apache/camel-k/pull/1259), 
[@astefanutti](https://github.com/astefanutti))
   - Kubernetes events are generated to track the status of an integration 
([#1228](https://github.com/apache/camel-k/pull/1228), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - The kamel install and run commands provide a --save flag to store the 
command line parameters to the default configuration file 
([#1217](https://github.com/apache/camel-k/pull/1217), 
[@nicolaferraro](https://github.com/nicolaferraro))
   
   ## Bug Fixes
   
   - Some commands like `kamel version` threw an error if executed without 
connection to a cluster ([#1241](https://github.com/apache/camel-k/pull/1241), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - Fixed x509 certificate errors for Knative serving services on OpenShift 
([#1269](https://github.com/apache/camel-k/pull/1269), 
[@nicolaferraro](https://github.com/nicolaferraro))
   
   
   
   ## Other Notable Changes
   
   - feat(trait): Unified JVM trait 
([#1226](https://github.com/apache/camel-k/pull/1226), 
[@astefanutti](https://github.com/astefanutti))
   - chore(dev): Upgrade Operator SDK to version 0.15.0 
([#1224](https://github.com/apache/camel-k/pull/1224), 
[@astefanutti](https://github.com/astefanutti))
   - Operator is installed via OLM (Operator Lifecycle Manager) when available. 
([#1260](https://github.com/apache/camel-k/pull/1260), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - Code rebased on Knative 0.12.x 
([#1271](https://github.com/apache/camel-k/pull/1271), 
[@nicolaferraro](https://github.com/nicolaferraro))
   - chore(build): Upgrade Kaniko to version 0.17.1 
([#1253](https://github.com/apache/camel-k/pull/1253), 
[@astefanutti](https://github.com/astefanutti))
   - fix(install): Check permission to create OpenShift ConsoleCLIDownload 
resource ([#1248](https://github.com/apache/camel-k/pull/1248), 
[@astefanutti](https://github.com/astefanutti))
   - fix(dev): Use go-homedir package instead of os/user to retrieve user home 
directory ([#1211](https://github.com/apache/camel-k/pull/1211), 
[@astefanutti](https://github.com/astefanutti))
   - fix(jolokia): Order consistently Jolokia agent options when encoded as 
environment variable ([#1198](https://github.com/apache/camel-k/pull/1198), 
[@astefanutti](https://github.com/astefanutti))
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to