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

serviceAccountAnnotations is not usable #1493

Open
koltunskim opened this issue Oct 28, 2024 · 1 comment
Open

serviceAccountAnnotations is not usable #1493

koltunskim opened this issue Oct 28, 2024 · 1 comment

Comments

@koltunskim
Copy link

considering documentation, I should be able to use [key].serviceAccountAnnotations map[string]string. This does not work as serivceAccountAnnotations object can not be parsed by the API.

error: strict decoding error: unknown field "spec.override.nodeAgent.serviceAccountAnnotations"

command kubectl get crd datadogagents.datadoghq.com -o yaml | grep -i service | grep -i serviceAccountAnnotations gives empty result.

Chart used is datadog-operator v1.9.0

agent manifest:

apiVersion: "datadoghq.com/v2alpha1"
kind: "DatadogAgent"
metadata:
  name: "datadog"
  namespace: "datadog"
spec:
  features:
    logCollection:
      containerCollectAll: true
      enabled: true
  global:
    clusterName: "redacted"
    credentials:
      apiKey: "redacted"
      appKey: "redacted"
    tags: ["env:env"]
  override:
    nodeAgent:
      serviceAccountAnnotations:
        test: "true"
      containers:
        agent:
          resources:
            limits:
              cpu: "100m"
              memory: "200Mi"
            requests:
              cpu: "50m"
              memory: "100Mi"

I've tried it also with combinations with createRbac and serviceAccountName with no luck

@khewonc
Copy link
Contributor

khewonc commented Oct 30, 2024

@koltunskim The serviceAccountAnnotations field was added in operator v1.10.0, which is undergoing QA at the moment and hasn't been released yet. The CRDs for the datadog-operator helm chart will be updated after v1.10.0 is released. You can double check which version of the operator the chart uses with this appVersion field, which at the moment of writing is 1.9.0

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

2 participants