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

mimir helm chart 5.5.0 fails (ArgoCD outofsync or unknown field) #9638

Closed
jkleinlercher opened this issue Oct 15, 2024 · 1 comment · Fixed by #9669
Closed

mimir helm chart 5.5.0 fails (ArgoCD outofsync or unknown field) #9638

jkleinlercher opened this issue Oct 15, 2024 · 1 comment · Fixed by #9669
Assignees
Labels
bug Something isn't working helm

Comments

@jkleinlercher
Copy link

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:

{{- include "mimir.lib.topologySpreadConstraints" (dict "ctx" $ "component" "meta-monitoring") | nindent 6 }}

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

  • Infrastructure: Kubernetes
  • Deployment tool: helm

Additional Context

@narqo
Copy link
Contributor

narqo commented Oct 18, 2024

Thank you for reporting this. It will be resolved in 5.5.1, that we're preparing in #9670

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working helm
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants