Accessing the deployed service using Helm chart in Kubernetes cluster

Question

Currently, I am trying to deploy my microservice end point Docker image on a Kubernetes cluster by creating the Helm chart. For this, I created the chart and changed the parameters in values.yaml and deployment.yaml for port change. And also I want to access from my Angular front end. So I added service type= NodePort. And when I described the service, it gave me the port 30983 to access.

And I accessed like http://node-ip:30983/endpoint

But I am only getting the site can't be reached the message. Let me add the details of what I did here:

My values.yaml file containing the following to mention the service type:

And my templates/service.yaml file containing like the following:

And my templates/deployment.yaml file containing the following:

And I tried to access like the following:

http://192.168.16.177:30983/

And only getting site can't be reached.

NB: when I tried to describe the service, then I am getting the following:

The output of kubectl get pod --show-labels like the following image screenshot

Updated

And when we using kubectl describe pod command, getting like the following:

Updated Error

Readiness probe failed: HTTP probe failed with statuscode: 404
Liveness probe failed: HTTP probe failed with statuscode: 404

How can I access my endpoint from deployment?

please provide output of "kubectl get pod --show-labels" and "kubectl get svc" — Vasilii Angapov
– Vasilii Angapov, Commented May 6, 2019 at 8:25
@VasilyAngapov - Yes sir, updated in question. And thank you for your response. — Mr.DevEng
– Mr.DevEng, Commented May 6, 2019 at 8:34
your pod is Crashlooping. Your app is crashing for some reason. You need to read logs "kubectl logs -p POD_NAME" where POD_NAME is the name of your failing pod. — Vasilii Angapov
– Vasilii Angapov, Commented May 6, 2019 at 8:37
@VasilyAngapov - I updated my result sir. Can you please look on updated question ? — Mr.DevEng
– Mr.DevEng, Commented May 6, 2019 at 15:30
you didn't provide the logs of crashlooping pods. Without logs nobody can help you. Read my previous comment again pls. — Vasilii Angapov
– Vasilii Angapov, Commented May 6, 2019 at 16:16

Vasilii Angapov · Accepted Answer · 2019-05-10 16:06:26Z

4

+100

Try this for healthcheck probes:

livenessProbe:
  tcpSocket:
    port: 8085
readinessProbe:
  tcpSocket:
    port: 8085

edited May 10, 2019 at 16:06

answered May 10, 2019 at 8:16

Vasilii Angapov

9,08020 silver badges37 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Mr.DevEng Over a year ago

Ok sir, I will try this change. Thank you for your response.

Mr.DevEng Over a year ago

I updated the question when i tried the kubectl describe pod. Can you look on that please?

Vasilii Angapov Over a year ago

your liveness probe returns 404, that's why your pod is restarting. Liveness probe must only return HTTP response 200. Find a path where it returns 200 or use tcpSocket probe.

Vasilii Angapov Over a year ago

@Jacob I've updated my answer, can you try it and tell if it helps?

probhonjon · Accepted Answer · 2019-05-15 14:13:29Z

1

try the following command docker ps -a and find the container associated with the pod. The container name should be pretty much same as the pod name with some prefix/suffix.

then look at the logs using docker logs <container_id>. Maybe that will give you clues to what it is restarting

answered May 15, 2019 at 14:13

probhonjon

3115 silver badges10 bronze badges

Collectives™ on Stack Overflow

Accessing the deployed service using Helm chart in Kubernetes cluster

2 Answers 2

4 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related