We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe.
This is the same as #710, but for the operator itself instead of tenants.
Currently kubectl minio delete asks for confirmation; implement a flag --force to avoid interactive behavior.
kubectl minio delete
--force
Describe the solution you'd like
kubectl minio delete --force
Describe alternatives you've considered Skip deleting my operator in tests and just let it be destroyed when the cluster is removed.
Additional context For scripts, tests, or other non-interactive use.
The text was updated successfully, but these errors were encountered:
I was reviewing this change to explain or help Abdul with this task and found that the solution can be found here: https://github.com/minio/operator/pull/711/files
Sorry, something went wrong.
Similar code will apply not just for the tenant but for the Operator as well:
Now to test the code change, we can look at Pedro's notes at: #1612
r-scheele
No branches or pull requests
Is your feature request related to a problem? Please describe.
This is the same as #710, but for the operator itself instead of tenants.
Currently
kubectl minio delete
asks for confirmation; implement a flag--force
to avoid interactive behavior.Describe the solution you'd like
kubectl minio delete --force
Describe alternatives you've considered
Skip deleting my operator in tests and just let it be destroyed when the cluster is removed.
Additional context
For scripts, tests, or other non-interactive use.
The text was updated successfully, but these errors were encountered: