Skip to content
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

Allow non-interactive way to delete the operator using kubectl plugin #1683

Closed
thomasjm opened this issue Jul 13, 2023 · 3 comments
Closed
Assignees
Labels
community enhancement New feature or request

Comments

@thomasjm
Copy link

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.

@pjuarezd pjuarezd added enhancement New feature or request and removed triage labels Jul 13, 2023
@cniackz
Copy link
Contributor

cniackz commented Jul 14, 2023

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

@cniackz
Copy link
Contributor

cniackz commented Jul 14, 2023

Similar code will apply not just for the tenant but for the Operator as well:

Screenshot 2023-07-14 at 8 46 08 AM

@cniackz
Copy link
Contributor

cniackz commented Jul 14, 2023

Now to test the code change, we can look at Pedro's notes at: #1612

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants