Error with defaultFelixConfiguration.enabled: true with Helm

[mnival]

Expected Behavior

It should be possible to enable:

defaultFelixConfiguration:
  enabled: true

after a first installation done with the default values

Current Behavior

Currently, I receive this error:

$ helm upgrade --reset-values -n tigera-operator platform-nonprod-calico projectcalico/tigera-operator -f configuration/calico-values.yaml --version 3.28.1
Error: UPGRADE FAILED: Unable to continue with update: FelixConfiguration "default" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "platform-nonprod-calico"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "tigera-operator"

configuration/calico-values.yaml:

installation:
  cni:
    type: Calico
defaultFelixConfiguration:
  enabled: true
  wireguardEnabled: true

I executed these command before helm command:

kubectl label FelixConfiguration default app.kubernetes.io/managed-by=Helm
kubectl annotate FelixConfiguration default meta.helm.sh/release-namespace=tigera-operator
kubectl annotate FelixConfiguration default meta.helm.sh/release-name=platform-nonprod-calico

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

• Calico version
• Calico dataplane (iptables, windows etc.)
• Orchestrator version (e.g. kubernetes, mesos, rkt):
• Operating System and version:
• Link to your project (optional):

[coutinhop]

@mnival it doesn't look like you followed these steps when upgrading: https://docs.tigera.io/calico/3.28/operations/upgrading/kubernetes-upgrade#upgrading-an-installation-that-was-installed-using-helm

Could you try them and let us know if it works that way?