Change Default HTTP Port for Bitnami/nginx Web Server Using ConfigMap in Kubernetes

Sat, 12 Oct 2024 19:26:00 -0500

When running a Bitnami/nginx web server in Kubernetes, you might need to change the default HTTP port (which is typically port 80) to a different port for various reasons, such as security policies, port conflicts, or custom routing requirements. In this post, we’ll show you how to modify the default port of an NGINX web server using a ConfigMap in Kubernetes.

Change Default Ingress Port to HTTP for Bitnami/nginx in Kubernetes

Fri, 11 Oct 2024 19:26:00 -0500

When setting up Bitnami/nginx as your Ingress controller in a Kubernetes environment, the default configuration may use HTTPS (port 443). However, there are cases where you might want to change the default Ingress port to HTTP (port 80), especially if you’re dealing with non-HTTPS traffic or need to expose services through standard HTTP.

In this post, we will walk through how to modify the default Ingress port for Bitnami/nginx in Kubernetes to use HTTP (port 80) instead of HTTPS, allowing you to handle non-encrypted traffic effectively.

Bitnami on Support Tools

Change Default HTTP Port for Bitnami/nginx Web Server Using ConfigMap in Kubernetes

Change Default Ingress Port to HTTP for Bitnami/nginx in Kubernetes