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
When installin mimir helm chart 5.5.0 with ArgoCD I recognized permanent outofsync in grafanaagent resource like documented in suxess-it/kubriX#722 (comment) ?
When deploying with „helm template …“| kubectl apply I get
Error from server (BadRequest): error when creating "STDIN": GrafanaAgent in version "v1alpha1" cannot be handled as a GrafanaAgent: strict decoding error: unknown field "spec.containers[1].topologySpreadConstraints"
and indeed topologySpreadConstraints is not a valid attribute inside containers attribute.
I believe the problem is that topologySpreadConstraints has an indent of 6 instead of 4:
Describe the bug
When installin mimir helm chart 5.5.0 with ArgoCD I recognized permanent outofsync in grafanaagent resource like documented in suxess-it/kubriX#722 (comment) ?
When deploying with „helm template …“| kubectl apply I get
Error from server (BadRequest): error when creating "STDIN": GrafanaAgent in version "v1alpha1" cannot be handled as a GrafanaAgent: strict decoding error: unknown field "spec.containers[1].topologySpreadConstraints"
and indeed topologySpreadConstraints is not a valid attribute inside containers attribute.
I believe the problem is that topologySpreadConstraints has an indent of 6 instead of 4:
mimir/operations/helm/charts/mimir-distributed/templates/metamonitoring/grafana-agent.yaml
Line 67 in 197314a
To Reproduce
Steps to reproduce the behavior:
Install mimir 5.5.0 helm chart with ArgoCD or simply apply rendered GrafanaAgent resource like in suxess-it/kubriX#722 (comment)
Expected behavior
ArgoCD app should be synced and healthy or command explained above should run without error.
Environment
Additional Context
The text was updated successfully, but these errors were encountered: