-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KnativeClient.isSupported doesn't check all of the applicable API Groups #4447
Comments
This change should be applied to DefaultServiceCatalogClient as well. |
@shawkins : I'm not sure if I understand. From my understanding we only want to use kubernetes-client/extensions/service-catalog/generator/cmd/generate/generate.go Lines 57 to 59 in c134637
Isn't it working as expected? Or perhaps I've misunderstood the problem. |
It is working as expected, but it's more restrictive that what the older check was. Since we don't guarantee a 1-1 relationship with api groups and clients, it's best to have these checks be more general. Should there be another sub group introduced, it will have the same problem as knative. |
…I Groups (fabric8io#4447) + Extension client interfaces should extend SupportTestingClient rather than implementations + Disable exact apiGroup match in isSupported method call in extension clients which use more than one apiGroup. This effects Istio, Knative and Tekton extensions that use more than one apiGroups Signed-off-by: Rohan Kumar <rohaan@redhat.com>
…I Groups (fabric8io#4447) + Extension client interfaces should extend SupportTestingClient rather than implementations + Disable exact apiGroup match in isSupported method call in extension clients which use more than one apiGroup. This effects Istio, Knative and Tekton extensions that use more than one apiGroups Signed-off-by: Rohan Kumar <rohaan@redhat.com>
…I Groups (fabric8io#4447) + Disable exact apiGroup match in isSupported method call in extension clients which use more than one apiGroup. This effects Istio, Knative and Tekton extensions that use more than one apiGroups Signed-off-by: Rohan Kumar <rohaan@redhat.com>
…I Groups (fabric8io#4447) + Disable exact apiGroup match in isSupported method call in extension clients which use more than one apiGroup. This effects Istio, Knative and Tekton extensions that use more than one apiGroups Signed-off-by: Rohan Kumar <rohaan@redhat.com>
…I Groups (#4447) + Disable exact apiGroup match in isSupported method call in extension clients which use more than one apiGroup. This effects Istio, Knative and Tekton extensions that use more than one apiGroups Signed-off-by: Rohan Kumar <rohaan@redhat.com>
This can now be done because fabric8io/kubernetes-client#4447 is included in version 6.3 of the k8s client
Describe the bug
Initially reported: quarkusio/quarkus#28171
With fix: quarkusio/quarkus#28172
The current implementation of
isSupported()
forKnativeClient
is:This is not taking into consideration all of the API groups our models support:
Fabric8 Kubernetes Client version
6.0.0
Steps to reproduce
KnativeClient.isSupported
method.false
is returned instead oftrue
Expected behavior
true
should be returned insteadSuggested fix
The check should not be exact:
The text was updated successfully, but these errors were encountered: