Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[loki-distributed] Gateway Ingress unable to skip TLS secret #2120

Open
den-is opened this issue Jan 13, 2023 · 0 comments
Open

[loki-distributed] Gateway Ingress unable to skip TLS secret #2120

den-is opened this issue Jan 13, 2023 · 0 comments

Comments

@den-is
Copy link
Contributor

den-is commented Jan 13, 2023

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:

tls:
- secretName: loki-gateway-tls
hosts:
- gateway.loki.example.com

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: [] or tls: 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

# tls:
# - hosts:
# - loki.example.com
# secretName: loki-distributed-tls

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant