Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Camel K 1.0.0 #1498

Closed
nicolaferraro opened this issue Jun 5, 2020 · 1 comment
Closed

Release Camel K 1.0.0 #1498

nicolaferraro opened this issue Jun 5, 2020 · 1 comment
Milestone

Comments

@nicolaferraro
Copy link
Member

Trying to cut a release today after merging the pending PRs.

@nicolaferraro nicolaferraro added this to the 1.0.0 milestone Jun 5, 2020
@nicolaferraro
Copy link
Member Author

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant