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
IR-369,IR-370: support Azure workload identity #857
Conversation
@flavianmissi: This pull request references IR-369 which is a valid jira issue. In 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/test-infra repository. |
1 similar comment
@flavianmissi: This pull request references IR-369 which is a valid jira issue. In 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/test-infra repository. |
/retest |
@flavianmissi: This pull request references IR-369 which is a valid jira issue. This pull request references IR-370 which is a valid jira issue. In 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/test-infra repository. |
/retest |
1 similar comment
/retest |
I have now configured a cluster with workload identity and can confirm that this works 🎉 /assign @dmage |
/retest |
failure seems unrelated |
/test e2e-hypershift |
@flavianmissi: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In 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/test-infra repository. |
/retest |
@flavianmissi: This pull request references IR-369 which is a valid jira issue. This pull request references IR-370 which is a valid jira issue. In 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/test-infra repository. |
also add "Storage Blob Data Contributor" role, otherwise the registry does not have permission to do anything in the container.
we'll need to add an identation level, so get rid of an unnecessary one before doing that.
putting this on hold so we can merge it together with openshift/image-registry#372 |
/retest |
test failures seems unrelated |
/test e2e-aws-ovn-image-registry |
/cc |
/test e2e-ovirt-sdn |
@flavianmissi: The following test failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
This looks pretty solid. I am wondering if it should also be placed behind a featureGate like we did with the other operators. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flavianmissi, jstuever The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes in this PR are for interfacing with the CCO, they don't affect how end-users interact with the operator or the registry. /label docs-approved |
/label qe-approved |
/unhold |
Test with openshift/image-registry#372 and cco 523 pr. |
ee650f3
into
openshift:master
No description provided.