This repository has been archived by the owner on Jun 18, 2022. It is now read-only.
rio uninstall does not cleanup all the rio resources #613
Comments
rancher-max
assigned rancher-max, cbron, StrongMonkey and daxmc99 and unassigned rancher-max
Oct 28, 2019
Also,
|
Also does not remove any secrets that were added with rio (githubtoken in my case) |
Rio uninstall should wait for CRDS to be cleaned up before deleting the controller. This avoids cert-manager CRDS blocking rio-system ns deletion. |
@rancher-max Available to test in master. |
This gave a fatal error, but actually did clean up the resources. We should remove the FATAL though: $ rio uninstall
Waiting for linkerd uninstall job to be finished
Cleaning up CRDs...
Deleting System Namespace rio-system...
Delete validating webhook
FATA[0049] clusterroles.rbac.authorization.k8s.io "rio-privileged" not found |
Riofile that I used for testing https://github.com/daxmc99/rio-demo/tree/rio-permissions-test |
Looks like it's all fixed! Uninstalling and reinstalling successfully, and resources are cleaned up on uninstall. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Running rio uninstall leaves some rio resources in the cluster.
To Reproduce
rio uninstall
in a cluster that has rio installed.It removes everything from
kubectl api-resources
andkubectl get crds -A
as expected, but there are three unexpected items withkubectl get clusterroles -A
:Running
kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io -A
yieldsNo resources found
as expected.Kubernetes version & type (GKE, on-prem):
kubectl version
-- multiple versions, but most recently:Rio version:
rio info
Uninstalled, but this was on v0.6.0-alpha.1
The text was updated successfully, but these errors were encountered: