fix: ServiceAccount are correctly annotated

[JorTurFer]

NOTE: This other PR is in conflict as both updates the index, we will have to merge one and the rebase the other one

During the RBAC modifications, we introduced a but that suppressed the operator service account annotations. This can be critical for users who don't use podIdentity section but directly annotate the service account with pod identity information (basically, KEDA doesn't use pod identity on their cases)

This PR keeps the serviceaccount segregation, but instead of a fallback condition that includes the old serviceAccount.annotations only if the more new ones aren't set (which was failing because the values.yaml sets them) now we will place both together. When users migrate their yamls, they just need to add the new ones and remove the old ones, but as default, they won't have any breaking change

Checklist

• I have verified that my change is according to the deprecations & breaking changes policy
• Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes kedacore/keda#5758

[jkremser]

can you please elaborate on the issue here?

only if the more new ones aren't set (which was failing because the values.yaml sets them)

what do you mean by this exactly? User's values.yaml sets them? Or the default values.yaml that are bundled with the new version of the chart? Because if it was the latter, the issue would make sense to me, but these are empty:

• https://github.com/kedacore/charts/blob/v2.14.1/keda/values.yaml#L299
• https://github.com/kedacore/charts/blob/v2.14.1/keda/values.yaml#L308
• https://github.com/kedacore/charts/blob/v2.14.1/keda/values.yaml#L317

so if not provided, the old format is tried

[JorTurFer]

Default values provided by chart's values.yaml set them to true:

charts/keda/values.yaml

Lines 290 to 317 in f9f23e9

	serviceAccount:
	operator:
	# -- Specifies whether a service account should be created
	create: true
	# -- The name of the service account to use.
	name: keda-operator
	# -- Specifies whether a service account should automount API-Credentials
	automountServiceAccountToken: true
	# -- Annotations to add to the service account
	annotations: {}
	metricServer:
	# -- Specifies whether a service account should be created
	create: true
	# -- The name of the service account to use.
	name: keda-metrics-server
	# -- Specifies whether a service account should automount API-Credentials
	automountServiceAccountToken: true
	# -- Annotations to add to the service account
	annotations: {}
	webhooks:
	# -- Specifies whether a service account should be created
	create: true
	# -- The name of the service account to use.
	name: keda-webhook
	# -- Specifies whether a service account should automount API-Credentials
	automountServiceAccountToken: true
	# -- Annotations to add to the service account
	annotations: {}

[JorTurFer]

This condition is failing because of that:

 {{- toYaml (.Values.serviceAccount.operator).annotations | default .Values.serviceAccount.annotations | nindent 4}}

As .Values.serviceAccount.operator is true, it takes the annotations although are empty, not using ever the default vale, breaking the old behaviour

[jkremser]

thanks again @JorTurFer for taking this one
(lgtm)