java-operator-sdk
java-operator-sdk copied to clipboard
Java SDK for building Kubernetes Operators
- fix: grammar - refactor: clean up WorkflowReconcileResult - refactor: make it easier to create Conditions
More specifically annotations and labels should be checked since the rest of the fields are either irrelevant (e.g. `name`) or not under a user's control (e.g. `managedFields`).
The json mapper might be fine tuned for application in some cases, probably in the default case we should use that everywhere if possible. see also: https://github.com/fabric8io/kubernetes-client/issues/1308
IMO these are pretty obsolete (at least I did not open them for a very long time)
Fixes #1273 Depends on #1276.
Workflows are essentially acyclic, detecting cycles is already implemented in PR: https://github.com/java-operator-sdk/java-operator-sdk/pull/1257 However this approach does not log the detected cycle - just logs that "there is a cycle" -...
ADRs are highly beneficial for making and documenting complex architectural decisions.
Currently informers and other provided event source implementations cache all the received resources. This could lead to very high memory consumption. In that case what could be done is limit...
Provides alternative methods for update control to check if the resource and/or status sub-resource actually changed, and do the requests just in that case.