ci: Add bundle-sync verification to operator PR workflow - #6751
Open
ntkathole wants to merge 5 commits into
Open
ci: Add bundle-sync verification to operator PR workflow#6751ntkathole wants to merge 5 commits into
ntkathole wants to merge 5 commits into
Conversation
ntkathole
force-pushed
the
ci/operator-bundle-verify
branch
3 times, most recently
from
August 18, 2026 10:26
8ead3ee to
60b156e
Compare
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6751 +/- ##
=======================================
Coverage 46.96% 46.96%
=======================================
Files 418 418
Lines 51675 51675
Branches 7485 7485
=======================================
Hits 24268 24268
Misses 25673 25673
Partials 1734 1734
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
ntkathole
force-pushed
the
ci/operator-bundle-verify
branch
from
August 18, 2026 10:57
60b156e to
9b7201d
Compare
ntkathole
force-pushed
the
ci/operator-bundle-verify
branch
from
August 18, 2026 11:10
0946fe1 to
573bd48
Compare
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
Run `make bundle` to pick up refined clusterrole/clusterrolebinding RBAC rules and drop stale subjectaccessreviews permission. Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
ntkathole
force-pushed
the
ci/operator-bundle-verify
branch
from
August 18, 2026 15:44
573bd48 to
8df91f1
Compare
retry.RetryOnConflict only handles Conflict (resource version mismatch). When concurrent reconcile loops both GET a NotFound resource and race to Create it, the loser gets AlreadyExists which was not retried. Switch to retry.OnError with a predicate covering both IsConflict and IsAlreadyExists so the retry re-GETs the now-existing resource and proceeds with an update. Signed-off-by: ntkathole <nikhilkathole2683@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Run make bundle to pick up the clusterrole get/list RBAC verbs and updated CRD field descriptions. Signed-off-by: ntkathole <nikhilkathole2683@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
The controller-runtime cached client can return stale NotFound for cluster-scoped resources when the informer cache has not yet synced. This causes CreateOrUpdate to attempt a Create that fails with AlreadyExists. Retrying does not help because the cache remains stale during the short retry window. Treat AlreadyExists and Conflict as non-errors since the resource exists in the desired state. The next reconcile cycle will update its contents once the cache has synced. This follows the standard Kubernetes operator eventual-consistency pattern. Signed-off-by: ntkathole <nikhilkathole2683@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This adds a gate so future RBAC or kustomize changes that are not reflected in the CSV will be caught at PR time.