You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
When using yurtctl revert to revert the yurt cluster back to a kubernetes cluster, it seems that it will not delete the configmap yurt-tunnel-nodes which is used by yurt-tunnel to resolve dns.
We can find the configmap yurt-tunnel-nodes after reversion.
What you expected to happen:
yurtctl should delete yurt-tunnel-nodes when yurt-tunnel has been deployed through yurtctl convert --deploy-yurttunnel
How to reproduce it (as minimally and precisely as possible):
Use yurtctl convert --deploy-yurttunnel to convert the k8s cluster to openyurt cluster and then use yurtctl revert to revert it back to the k8s cluster.
others
We can also find configmap yurtctl-lock left in the cluster. Does it need to be deleted as well?
/kind bug
The text was updated successfully, but these errors were encountered:
@Congrool Thank you for raising issue.
I think these two configmaps should be removed after yurtctl revert, would you like to take over and fix this bug?
@Congrool Thank you for raising issue. I think these two configmaps should be removed after yurtctl revert, would you like to take over and fix this bug?
What happened:
When using
yurtctl revert
to revert the yurt cluster back to a kubernetes cluster, it seems that it will not delete the configmapyurt-tunnel-nodes
which is used by yurt-tunnel to resolve dns.We can find the configmap
yurt-tunnel-nodes
after reversion.root@openyurt-e2e-test-control-plane:~/openyurt# kubectl get cm -A NAMESPACE NAME DATA AGE default kube-root-ca.crt 1 50m kube-node-lease kube-root-ca.crt 1 50m kube-public cluster-info 2 50m kube-public kube-root-ca.crt 1 50m kube-system coredns 1 50m kube-system extension-apiserver-authentication 6 50m kube-system kube-proxy 2 50m kube-system kube-root-ca.crt 1 50m kube-system kubeadm-config 2 50m kube-system kubelet-config-1.20 1 50m kube-system yurt-tunnel-nodes 1 43m kube-system yurtctl-lock 0 46m local-path-storage kube-root-ca.crt 1 50m local-path-storage local-path-config 1 50m
What you expected to happen:
yurtctl should delete
yurt-tunnel-nodes
when yurt-tunnel has been deployed throughyurtctl convert --deploy-yurttunnel
How to reproduce it (as minimally and precisely as possible):
Use
yurtctl convert --deploy-yurttunnel
to convert the k8s cluster to openyurt cluster and then useyurtctl revert
to revert it back to the k8s cluster.others
We can also find configmap
yurtctl-lock
left in the cluster. Does it need to be deleted as well?/kind bug
The text was updated successfully, but these errors were encountered: