Nginx Ingress⚓︎
Important: The NGINX ingress should only be used for open deployments where EOEPCA’s IAM-based request authorization is not required - or you are integrating your own IAM approach. If you are following the IAM integration and request authorization approach described in this guide, then select the APISIX Ingress instead.
This document provides instructions to deploy ingress-nginx for EOEPCA+.
Quickstart Installation⚓︎
Disclaimer: We recommend following the official installation instructions for the NGINX Ingress Controller. However, this quick start guide should also work for most environments.
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm upgrade -i ingress-nginx ingress-nginx/ingress-nginx \
--namespace ingress-nginx --create-namespace \
--set controller.ingressClassResource.default=true \
--set controller.allowSnippetAnnotations=true \
--set controller.service.type=LoadBalancer
Adjust parameters as needed (e.g. NodePort vs. LoadBalancer service).
Forced TLS Redirection⚓︎
By default, if you want to force HTTP→HTTPS redirection, you can use an ingress annotation or config snippet. For instance:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: my-service
annotations:
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
spec:
ingressClassName: nginx
tls:
- hosts:
- "my-service.example.com"
secretName: my-service-tls
rules:
- host: my-service.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: my-service
port:
number: 80