-
Notifications
You must be signed in to change notification settings - Fork 667
OCPBUGS-61183: cluster in workload identity mode is not applied with the token-auth-… #15459
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
OCPBUGS-61183: cluster in workload identity mode is not applied with the token-auth-… #15459
Conversation
|
@cajieh: This pull request references Jira Issue OCPBUGS-61183, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
c5e8fab to
e64ba92
Compare
|
/jira refresh |
|
@cajieh: This pull request references Jira Issue OCPBUGS-61183, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
29ca6a1 to
cfdad13
Compare
5fac09b to
d4af0ee
Compare
| GridItem, | ||
| Radio, | ||
| Stack, | ||
| StackItem, |
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.
Added these PF components to fix a margin issue, likely a regression from the recent Operator Hub changes. Although this was not part of the bug ticket.
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.
A <Stack> with a single <StackItem> is a bit overkill to fix a margin issue. Simply adding a className="pf-v6-u-mb-md" to each <DismissableAlert> is a bit simpler.
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.
Actually, I used the PF class at first but later changed to Stack based on previous feedback that discouraged the use of classes, although that work was more complex than this. I will go with your opinion.
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 DismissableAlert was missing a className prop, so I added it to prevent the need for a wrapping div.
d4af0ee to
64112b5
Compare
| setTokenizedAuth('Azure'); | ||
| } else if (clusterIsGCPWIF) { | ||
| setTokenizedAuth('GCP'); | ||
| } |
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.
Could create a map of providers and use the .find() method to identify the first function that returns true, but I didn't see a need for it at this time. I might be wrong.
|
/test okd-scos-e2e-aws-ovn |
|
/verified later @yapei |
|
@cajieh: This PR has been marked to be verified later by DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
64112b5 to
d29415f
Compare
d29415f to
c054364
Compare
rhamilto
left a comment
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.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cajieh, rhamilto, sg00dwin The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified later @yapei |
|
/retest |
|
@cajieh: This PR has been marked to be verified later by DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@cajieh: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
@cajieh: Jira Issue OCPBUGS-61183: All pull requests linked via external trackers have merged: This pull request has the DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/cherry-pick release-4.20 |
|
@cajieh: new pull request created: #15507 DetailsIn 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-sigs/prow repository. |
|
Fix included in accepted release 4.21.0-0.nightly-2025-09-13-162334 |
|
/cherry-pick release-4.19 |
|
@cajieh: #15459 failed to apply on top of branch "release-4.19": DetailsIn 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-sigs/prow repository. |
|
Oh, it appears this regression was introduced in 4.20, but the target version in the ticket is 4.17. I couldn't reproduce the issue in versions 4.19 or older, and I believe @yapei couldn't either, correct? |
…azure annotation