You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also because the ingress controller is seeing TLS secret configured for the Ingress object it automatically redirects traffic to HTTPS.
So I had to disable ssl-redirect:
annotations:
haproxy.org/ssl-redirect: "false"
This is a common config across many ingress controllers.
The text was updated successfully, but these errors were encountered:
Installation of loki-distributed with Gateway Ingress enabled is forcing you to use TLS secret for the host:
Chart values.yaml has default non-empty TLS secret defined:
helm-charts/charts/loki-distributed/values.yaml
Lines 939 to 942 in ccdb6f3
I'm deploying loki-distributed in an internal network where I do not need TLS/HTTPS communications with loki-gateway.
Passing null values during the helm install do not override not null default values.
I.e.: These do not work
tls: []
ortls: null
This is a known bug helm/helm#5184
Please comment out the default value and keep them as an example.
At the same time the chart already has correctly disabled the default TLS secret for non-Gateway Ingress object
helm-charts/charts/loki-distributed/values.yaml
Lines 805 to 808 in ccdb6f3
Also because the ingress controller is seeing TLS secret configured for the Ingress object it automatically redirects traffic to HTTPS.
So I had to disable ssl-redirect:
This is a common config across many ingress controllers.
The text was updated successfully, but these errors were encountered: