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
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:
Create a values.yaml file
helm template --values values.yaml gel grafana/loki | less
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
The text was updated successfully, but these errors were encountered:
Describe the bug
When deploying GEL 3.0 from the Helm chart, the following happens:
enterprise-logs:v3.0.0
but the image tag is actuallyenterprise-logs:3.0.0
(without thev
). So the deployment fails to pull the image from Docker Hub.To Reproduce
Steps to reproduce the behavior:
helm template --values values.yaml gel grafana/loki | less
v3.0.0
instead of3.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:
Screenshots, Promtail config, or terminal output
N/A
The text was updated successfully, but these errors were encountered: