-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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 microservices Tanka: error during manifest generation #9361
Comments
5 tasks
DylanGuedes
pushed a commit
that referenced
this issue
May 4, 2023
**What this PR does / why we need it**: Fixes an error on the ServiceMonitor generated when ``` memberlist_ring_enabled: true, create_service_monitor: true, ``` It also adds some checks on `memberlist.libsonnet` to avoid generating invalid kubernetes manifests. **Which issue(s) this PR fixes**: Fixes #9361
aminesnow
pushed a commit
to aminesnow/loki
that referenced
this issue
May 4, 2023
…na#9362) **What this PR does / why we need it**: Fixes an error on the ServiceMonitor generated when ``` memberlist_ring_enabled: true, create_service_monitor: true, ``` It also adds some checks on `memberlist.libsonnet` to avoid generating invalid kubernetes manifests. **Which issue(s) this PR fixes**: Fixes grafana#9361
Hi @DylanGuedes , Thanks |
Not sure, but probably less than 2 months (2.9 release) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There is an error during manifest generation with the following options:
The error is:
Error: evaluating jsonnet: RUNTIME ERROR: Field does not exist: name /home/ivan.rizzante/kubernetes/gitops/loki/vendor/loki/servicemonitor.libsonnet:42:13-42 thunk from <object <anonymous>> Array element 3 Field "values" Array element 0 Field "matchExpressions" Field "selector" Field "spec" Field "serviceMonitor" During manifestation
To Reproduce
Steps to reproduce the behavior:
tk show
Expected behavior
I should be able to generate the manifests
Environment:
Screenshots, Promtail config, or terminal output
If applicable, add any output to help explain your problem.
The text was updated successfully, but these errors were encountered: