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 DevOps Consultation Services

Add Few lines about the company here

Contact

MFH Devops Consulation
#4-72-1/1. 1st Floor, Beach Road Lawson’s Bay Colony, Near Shanti Ashram, Opp. Bharat Petroleum, Visakhapatnam, Andhra Pradesh – 530017