-
Notifications
You must be signed in to change notification settings - Fork 83
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
Fixed reconcile running on all KIngress after ksvc deletion #1159
Fixed reconcile running on all KIngress after ksvc deletion #1159
Conversation
Hi @ryutoyasugi. Thanks for your PR. I'm waiting for a knative-extensions 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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1159 +/- ##
=======================================
Coverage 80.81% 80.81%
=======================================
Files 18 18
Lines 1392 1392
=======================================
Hits 1125 1125
Misses 213 213
Partials 54 54 ☔ View full report in Codecov by Sentry. |
// Force reconcile all Kourier ingresses that are either not reconciled yet | ||
// (and thus might end up in a conflict) or already in conflict. | ||
return isKourierIngress(obj) && (lbReady == "" || lbReady == conflictReason) | ||
return isKourierIngress(obj) && (lbReady == nil || lbReady.GetReason() == conflictReason) |
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.
Given that:
func (c *Condition) GetReason() string {
if c == nil {
return ""
}
return c.Reason
}
Ingresses that have condition(LBReady) that is not nil, do have Reason "" and match all the reconciled ones correct?
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.
Yes, for successfully working ingresses, the condition(LBReady) is not nil and the Reason is empty.
/ok-to-test |
I tested it locally with conflicting dms, stamping it. |
/cherry-pick release-1.12 |
@skonto: once the present PR merges, I will cherry-pick it on top of release-1.12 in a new PR and assign it to you. In response to this:
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ryutoyasugi, skonto 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 |
@skonto: new pull request created: #1170 In response to this:
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. |
Why
I found Reconcile running on all KIngress after ksvc was removed.
The same problem has been reported. #941
Changes
Fixed conditions under which
resyncConflicts
are executed.https://github.com/knative-extensions/net-kourier/blob/cbd0d74/pkg/reconciler/ingress/ingress.go#L135
Related PR
#502, #486