Failed to get resource when kind is in two different api versions

[josegonzalez]

Description

I am using Traefik for routing, and they recently switched from traefik.containo.us to traefik.io as their apiVersion. The CRDs are currently duplicated if you install Traefik v2, with a recommendation that users use traefik.io instead of traefik.containo.us (the latter is removed in the upcoming Traefik v3). That said, it looks like helm dashboard ignores the apiVersion of the object and instead just looks up the resource under the first matching CRD.

The /resources endpoint returns the correct apiVersion on the resource, so I'm guessing it could be possible to send that along when fetching the resource vs just depending on the Kind to be unique.

Screenshots

Additional information

No response

[undera]

@josegonzalez Can you compose me a detailed instruction on how to reproduce this in my cluster? Which charts of which version to install?

[josegonzalez]

If you setup a server via k3s as shown here, you'll get the same CRD under two different groups. Then I would create a helm chart with something like the below as a template:

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: redirect-to-https
spec:
  redirectScheme:
    scheme: https
    permanent: true

The helm dashboard will then query the CRD with the wrong apiVersion (traefik.containo.us/v1alpha1).

This is probably also an issue for anyone upgrading across CRDs, where the version increases but the older CRD might be used instead.