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

[tempo] helm parse error on service account labels and annotation #3318

Open
rbnmk opened this issue Sep 19, 2024 · 0 comments
Open

[tempo] helm parse error on service account labels and annotation #3318

rbnmk opened this issue Sep 19, 2024 · 0 comments

Comments

@rbnmk
Copy link

rbnmk commented Sep 19, 2024

I am configuring Tempo on AKS with Azure Storage Blob as a backend. For authentication I use Federated (workload) Identity auth. For this I have configured the following in the values.yaml

serviceAccount:
  # -- Specifies whether a ServiceAccount should be created
  create: true
  # -- The name of the ServiceAccount to use.
  # If not set and create is true, a name is generated using the fullname template
  name: null
  # -- Image pull secrets for the service account
  imagePullSecrets: []
  # -- Annotations for the service account
  annotations: 
    azure.workload.identity/client-id: "000000-0000-0000-0000"
  # -- Labels for the service account
  labels: 
    azure.workload.identity/use: "true"
  automountServiceAccountToken: true

I have added the annotations and labels to work with Federated Auth. but now I get the following error:
##[error]Error: UPGRADE FAILED: YAML parse error on tempo/templates/statefulset.yaml: error converting YAML to JSON: yaml: line 34: mapping values are not allowed in this context

I noticed that I do not get this error when running helm upgrade from my computer, I only get the error when running helm upgrade in Azure DevOps pipelines.

output of helm version, which is the same version I am explicitly installing in Azure DevOps pipelines:
version.BuildInfo{Version:"v3.11.3", GitCommit:"323249351482b3bbfc9f5004f65d400aa70f9ae7", GitTreeState:"clean", GoVersion:"go1.20.3"}

While researching I found out there might be related issues for other parts that were already fixed, could it be the same?

source: #767

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

No branches or pull requests

1 participant