ServiceAccount name used in deployment doesn't match actual SA name

[Timizki]

Expected Behavior

Service account name in deployment should match actual service account name.

Service account:
apiVersion: v1 kind: ServiceAccount metadata: name: example-kestra-operator namespace: example

Replicaset template:
apiVersion: apps/v1 kind: ReplicaSet metadata: name: example-kestra-operator-7b9ff767dc namespace: example spec: template: spec: serviceAccount: example-kestra-operator serviceAccountName: example-kestra-operator

Actual Behaviour

Service account:
apiVersion: v1 kind: ServiceAccount metadata: name: example-kestra-operator namespace: example

Replicaset template:
apiVersion: apps/v1 kind: ReplicaSet metadata: name: example-kestra-operator-7b9ff767dc namespace: example spec: template: spec: serviceAccount: kestra-operator serviceAccountName: kestra-operator

Steps To Reproduce

Env:

• k3s
• argocd
• helm

1. create new helm "example":
2. add kestra-io operator helm chart as dependency
3. create values.yaml with content
   kestra-operator: annotations: test: example-test
4. install example chart to k3s / kubernetes with argocd
5. Check Replicaset

Environment Information

• Kestra Version:
• Helm Charts version: 1.0.0
• K3s version: v1.31.5+k3s1
• Argocd version: 2.12.10