This is common mistake we should avoid with volumes while deploying applications on Kubernetes

Issue

Exposed service or pods as NodePort and LoadBalancer as-well but application is not accessible on web/external

Common mistakes

  • Trying to use the server IP:port is a blunder instead we should use node_IP:port.

Run below command to find the node IP addresses

kubectl get nodes -o wide |  awk {‘print $1″ ” $2 ” ” $7’} | column -t

  • Using the same pvc (Persistent Volume Claim), Check the below Resolution :

Resolution

  • Created new PVC

Old file

Correct PVC name in yaml file

Update deployment file with right PVC name

1 thought on “This is common mistake we should avoid with volumes while deploying applications on Kubernetes”

Leave a Comment

MFH IT Solutions (Regd No -LIN : AP-03-46-003-03147775)

Consultation & project support organization.

Contact

MFH IT Solutions (Regd)
NAD Kotha Road, Opp Bashyam School, Butchurajupalem, Jaya Prakash Nagar Visakhapatnam, Andhra Pradesh – 530027