-
-
Notifications
You must be signed in to change notification settings - Fork 1
refactor: Extract apply and update status steps #856
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
Open
adwk67
wants to merge
11
commits into
main
Choose a base branch
from
feat/smooth-operator/extract-apply-step
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 8 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
5550570
move object_meta into the build step
adwk67 0be4475
derive the version label instead of hardcoding the dev suffix
adwk67 8633b62
extract apply and update_status steps
adwk67 63fbf22
look up the applied Router listener declaratively
adwk67 f36566d
clean-up
adwk67 1ad652a
changelog
adwk67 0312b55
added listener look-up test, minor improvements
adwk67 e112e2c
destructure the resources exhaustively in apply()
adwk67 5e6d481
include listener in dereferencing step so that its status/addresses c…
adwk67 dfb0d29
Merge branch 'main' into feat/smooth-operator/extract-apply-step
adwk67 173a9d0
add debug statement for CM miss
adwk67 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
The discovery ConfigMap should be built in the build step, where it belongs.
The current comment is also inaccurate. It claims the discovery ConfigMap can be built from the applied Listener object, but what actually happens is:
▎ failed to build discovery ConfigMap, failed to configure listener discovery configmap, router listener has no adress [sic]
Instead, we can simply:
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.
It must eventually converge otherwise the smoke test would not work (but, yes, we emit a few unecessary ERRORs until that happens). And the fact that we error out of the reconcile means it gets triggered again, whereas if we just miss out the ConfigMap when there is no status, there is no guarantee it gets retriggered unless we watch listeners, too. So should we add a watch on listeners (with an RBAC change, too), or return a short requeue if the status is not yet available?
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.
I would watch the Listeners. When the discovery ConfigMap is properly integrated into the controller steps then a lot of code can be removed that handled this special case.
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.
See 5e6d481 and 173a9d0.
Re-tested: