Minor improvements

• fix: if a watch closes and fails to reconnect, exit the operator #395
• feat: make reconciliation thread number configurable #399

⚠️ Note that the spring-boot-auto-config sample module has been deactivated for this release as it's currently failing and needs to be fixed.

Minor improvements

• It's now possible to configure the ObjectMapper used by CustomResourceCache #384
• AbstractConfigurationService should now be easier to use by sub-classes #388

Dependencies update and improvements

• Use fabric8 kubernetes-client version 5.2.1.
• Make it possible to watch only the namespace in which the operator is deployed (without having to know its name beforehand) using @Controller(namespaces = Controller.WATCH_CURRENT_NAMESPACE) #372
• Make it possible to bypass CRD-based validation in Spring Boot applications #380

Quarkus extension has moved to the Quarkiverse!

See https://github.com/java-operator-sdk/java-operator-sdk#quarkus for more details.

Fix for OpenShift connection error

Fixes #365

Better OpenShift support, make some validation optional

See https://github.com/java-operator-sdk/java-operator-sdk#deactivating-customresource-implementations-validation for more details.

Updated to Quarkus 1.12.1 and Fabric8 client 5.1.1

Uses fabric8's kubernetes-client CRD generator. See https://github.com/java-operator-sdk/java-operator-sdk/blob/master/README.md#automatic-generation-of-crds for more details.

Updated to Quarkus 1.12.0 and Fabric8 client 5.1.0

• Updates to Quarkus extension
  Several improvements and fixes have been made to the Quarkus extension, most notably updating to Quarkus 1.12.0.
  Please take a look at the Quarkus migration guide https://github.com/quarkusio/quarkus/wiki/Migration-Guide-1.12 for details of changes brought about with the update (notably in how applications are now packaged).

• Update to Fabric8 kubernetes-client 5.1.0

• Switch to use the v1 CRD API

v1.7.1: Merge pull request #318 from java-operator-sdk/fixes

Features

• Quarkus extension now supports externalized configuration using application.properties.

Fixes

• Fixes #310
• Fixes #313
• Fixes #314
• Fixes #315
• Fixes #317
• All namespaces are watched by default and this behavior should now be consistently enforced across the SDK (#302)

Changes

• Integration tests are not run by default anymore, use all-tests profile to run all the tests
• It is now possible to override a controller's default configuration when registering it, using ControllerConfigurationOverrider. To make things consistent, only two versions of the register method have been kept, one using the controller (and its default configuration) and one using the controller with an associated overridden configuration.

v1.7.0: Merge pull request #288 from java-operator-sdk/client-v5

The 1.7.0 release updates to the 5.0.0 version of the fabric8 Kubernetes client. While this should improve the user experience quite nicely, there are a couple of things to be aware of when upgrading from a previous version as detailed below:

• Doneable classes have been removed along with all the involved complexity
• Controller annotation has been simplified: the crdName field has been removed as that value is
  computed from the associated custom resource implementation
• Custom Resource implementation classes now need to be annotated with Group and Version
  annotations so that they can be identified properly. Optionally, they can also be annotated with
  Kind (if the name of the implementation class doesn't match the desired kind) and Plural if
  the plural version cannot be automatically computed (or the default computed version doesn't match
  your expectations).
• The CustomResource class that needs to be extended is now parameterized with spec and status
  types, so you can have an empty default implementation that does what you'd expect. If you don't
  need a status, using Void for the associated type should work.
• Custom Resources that are namespace-scoped need to implement the Namespaced interface so that
  the client can generate the proper URLs. This means, in particular, that CustomResource
  implementations that do not implement Namespaced are considered cluster-scoped. As a
  consequence, the isClusterScoped method/field has been removed from the appropriate
  classes (Controller annotation, in particular) as this is now inferred from the CustomResource
  type associated with your Controller.

Many of these changes might not be immediately apparent but will result in 404 errors when
connecting to the cluster. Please check that the Custom Resource implementations are properly
annotated and that the value corresponds to your CRD manifest. If the namespace appear to be missing
in your request URL, don't forget that namespace-scoped Custom Resources need to implement
the Namescaped interface.