provider-helm hides providerconfigs

[crossplane-contrib]

provider-helm hides providerconfigs

[muvaf]

You can also give enough information for kubectl to figure it out, i.e. providerconfig.gcp would also work.

[jbw976]

@echarles this is the somewhat unfortunate (but expected) behavior of kubectl when multiple CRDs with the same Kind (but different groups) are installed into the cluster. All the providers have a type called ProviderConfig, so you'd see the same behavior if you installed say both provider-gcp and provider-aws.

I'm not exactly sure how kubectl or api-server picks which type has precedence, but to be sure you're doing an operation on the correct type, you should use the fully qualified name - e.g. providerconfig.gcp.crossplane.io.

[echarles]

I get that it is how kubectl / k8s behaves. I would have hoped that all ProviderConfig would be shown, and not only the ones from a single group.

I guess this issue can be closed. It is maybe worth to mention that behavior in the docs.

[echarles]

Closing as the reported behavior is expected.