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

How to add private Docker registry to Rancher

Via kubectl kubectl -n kube-system create secret docker-registry gitlab \ --docker-server="registry.example.com" \ [email protected] \ --docker-username=name \ --docker-password=password Via Kubernetes yaml apiVersion: v1 data: .dockerconfigjson: eyJhdXRocyI6eyJyZWdpc3RyeS5leGFtcGxlLmNvbSI6eyJ1c2VybmFtZSI6Im5hbWUiLCJwYXNzd29yZCI6InBhc3N3b3JkIiwiZW1haWwiOiJyZWdpc3RyeUBleGFtcGxlLmNvbSIsImF1dGgiOiJibUZ0WlRwd1lYTnpkMjl5WkE9PSJ9fX0= kind: Secret metadata: name: gitlab

Longhorn - Kubernetes persistent volume storage

Deploy You can deploy Longhorn persistent volume storage via kubectl apply -f https://raw.githubusercontent.com/rancher/longhorn/v0.3-rc/deploy/longhorn.yaml Destroy Destroying is not that easy. If you run kubectl delete -f https://raw.githubusercontent.com/rancher/longhorn/v0.3-rc/deploy/longhorn.yaml command, you will stuck

Terraform: Autogenerate LoadBalancer config for Nginx

My production stack is build on top of Kubernetes cluster running in the Hetzner Cloud powered by Rancher 2. High Availability Installation with External Load Balancer (TCP/Layer 4) needs nginx.conf with all IP addresses of all worker nodes. I dont want to hardcode IPs into this config, so

Custom dockerized deployment without AWS

To be written