How to uninstall team-container
anhefti opened this issue · 3 comments
anhefti commented
How can I uninstall team-container and start from scratch?
Thanks!
pagong commented
You need to use helm uninstall commands in the reverse order of installation.
Example:
uninstall Jitsi Meet: helm uninstall video team-video --values values-video.yaml
uninstall Setup: helm uninstall setup team-setup --values values-setup.yaml
anhefti commented
Thanks.
I'm new to Kubernetes but with some Docker experiences. And I try to setup a Jitsi Meet service with the help of your article and this repository.
I always stuck within the team router setup where a let's encrypt certificate should be requested and installed.
I work on a Red Hat Enterprise Linux 7 VM with open Ports 80, 443 and 4443. After using helm to install the router team-setup the traefik pod/container always remains in "Pending" status. It seems that something with the volume binding is not correct as the most warning events are about volumes? But I don't have a clue what went wrong and how to fix it.
[root@clancy team-container]# kubectl get pods
NAME READY STATUS RESTARTS AGE
landingpage-9f5bf8678-7nfnn 1/1 Running 0 27m
svclb-traefik-rdzdk 2/2 Running 0 27m
traefik-9d458cdbc-mkh7q 0/1 Pending 0 27m
[root@clancy team-container]#
[root@clancy team-container]# kubectl get events
LAST SEEN TYPE REASON OBJECT MESSAGE
31m Normal Starting node/clancy.ethz.ch Starting kubelet.
31m Warning InvalidDiskCapacity node/clancy.ethz.ch invalid capacity 0 on image filesystem
31m Normal NodeHasSufficientPID node/clancy.ethz.ch Node clancy.ethz.ch status is now: NodeHasSufficientPID
31m Normal NodeHasSufficientMemory node/clancy.ethz.ch Node clancy.ethz.ch status is now: NodeHasSufficientMemory
31m Normal NodeHasNoDiskPressure node/clancy.ethz.ch Node clancy.ethz.ch status is now: NodeHasNoDiskPressure
31m Normal NodeAllocatableEnforced node/clancy.ethz.ch Updated Node Allocatable limit across pods
31m Normal Starting node/clancy.ethz.ch Starting kube-proxy.
31m Normal NodeReady node/clancy.ethz.ch Node clancy.ethz.ch status is now: NodeReady
31m Normal RegisteredNode node/clancy.ethz.ch Node clancy.ethz.ch event: Registered Node clancy.ethz.ch in Controller
28m Normal Starting node/clancy.ethz.ch Starting kubelet.
28m Warning InvalidDiskCapacity node/clancy.ethz.ch invalid capacity 0 on image filesystem
28m Normal Starting node/clancy.ethz.ch Starting kube-proxy.
28m Normal NodeAllocatableEnforced node/clancy.ethz.ch Updated Node Allocatable limit across pods
28m Normal NodeHasSufficientMemory node/clancy.ethz.ch Node clancy.ethz.ch status is now: NodeHasSufficientMemory
28m Normal NodeHasNoDiskPressure node/clancy.ethz.ch Node clancy.ethz.ch status is now: NodeHasNoDiskPressure
28m Normal NodeHasSufficientPID node/clancy.ethz.ch Node clancy.ethz.ch status is now: NodeHasSufficientPID
28m Warning Rebooted node/clancy.ethz.ch Node clancy.ethz.ch has been rebooted, boot id: ab3b106c-ce92-4c6a-98fd-19caa67009fc
27m Normal RegisteredNode node/clancy.ethz.ch Node clancy.ethz.ch event: Registered Node clancy.ethz.ch in Controller
15m Normal WaitForFirstConsumer persistentvolumeclaim/traefik-cert waiting for first consumer to be created before binding
15m Normal ScalingReplicaSet deployment/landingpage Scaled up replica set landingpage-9f5bf8678 to 1
15m Normal ScalingReplicaSet deployment/traefik Scaled up replica set traefik-9d458cdbc to 1
15m Normal SuccessfulCreate replicaset/traefik-9d458cdbc Created pod: traefik-9d458cdbc-mkh7q
15m Normal SuccessfulCreate replicaset/landingpage-9f5bf8678 Created pod: landingpage-9f5bf8678-7nfnn
<unknown> Normal Scheduled pod/landingpage-9f5bf8678-7nfnn Successfully assigned default/landingpage-9f5bf8678-7nfnn to clancy.ethz.ch
15m Normal SuccessfulCreate daemonset/svclb-traefik Created pod: svclb-traefik-rdzdk
<unknown> Normal Scheduled pod/svclb-traefik-rdzdk Successfully assigned default/svclb-traefik-rdzdk to clancy.ethz.ch
15m Normal Pulling pod/landingpage-9f5bf8678-7nfnn Pulling image "nginx:alpine"
15m Normal Pulling pod/svclb-traefik-rdzdk Pulling image "rancher/klipper-lb:v0.1.2"
15m Normal Pulled pod/landingpage-9f5bf8678-7nfnn Successfully pulled image "nginx:alpine"
15m Normal Created pod/landingpage-9f5bf8678-7nfnn Created container landingpage
15m Normal Started pod/landingpage-9f5bf8678-7nfnn Started container landingpage
15m Normal Pulled pod/svclb-traefik-rdzdk Successfully pulled image "rancher/klipper-lb:v0.1.2"
15m Normal Created pod/svclb-traefik-rdzdk Created container lb-port-80
15m Normal Started pod/svclb-traefik-rdzdk Started container lb-port-80
15m Normal Pulled pod/svclb-traefik-rdzdk Container image "rancher/klipper-lb:v0.1.2" already present on machine
15m Normal Created pod/svclb-traefik-rdzdk Created container lb-port-443
15m Normal Started pod/svclb-traefik-rdzdk Started container lb-port-443
<unknown> Warning FailedScheduling pod/traefik-9d458cdbc-mkh7q Failed to bind volumes: timed out waiting for the condition
20s Normal ExternalProvisioning persistentvolumeclaim/traefik-cert waiting for a volume to be created, either by external provisioner "rancher.io/local-path" or manual ly created by system administrator