Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Microk8s reset stuck after "Warning Ingress is deprecated" message

See original GitHub issue

Version

v1.19.2-34+1b3fa60b402c1c

installed using snap --classic

Issue

I cant reset my microk8s node, it get stuck after some warnings with the same message and I need to ctrl + c

inspection-report-20200929_194702.tar.gz

arturo@dred:~$ microk8s reset
Disabling all addons.
Disabling addon : ambassador
Disabling addon : cilium
Disabling addon : dashboard
Disabling addon : dns
Disabling addon : fluentd
Disabling addon : gpu
Disabling addon : helm
Disabling addon : helm3
Disabling addon : host-access
Disabling addon : ingress
Disabling addon : istio
Disabling addon : jaeger
Disabling addon : juju
Disabling addon : knative
Disabling addon : kubeflow
Disabling addon : linkerd
Disabling addon : metallb
Disabling addon : metrics-server
Disabling addon : multus
Disabling addon : prometheus
Disabling addon : rbac
Disabling addon : registry
Disabling addon : registry-help
Disabling addon : storage
All addons disabled.
Calling clean_cluster
Cleaning resources in namespace kube-system
No resources found
No resources found
No resources found
configmap "extension-apiserver-authentication" deleted
endpoints "kube-controller-manager" deleted
endpoints "kube-scheduler" deleted
lease.coordination.k8s.io "kube-controller-manager" deleted
lease.coordination.k8s.io "kube-scheduler" deleted
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
Cleaning resources in namespace kube-public
No resources found
No resources found
No resources found
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
No resources found
Cleaning resources in namespace kube-node-lease
No resources found
No resources found
No resources found
lease.coordination.k8s.io "dred" deleted
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
Cleaning resources in namespace default
No resources found
No resources found
No resources found
endpoints "kubernetes" deleted
persistentvolumeclaim "my-release-moodle" deleted
persistentvolumeclaim "data-my-release-mariadb-0" deleted
service "kubernetes" deleted
endpointslice.discovery.k8s.io "kubernetes" deleted
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

Issue Analytics

State:
Created 3 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

balchuacommented, Oct 5, 2020

@ktsakalozos While trying to reproduce this last weekend, i found out that in certain cases microk8s reset doesn’t restore back the cni. Because microk8s start returns 1 so the script exists before reaching the point where we apply the cni.yaml. For some strange reason it looks like it fails here. https://github.com/ubuntu/microk8s/blob/8c23ed3800608aa10c7b6d6b01ac9c256f382464/microk8s-resources/actions/common/utils.sh#L429

Didn’t get the chance to actually print it. It doesn’t happen all the time though. My guess is it could be related to the “checkpoint in progress” issue. But i have to try it again.

0reactions

stale[bot]commented, Nov 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.