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

Should 'kamel uninstall --all' also delete camel-k-registry-secret? #1859

Closed
tadayosi opened this issue Dec 11, 2020 · 3 comments
Closed

Should 'kamel uninstall --all' also delete camel-k-registry-secret? #1859

tadayosi opened this issue Dec 11, 2020 · 3 comments

Comments

@tadayosi
Copy link
Member

Currently kamel uninstall --all doesn't delete camel-k-registry-secret if it was generated with kamel install --registry ....

$ kamel uninstall --all 
Camel K Integration Platform removed from namespace default
Camel K Config Maps removed from namespace default
Camel K Operator removed from namespace default
Camel K Role Bindings removed from namespace default
Camel K Roles removed from namespace default
Camel K Service Accounts removed from namespace default
Camel K Custom Resource Definitions removed from cluster
Camel K Cluster Role Bindings removed from cluster
Camel K Cluster Roles removed from cluster

$ kubectl get secrets 
NAME                      TYPE                                  DATA   AGE
camel-k-registry-secret   kubernetes.io/dockerconfigjson        1      14h
default-token-48wb7       kubernetes.io/service-account-token   3      178d
...

Maybe it should remove the registry and also provide an option --skip-registry for users who don't want it to be removed.

@nicolaferraro
Copy link
Member

Yes, sounds good, I think we add some labels to detect if it's generated by us, btw that name is usually used only by our CLI

@tadayosi
Copy link
Member Author

@nicolaferraro Thanks. So maybe should we add a label app=camel-k for the generated secret and clean up them if they have the label under uninstalling?

tadayosi added a commit to tadayosi/camel-k that referenced this issue Dec 14, 2020
tadayosi added a commit that referenced this issue Dec 16, 2020
@tadayosi
Copy link
Member Author

Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants