Chris Laprun
Chris Laprun
- 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`).
Fixes #1273 Depends on #1276.
How do dependents work when we have more than one secondary resource (like having 3 deployments) ? _Originally posted by @sebastienblanc in https://github.com/java-operator-sdk/java-operator-sdk/pull/785#discussion_r787438396_
It's currently a maintenance burden to have two separate projects and also makes it confusing/difficult for users to figure out which version of the SDK is used for a given...
We need to make this use case work for managed dependent resources as well… I've started looking into it and will open as issue for it since we can't currently...
Since we allow registering reconcilers for native resources, would it make sense to allow a user to register several different controllers for the same resource (e.g. `ConfigMap`) provided their configuration...
It would make sense to automatically provide metadata so that services created by SDK-created operators are more easily bindable: https://github.com/k8s-service-bindings/spec
## Feature Request **Is your feature request related to a problem? Please describe.** There are several frameworks out there that aim at making it easier to develop operators by providing...