Skip to content
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

Closed
rajibul007 opened this issue Jul 23, 2021 · 5 comments
Closed

k3s issue with helm3 and pvc pending #3703

rajibul007 opened this issue Jul 23, 2021 · 5 comments

Comments

@rajibul007
Copy link

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

@rajibul007
Copy link
Author

root@cxcloudagent:~# kubectl get po -n kube-system
NAME READY STATUS RESTARTS AGE
local-path-provisioner-7ff9579c6-kz8qk 1/1 Running 2 2d23h
metrics-server-7b4f8b595-gvv5w 1/1 Running 1 2d23h
coredns-66c464876b-k6qpg 1/1 Running 1 2d23h

we are using only this from rancher

@rajibul007
Copy link
Author

rajibul007 commented Jul 23, 2021

IMAGE TAG IMAGE ID SIZE

docker.io/library/busybox latest 3a093384ac306 1.42MB
docker.io/rancher/library-busybox 1.31.1 1c35c44120825 764kB
docker.io/rancher/local-path-provisioner v0.0.14 e422121c9c5f9 13.4MB
docker.io/rancher/metrics-server v0.3.6 9dd718864ce61 10.5MB
docker.io/rancher/pause 3.1 da86e6ba6ca19 327kB

only using these images

it is a offline setup ,so loaded only above images

@rajibul007
Copy link
Author

rajibul007 commented Jul 23, 2021

please help @brandond

@rajibul007
Copy link
Author

rajibul007 commented Jul 26, 2021

I am not loading the image "docker.io/rancher/klipper-helm"
As I don't see the usecase and not giving any error
Is that image necessary ? is It causing the issue

Please help , we are using k3s in prod @brandond

@stale
Copy link

stale bot commented Jan 22, 2022

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.

@stale stale bot added the status/stale label Jan 22, 2022
@stale stale bot closed this as completed Feb 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant