-
Notifications
You must be signed in to change notification settings - Fork 127
WIP: Add default network deletion to minikube start loop #1537
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
/test ? |
@Sunnatillo: 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. |
@Sunnatillo: 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. |
/test metal3-bml-integration-test-centos |
[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 metal3-dev-env-integration-test-centos-main |
6cf798b
to
d336d72
Compare
/test metal3-dev-env-integration-test-centos-main |
Signed-off-by: Sunnatillo <sunnat.samadov@est.tech>
d336d72
to
63d93f9
Compare
/test metal3-dev-env-integration-test-centos-main |
/test metal3-bml-integration-test-centos |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
No description provided.