Releases: operator-framework/java-operator-sdk
Releases · operator-framework/java-operator-sdk
Cleaner shutdown and dependency updates
- Add lifecycle hooks to EventSource #368
- Update to fabric8 kubernetes-client 5.3.1
Minor improvements
Minor improvements
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!
Fix for OpenShift connection error
Better OpenShift support, make some validation optional
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
v1CRD 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-testsprofile 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 theregistermethod have been kept, one using the controller (and its default configuration) and one using the controller with an associated overridden configuration.