Skip to content
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

Knative deployer uses hasApiGroup to check for Knative support #31833

Merged
merged 1 commit into from
Mar 14, 2023

Conversation

manusa
Copy link
Contributor

@manusa manusa commented Mar 14, 2023

Fix #31787

This PR reverts (the reverted changes of) #30743

The isSupported method and its interface (SupportTestingClient) are deprecated and will be removed (fabric8io/kubernetes-client#4659).

The recommended approach is to use Client#supports(Class) or Client#supports(String, String). However, Knative has many resources (+versions) and its unclear which types/classes should be used for the check. So in this case, using hasApiGroup with the lenient matcher seems like reasonable choice to be able to target multiple Knative versions and APIs (Functions, Serving, Eventing, and so on).

Signed-off-by: Marc Nuri <marc@marcnuri.com>
@quarkus-bot
Copy link

quarkus-bot bot commented Mar 14, 2023

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@geoand geoand merged commit 9daba4f into quarkusio:main Mar 14, 2023
@quarkus-bot quarkus-bot bot added this to the 3.0 - main milestone Mar 14, 2023
@manusa manusa deleted the fix/knative branch March 14, 2023 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Knative deployer client check always fails over missing KnativeExtensionAdapter
3 participants