When using the keda chart, I noticed that annotations can generate empty key's when no additional annotations are passed in e.g.

# Source: keda/templates/manager/service.yaml
apiVersion: v1
kind: Service
metadata:
  annotations:
  labels:
    app.kubernetes.io/name: keda-operator    
    helm.sh/chart: keda-2.11.0
    app.kubernetes.io/component: operator
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/instance: release-name
    app.kubernetes.io/part-of: keda-operator
    app.kubernetes.io/version: 2.11.0
  name: keda-operator
  namespace: default
spec:
  ports:
  - name: metricsservice
    port: 9666
    targetPort: 9666
  selector:
    app: keda-operator
---

I am attempted to just alter the helm template logic to only create the annotation key should there be a value passed in. I have added a before and after yaml from running helm template locally. I carried out some local testing where I passed in a number of different values (i.e. not just AdditionalAnnotations) and seemed ok to me.

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)
• README is updated with new configuration values (if applicable) learn more
• A PR is opened to update KEDA core (repo) (if applicable, ie. when deployment manifests are modified)

Fixes #

Files for comparison:
beforeAfter.zip