-
I am currently evaluating hetzner-k3s for a future project and span up a simple cluster. I installed Ingress Nginx via Helm (Chart Version
With the following values set: controller:
service:
annotations:
load-balancer.hetzner.cloud/location: ash
load-balancer.hetzner.cloud/name: ingress-nginx-services
load-balancer.hetzner.cloud/type: lb11
load-balancer.hetzner.cloud/hostname: domain-pointing-to-lb.com
load-balancer.hetzner.cloud/http-redirect-https: 'false'
load-balancer.hetzner.cloud/uses-proxyprotocol: 'true'
load-balancer.hetzner.cloud/use-private-ip: 'true'
replicaCount: 2 Sample Ingress Config: apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-test
namespace: ingress-nginx
annotations:
kubernetes.io/ingress.class: "nginx"
spec:
rules:
- host: domain-pointing-to-lb.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: ingress-nginx-controller
port:
number: 80 Applied hetzner-k3 config # ...
k3s_version: v1.25.5+k3s1
use_ssh_agent: false
ssh_allowed_networks:
- 0.0.0.0/0
api_allowed_networks:
- 0.0.0.0/0
private_network_subnet: 10.0.0.0/16
schedule_workloads_on_masters: false
masters_pool:
# ...
worker_node_pools:
# ... When using Am I missing a configuration or is something off with my setup? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
The annotation |
Beta Was this translation helpful? Give feedback.
The annotation
load-balancer.hetzner.cloud/uses-proxyprotocol: 'true'
enables the proxy protocol on the load balancer, so you need to enable it also in the Nginx configmap otherwise Nginx won't udnerstand requests coming from the load balancer and you'll get a 400. So you need to edit the configmap created in the ingress nginx namespace and add the settinguse-proxy-protocol: "true"
. Hope this helps