-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ObservedGeneration to the sub Resources #291
Add ObservedGeneration to the sub Resources #291
Conversation
e4b0d30
to
7891792
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
other than the debate about <= and == this looks good
This patch does a few things: 1. it adds observedGeneration to the sub custom resources 2. it proposes to bump the observedGeneration at the beginning of the reconciliation loop (knative/serving#4937) 3. it checks, at the top level, if the ObservedGeneration matches with the metadata.generation assigned to the subCR(s), and if it's the last version it mirrors the Conditions 4. before marking the DeploymentReadyCondition as True, the ObservedGeneration is compared with the Generation of the Deployment/DaemonSets Signed-off-by: Francesco Pantano <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fmount, gibizer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
fc90a6f
into
openstack-k8s-operators:main
This patch does a few things:
it adds observedGeneration to the sub custom resources
it proposes to bump the observedGeneration at the beginning of the reconciliation loop (metadata.observedGeneration behaves differently across CRDs knative/serving#4937)
it checks, at the top level, if the ObservedGeneration matches with the metadata.generation assigned to the subCR(s)
before marking the DeploymentReadyCondition as True, the ObservedGeneration is compared with the Generation of the Deployment/DaemonSets