Скачать или смотреть Solving the Issue of Container Not Available on Set Port in Kubernetes

Discover how to troubleshoot container port issues in Kubernetes, particularly when using nginx, deployment, and service configurations.
---
This video is based on the question https://stackoverflow.com/q/76143210/ asked by the user 'KJ0797' ( https://stackoverflow.com/u/7448604/ ) and on the answer https://stackoverflow.com/a/76143638/ provided by the user 'Radek 'Goblin' Pieczonka' ( https://stackoverflow.com/u/3871750/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Kubernetes - Container not available on set port

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting Kubernetes: Container Not Available on Set Port

When working with Kubernetes, developers often encounter problems that can be frustrating and challenging. One such issue arises when a container is not accessible on a specific port set in the deployment and service configurations. In this guide, we’ll walk you through a common scenario where a user tried to set up an nginx container but ran into issues with port availability. We will explore the possible causes for this problem and how to resolve it effectively.

The Problem

Imagine you have created a Kubernetes deployment and service for an nginx container. Here’s how the commands might look:

[[See Video to Reveal this Text or Code Snippet]]

After setting everything up, you attempt to reach the service using a temporary pod:

[[See Video to Reveal this Text or Code Snippet]]

However, instead of getting a response from your nginx container, you find that it only responds when you curl directly to port 80. This leads to confusion: Why is the specified port (1234) not working?

Understanding Kubernetes Ports

Before we dive into the solution, let’s clarify the different ports involved in Kubernetes:

containerPort: This specifies the port on which the application inside your container is listening. In our example, you set this to 1234.

targetPort: This defines the port that the service will use to access the container. In your setup, this was set to 1234 as well.

port: The port on which the service will expose itself. In this case, it is set to 4444.

The Issue Explained

The key problem here stems from the nature of how nginx operates and what it listens for. By default, nginx listens on port 80. Your attempt to set it to listen on port 1234 by specifying containerPort: 1234 does not change nginx's default behavior unless configured explicitly.

Steps to Resolve the Issue

1. Verify Nginx Configuration

To access the desired port (1234), you need to modify the Nginx configuration inside your container to bind to port 1234. This can typically be done by editing the nginx configuration file (nginx.conf) within the container.

Access your nginx container:

[[See Video to Reveal this Text or Code Snippet]]

Modify the nginx configuration (add or update the server block):

[[See Video to Reveal this Text or Code Snippet]]

Reload nginx to apply the changes:

[[See Video to Reveal this Text or Code Snippet]]

2. Keep It Simple

If there is no strong reason to change the default port, consider using port 80 for simplicity. This will avoid complexity and potential configuration issues while still ensuring your service is accessible.

If keeping the default port, ensure your service targets port 80 instead:

[[See Video to Reveal this Text or Code Snippet]]

Test the service using the same curl command. You should be able to access your nginx container without issues:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

In summary, the issue of a container not being available on a set port in Kubernetes typically stems from the container’s default behavior, not an error in Kubernetes' configuration. By understanding how containerPort, targetPort, and port work in Kubernetes, along with nginx configuration specifics, you can effectively troubleshoot port-related issues.

When in doubt, keep it simple by using default service ports unless there's a compelling reason for a change. By doing so, you can save time and avoid unnecessary headaches while managing your Kubernetes deployments.