This message was deleted.
# general
a
This message was deleted.
e
looks like seq is waiting for its pv/pvc to be fulfilled
but nothing is meeting the requirement
m
Hey @echoing-camera-89368 i resolved that error i am getting a different error now
Startup probe failed: Get "<http://10.42.5.100:80/>": dial tcp 10.42.5.100:80: connect: connection refused
PVC is bound to PV so that error is resolved
I am trying to switch storage from LH storage to NFS
True NAS NFS server
e
what container is failing the healthcheck?
m
I see only 1 container
image: datalust/seq:2022.1.7647
SEQ POD is failing
e
whats in the logs there?
m
Deployment is not ready: dev-app/nfs-seq. 0 out of 1 expected pods are ready
e
the actual container logs, it might have a pointed error?
m
doesn’t return anything probably because container is not up
I did
kubectl logs nfs-seq-684cd5bd98-jztdd -n dev-app
and output is empty
e
are you able to start it using host mounts? just as a test?
m
I haven’t tried it. By host mount you mean node storage?
e
correct, use host mounts as the volume
m
I need to check the syntax to do the change in PV let me see
My guess is it is unable to use a sub-directory under the NFS export path
PV is referring to a sub-directory under the NFS mount path
e
you could also try starting a test pod and see if it can write to paths within nfs to test
m
ok
@echoing-camera-89368 Sorry this question is basic k8s. Do i need to create PV and PVC resources if i need to use NFS? I can directly reference the NFS server in the deployment right? I am looking at this link https://major.io/2022/04/08/mount-nfs-shares-in-kubernetes/