-
Notifications
You must be signed in to change notification settings - Fork 567
OCPBUGS-34027: Fix cleanup of orphaned OIDC resources in guest cluster #7143
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
Closed
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
1fe0ad9
fix(hcco): cleanup orphaned OIDC resources when config is removed
bryan-cox 6003474
fix(hcco): prevent OIDC resource cleanup race condition
bryan-cox a448d9c
fix(globalconfig): clear Authentication spec when OIDC config is removed
bryan-cox 68494f3
fix(OCPBUGS-34027): Explicitly set IntegratedOAuth type when removing…
bryan-cox 2041250
test(globalconfig): add unit tests for Authentication reconciliation
bryan-cox 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
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.
🧩 Analysis chain
Verify backward compatibility for unlabeled resources.
The tracking and labeling logic correctly marks resources during reconciliation. However, the PR description states: "resources created before this change may lack the managed label but can be cleaned up via name matching."
The current implementation only cleans up resources with the
OIDCProviderManagedLabel(see lines 1371-1372, 1389-1390 usingclient.HasLabels{OIDCProviderManagedLabel}). Resources created before this change won't be found by the label selector unless they're reconciled first.Scenario to consider:
Run this script to check if there's any name-based cleanup logic for backward compatibility:
Also applies to: 1253-1253, 1270-1274, 1287-1287, 1309-1313, 1325-1327
🏁 Script executed:
Length of output: 19279
The web search wasn't helpful for this specific code context. I need to look at the codebase directly to understand how the expectedConfigMaps and expectedSecrets sets are used.
Actually, let me get the correct line ranges:
Length of output: 0
🏁 Script executed:
Length of output: 0
🏁 Script executed:
Length of output: 3862
Length of output: 3622
Backward compatibility gap confirmed: cleanup only finds labeled resources.
The implementation only cleans up resources that have the
OIDCProviderManagedLabellabel (lines 1371, 1389). Resources created before this change won't have the label and won't be found by theclient.HasLabelsfilters, leaving them orphaned.The cleanup logic never performs name-based matching as mentioned in the PR description. If OIDC config is removed before old resources are reconciled and labeled:
List()withclient.HasLabels{OIDCProviderManagedLabel}won't find themConsider adding either a fallback name-based lookup or a migration mechanism to label existing resources on first reconciliation.
🤖 Prompt for AI Agents