-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
k3s issue with helm3 and pvc pending #3703
Comments
root@cxcloudagent:~# kubectl get po -n kube-system we are using only this from rancher |
IMAGE TAG IMAGE ID SIZE docker.io/library/busybox latest 3a093384ac306 1.42MB only using these images it is a offline setup ,so loaded only above images |
please help @brandond |
I am not loading the image "docker.io/rancher/klipper-helm" Please help , we are using k3s in prod @brandond |
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions. |
Environmental Info:
K3s Version: k3s version v1.19.7+k3s1 (5a00e38)
helm version
version.BuildInfo{Version:"v3.5.2", GitCommit:"167aac70832d3a384f65f9745335e9fb40169dc2", GitTreeState:"dirty", GoVersion:"go1.15.7"}
Node(s) CPU architecture, OS, and Version:
root@cxcloudagent:/var/lib/rancher/k3s/agent/images# uname -a
Linux cxcloudagent 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 node
Describe the bug:
after deploying some app using helm3 , pod is showing is k3s if I do Kubectl get po
but able to see app by helm ls
it is not happening all the time , but sometimes
then after I restart the server , I am able to see all the pod
and sometimes I see pod is in the pending state due to PVC creation
then I restarted the pod "local-path-provisioner-**" and redeploy the pod to fix the issue
both issues is not consistent ,, only sometimes happening
Steps To Reproduce:
Not able to reproduce the issue ..
we deploy all of our app using script , sometimes we got this
deploying/restart fixed the issue
Additional context / logs:
No error seen
or maybe no idea where I can see the log regarding this
please help
The text was updated successfully, but these errors were encountered: