CustomResourceDefinition Ownership Conflict with Helm in K3s v1.32.2+k3s1

[VenuNarukulla]

Description:
When deploying K3s v1.32.2+k3s1, Helm is creating Traefik-related resources by default. This is causing a conflict when attempting to install a Helm release due to ownership metadata issues in CustomResourceDefinitions (CRDs).

Steps to Reproduce:

1. Install K3s v1.32.2+k3s1.
2. Check installed Helm charts:

   helm list -n kube-system

   Output:

   NAME        NAMESPACE    REVISION UPDATED                                 STATUS    CHART                        APP VERSION
   traefik     kube-system  1        2025-03-10 20:40:00.08993631 +0000 UTC  deployed  traefik-34.2.1+up34.2.0     v3.3.2
   traefik-crd kube-system  1        2025-03-10 20:39:43.709288972 +0000 UTC deployed  traefik-crd-34.2.1+up34.2.0 v3.3.2
   

3. Try to install a Helm chart (e.g., Consul):

   helm upgrade --install consul-platform consul \
     -f consul/projectname/values.yaml \
     -f consul/projectname/values-platform.yaml -n platform

4. Error message:

   Release "consul-platform" does not exist. Installing it now.
   Error: Unable to continue with install: CustomResourceDefinition "gatewayclasses.gateway.networking.k8s.io" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "consul-platform": current value is "traefik-crd"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "platform": current value is "kube-system"
   

Expected Behavior:
The Helm installation should proceed without encountering CRD ownership conflicts.

Workaround:

• Installing K3s v1.31.6+k3s1 does not produce this issue. Example:

  helm list -n kube-system

  Output:

  NAME        NAMESPACE    REVISION UPDATED                                 STATUS    CHART                        APP VERSION
  traefik     kube-system  1        2025-03-10 21:05:26.986235908 +0000 UTC deployed  traefik-27.0.201+up27.0.2     v2.11.10
  traefik-crd kube-system  1        2025-03-10 21:05:23.935779018 +0000 UTC deployed  traefik-crd-27.0.201+up27.0.2 v2.11.10
  

  The Consul chart installs successfully without any ownership metadata issues.

Environment:

• K3s version: v1.32.2+k3s1 (problematic), v1.31.6+k3s1 (working)
• Helm version: 3.17
• OS: Ubuntu

Additional Notes:

• This issue appears to be related to the Helm-managed Traefik CRDs being deployed in the kube-system namespace and interfering with other Helm releases.
• Requesting guidance on how to resolve this conflict without downgrading K3s.

---

Would appreciate any insights or workarounds from the community!

[brandond]

Unable to continue with install: CustomResourceDefinition "gatewayclasses.gateway.networking.k8s.io" in namespace "" exists and cannot be imported into the current release:

This isn't a bug. Traefik 2.0 includes Gateway API support and includes the Gateway CRDs. If you want to install a different chart that also bundles these CRDs, you will need to disable the Traefik bundled with K3s, or disable those CRDs in the chart you're trying to deploy.

I would defer to the Consul project on how to disable the Gateway CRDs when deploying their chart.