Skip to content
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

Merged

Conversation

taragu
Copy link
Contributor

@taragu taragu commented Aug 22, 2019

/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

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Aug 22, 2019
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 22, 2019
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a 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.

@knative-prow-robot knative-prow-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 22, 2019
@knative-prow-robot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@knative-prow-robot knative-prow-robot added area/API API objects and controllers area/networking labels Aug 22, 2019
@taragu taragu force-pushed the ingress-reconcile-observed-gen branch from 593867c to 57c2f17 Compare August 22, 2019 19:33
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 22, 2019
@taragu
Copy link
Contributor Author

taragu commented Aug 26, 2019

/ok-to-test

@knative-prow-robot knative-prow-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 26, 2019
@knative-test-reporter-robot

The following jobs failed due to test flakiness:

Test name Triggers Retries
pull-knative-serving-integration-tests pull-knative-serving-integration-tests 1/3

Automatically retrying...
/test pull-knative-serving-integration-tests

@taragu taragu force-pushed the ingress-reconcile-observed-gen branch from 57c2f17 to b8dd98c Compare August 26, 2019 16:21
@knative-metrics-robot
Copy link

The following is the coverage report on pkg/.
Say /test pull-knative-serving-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/networking/v1alpha1/ingress_lifecycle.go 92.3% 92.9% 0.5
pkg/reconciler/route/route.go 83.7% 84.2% 0.5

@taragu
Copy link
Contributor Author

taragu commented Aug 30, 2019

@vagababov would you please take a look at this when you get a chance?

Copy link
Contributor

@vagababov vagababov left a 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?

@taragu
Copy link
Contributor Author

taragu commented Sep 3, 2019

@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) )

Copy link
Contributor

@vagababov vagababov left a 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

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2019
@knative-prow-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 3, 2019
@taragu
Copy link
Contributor Author

taragu commented Sep 3, 2019

/test pull-knative-serving-integration-tests

@knative-prow-robot knative-prow-robot merged commit 465f368 into knative:master Sep 3, 2019
@taragu taragu deleted the ingress-reconcile-observed-gen branch February 18, 2020 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/API API objects and controllers area/networking cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants