-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Consistent update for ObservedGeneration for ingress: update observed generation -> reconcile -> update status #5250
Consistent update for ObservedGeneration for ingress: update observed generation -> reconcile -> update status #5250
Conversation
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.
@taragu: 1 warning.
In response to this:
/lint
Part of #5076
Proposed Changes
- Update ingress ObservedGeneration before reconciling to indicate that we've attempted to reconcile its spec, and marking ingress as not ready if reconciliation fails
Release Note
NONE
/cc @jonjohnsonjr
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Hi @taragu. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
593867c
to
57c2f17
Compare
/ok-to-test |
The following jobs failed due to test flakiness:
Automatically retrying... |
… generation -> reconcile -> update status
57c2f17
to
b8dd98c
Compare
The following is the coverage report on pkg/.
|
@vagababov would you please take a look at this when you get a chance? |
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.
Why did we rearrange the events?
@vagababov the main rearrangement in this PR is when to update the observed generation. We want to update it first so that even if an error is encountered, we show that we've attempted to reconcile the spec (number 3 in #5076 (comment) ) |
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.
Ah, I see.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: taragu, vagababov 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 |
/test pull-knative-serving-integration-tests |
/lint
Part of #5076
Proposed Changes
Release Note
/cc @jonjohnsonjr