-
Notifications
You must be signed in to change notification settings - Fork 216
do not merge, vsphere privilege logging #1384
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
base: main
Are you sure you want to change the base?
Conversation
our continued issue determining what privelges are required for components
Skipping CI for Draft Pull Request. |
/test ? |
@jcpowermac: The following commands are available to trigger required jobs:
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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test e2e-vsphere-ovn |
/test e2e-vsphere-ovn |
2 similar comments
/test e2e-vsphere-ovn |
/test e2e-vsphere-ovn |
f833d5f
to
49817b1
Compare
/test e2e-vsphere-ovn |
1 similar comment
/test e2e-vsphere-ovn |
49817b1
to
50b5201
Compare
/test e2e-vsphere-ovn |
@jcpowermac: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
our continued issue determining what privileges are required for components