Open Fabian-K opened 2 years ago
I've encountered this issue as well, while trying to use a k3d/k3s cluster and installing Flux.
K3s comes with a helmcharts.helm.cattle.io
resource, and also Flux has a helmcharts.source.toolkit.fluxcd.io
.
Trying to go to helmcharts.source.toolkit.fluxcd.io
will result on showing the helmcharts.helm.cattle.io
instead.
This issue also happens when you use both Flux v1 and Flux v2 (during migration for example) as both provides a HelmChart CRD though in different groups.
The same with the RabbitMQ Messaging Topology Operator: built-in Kubernetes user
resources are displayed instead of users.rabbitmq.com
ones.
I have the same issue! We have redefined the workflowtemplates.argoproj.io to workflowtemplates.xxxx. And i can list my cr by using: `kubect get workflowtemplates.xxxx -A ', but the list in k9s is empty.
It's there any plan to fix this issue?
Hi there! I can try to fix it, but I don't have this case in my cluster. Is it possible to create CRDs by hand and apply it to my cluster? Or maybe create minicube cluster with bad crds. @zhangfei614 how did you redefine it? Thanks!
Describe the bug
When installing tekton-triggers and knative-eventing to a cluster, there are two CRDs with the plural
triggers
Starting on the list of CRDs, when selecting
triggers.triggers.tekton.dev
and by that navigating to the instances, the instances oftriggers.eventing.knative.dev
are actually shown.To Reproduce Steps to reproduce the behavior:
customresourcedefinitions
triggers.triggers.tekton.dev
triggers.eventing.knative.dev
instead oftriggers.triggers.tekton.dev
Expected behavior Show instances of the selected CRD
Versions (please complete the following information):
Thanks, Fabian