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

Helm chart is using wrong image tag and proxy config for GEL in SSD mode #12845

Closed
monodot opened this issue May 1, 2024 · 0 comments · Fixed by #12878
Closed

Helm chart is using wrong image tag and proxy config for GEL in SSD mode #12845

monodot opened this issue May 1, 2024 · 0 comments · Fixed by #12878

Comments

@monodot
Copy link
Contributor

monodot commented May 1, 2024

Describe the bug
When deploying GEL 3.0 from the Helm chart, the following happens:

  • The chart tries to deploy enterprise-logs:v3.0.0 but the image tag is actually enterprise-logs:3.0.0 (without the v). So the deployment fails to pull the image from Docker Hub.
  • The GEL plugin for Grafana does not show Ring Health properly, because the enterprise gateway is configured with proxy URLs which assume distributed mode, and not the default SSD mode.

To Reproduce
Steps to reproduce the behavior:

  1. Create a values.yaml file
  2. helm template --values values.yaml gel grafana/loki | less
  3. Notice that the image tag is v3.0.0 instead of 3.0.0. The URLs on the Deployment are set to distributed URLs (distributor, ingester, etc).

Expected behavior
The Helm chart should deploy GEL 3.0.0, and the GEL plugin for Grafana should correctly show Ring health.

Environment:

  • Infrastructure: laptop -> GKE
  • Deployment tool: helm

Screenshots, Promtail config, or terminal output
N/A

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