ingress - Exploit.cz

ingress

A collection of 4 posts

RKE2 - enable nginx proxy protocol by default

RKE2 - enable nginx proxy protocol by default

After RKE2 upgrade you will lost your rke2-ingress-nginx-controller config values. Define this HelmChartConfig and your setup will be used every time, when you upgrade RKE2. More info about config in official documentation [https://docs.rke2.io/networking/#nginx-ingress-controller]. apiVersion: helm.cattle.io/v1 kind: HelmChartConfig metadata: name: rke2-ingress-nginx namespace: kube-system

Redirect .env file to your Curriculum Vitae - simplest way to Ingress redirect via annotations in Kubernetes

Redirect .env file to your Curriculum Vitae - simplest way to Ingress redirect via annotations in Kubernetes

Redirect /.env file to your curriculum vitae via nginx.ingress.kubernetes.io/temporal-redirect annotation apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/ssl-redirect: "true" kubernetes.io/tls-acme: "true" nginx.ingress.kubernetes.io/from-to-www-redirect: "true" nginx.ingress.kubernetes.io/temporal-redirect: https://exploit.cz/

Failed upgrade - Kubernetes cluster managed by RKE to v1.14

Failed upgrade - Kubernetes cluster managed by RKE to v1.14

I am using RKE cli tool from Rancher for upgrading Kubernetes cluster, but instead of using rancher/nginx-ingress-controller:0.21 I am using kubernetes-ingress-controller/nginx-ingress-controller:0.25.0. In Kubernetes v1.13 kubernetes-ingress-controller/nginx-ingress-controller:0.25.0 works well but stopped after upgrade. You will get this error in ingress

How to solve x-real-ip 127.0.0.1 issue in Kubernetes Rancher cluster

How to solve x-real-ip 127.0.0.1 issue in Kubernetes Rancher cluster

I am using L4 Nginx Loadbalancer to Kubernetes Cluster nodes with Stream configuration in Nginx. Problem is that all Ingress resources got remote_ip from localhost * x-forwarded-for=127.0.0.1 * x-real-ip=127.0.0.1 How to fix? 1. You have to edit global ingress config in ConfigMap named