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?
Deployment Speed: A Helm map will quickly be deployed into a Kubernetes cluster. Either pull down a GitHub project with the Helm chart that you simply are about to deploy, or provide the Chart name from the required Helm repository. The Consul-Helm repository is fetched from GitHub, or from the default Helm repository hosted by Google.
A chart may be an assortment of files that describe a connected set of Kubernetes resources. A single chart can be used to deploy one thing straightforward, sort of a Memcached pod, or one thing advanced, sort of a full app stack with communications protocol servers, databases, caches, and so on. Helm is a tool for managing Kubernetes charts.
To create a new Helm chart, use: 2. Using the ls command, list the chart structure: The Helm chart directory contains: Directory charts – Used for adding dependent charts. Empty by default. Directory templates – Configuration files that deploy in the cluster.
Deploy Helm Chart 1 Check minikube Status. If Minikube isn’t running, the install Helm chart step returns an error. ... 2 Install the Helm Chart. The helm install command deploys the app. ... 3 Export the Pod Node Port and IP Address. Copy the two export commands from the helm install output. 4 View the Deployed Application. ...
Try this for healthcheck probes:
livenessProbe:
tcpSocket:
port: 8085
readinessProbe:
tcpSocket:
port: 8085
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
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With