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.

Quarkus extension improvements

Merge pull request #297 from java-operator-sdk/native-compilation

Native compilation improvements

Quarkus extension and Spring Boot test support improvements

Merge pull request #290 from java-operator-sdk/timertestfix

Increase test timer slack time to make test not fail

Addresses a crasher with the Quarkus extension

Merge pull request #265 from java-operator-sdk/fix-264

Fixes #264

Initial Quarkus extension

This release re-organized the way the code is structured to provide a Quarkus extension called operator-framework-quarkus-extension.

It also initiates changes in the way configuration of controllers are defined, with the possibility of externalizing configuration (not completely implemented yet).

Finally, it renames the Spring Boot starter to operator-framework-spring-boot-starter to conform to Spring Boot's conventions.

v1.5.0

Updates:

• Retry functionality: #252
• Various other improvements

v1.4.0

This release contains fundamental changes to the framework:

• Introducing Event Sources: re-worked core to support watching resources (other than custom resource) in an extensible way
• Improvements on Quarkus support
• We dropped java 8 support (minimal version is now java 11)

See also:

• #188
• #232

v1.3.0

This is a quite big release, what contains also API changes. The most important improvements are:

• Support for status sub-resource updates: https://github.com/ContainerSolutions/java-operator-sdk/issues/93
• Provides a better API for retry state
• We add finalizer before executing the controller method

Fixes also issues like:

• https://github.com/ContainerSolutions/java-operator-sdk/issues/136
• The scheduling algorithm became much simpler by handling generations differently

This release includes new package name and artifact group id

v1.2.3

• This is a service release, updated versions of dependencies.
• Mainly openshift-client to 4.10.2