-
Notifications
You must be signed in to change notification settings - Fork 104
NE-2743: Support centralized TLS security profiles for CDO metrics #482
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
Merged
openshift-merge-bot
merged 6 commits into
openshift:master
from
Thealisyed:bump-to-4.22
Jul 21, 2026
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a91d2ca
NE-2743: Vendor openshift/api and bump dependencies
Thealisyed 4c34182
NE-2743: Align static operator deployment ciphers with Intermediate T…
Thealisyed 669cf57
NE-2743: Sync CRD manifests with vendored openshift/api
Thealisyed d060e74
NE-2743: Replace kube-rbac-proxy with direct TLS serving for operator…
Thealisyed 98f0b49
NE-2743: Log warning for unsupported TLS groups instead of silently s…
Thealisyed d4368ad
Address Davide's review feedback
Thealisyed File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
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.
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.
While this static loading behavior is historically common in
controller-runtimeoperators, it does introduce a subtle asymmetry in our design:9393until a manual restart or node reschedule occurs.Across the OpenShift ecosystem, we have a standardized pattern to solve this exact dynamic update limitation. Instead of attempting to hot-reload TLS parameters (which can lead to inconsistent states on long-lived connections), operators use a
SecurityProfileWatcherfrom theopenshift/controller-runtime-commonlibrary to trigger a graceful self-shutdown when the TLS profile changes. Because the operator's Deployment hasrestartPolicy: Always, Kubernetes instantly spawns a new pod, which re-reads the fresh TLS config on boot.You can see an example of this in the ptp-operator main.go.
This is definitely a separate, well-defined enhancement that doesn't need to block this PR. Let's merge this work as-is to unblock the
kube-rbac-proxyremoval, and we can track implementing theSecurityProfileWatcherin a follow-up Jira story. What do you think?I think we should add a Jira to track this and do this as a follow-up PR.