-
Notifications
You must be signed in to change notification settings - Fork 192
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
NE-1244: Use permissions instead of the "Contributor" role in Azure CredentialsRequest #929
Conversation
@Miciah: This pull request references NE-1244 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. |
/test e2e-azure-operator |
Skipping CI for Draft Pull Request. |
e2e-azure-operator failed on |
@abutcher, is this sufficiently fine-grained to satisfy the requirements of the epic?
|
@Miciah Yeah, I think this will be sufficiently fine grained. Azure e2e is currently |
c468b1d
to
6330929
Compare
@Miciah: This pull request references NE-1244 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. |
/test e2e-azure-operator |
e2e-azure-operator failed because
I don't think I've seen this failure before. At the same time, I don't see how the changes in this PR could cause it. |
I think the bot missed my previous comment. |
6330929
to
2a198b1
Compare
Rebased for #900. |
Instead of requesting the "Contributor" role, request the individual permissions that the operator requires in order to manage DNS records on Azure. This commit resolves NE-1244. https://issues.redhat.com/browse/NE-1244 * manifests/00-ingress-credentials-request.yaml: Replace the "Contributor" role with a list of permissions.
2a198b1
to
162f14c
Compare
Rebased for #905. /test e2e-azure-operator |
@Miciah: This pull request references NE-1244 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. |
/test e2e-azure-manual-oidc |
@Miciah: This pull request references NE-1244 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. |
A custom role was created during credentials provisioning:
Ingress operator pod logs from the test are here. I noticed we kicked off an |
Excellent!
The e2e-azure-manual-oidc job suffices in my opinion. The operator logs show that the operator succeeded in both creating and deleting DNS records, in both the public and private zones. We only use one record type on Azure (namely type A), so there isn't much variation in what the operator does on Azure as far as DNS is concerned. |
/assign |
@candita - can you wrap this up today? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: candita 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 |
@Miciah followup question asked in slack. |
e2e-aws-operator failed with a lot of test failures: It appears that AWS did not enforce the 3-second idle timeout that The The other tests appear to have failed because they were pulling the "openshift/origin-node" image from Docker Hub. I filed OCPBUGS-17359 and posted #970 to address that issue. |
Hi @newtonheath - the hold is on CI failures right now. |
/test e2e-hypershift |
@Miciah: The following tests 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. |
/test e2e-hypershift |
Instead of requesting the "Contributor" role, request the individual permissions that the operator requires in order to manage DNS records on Azure.
manifests/00-ingress-credentials-request.yaml
: Replace the "Contributor" role with a list of permissions.Notes for reviewers: Per discussions on NE-1244, this PR restricts the CredentialsRequest for Azure to a specific set of permissions. Because of the way the e2e-azure-operator job is configured, this job doesn't actually use the precise rules or permissions that are listed in the CredentialsRequest, but the e2e-azure-manual-oidc job that was added by openshift/release#41502 does.