-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Provider io.fabric8.knative.client.KnativeExtensionAdapter not found #29096
Labels
Milestone
Comments
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Nov 7, 2022
Thanks for reporting! #29100 should take care of it |
Thanks for the quick fix @geoand. |
YW! |
geoand
added a commit
that referenced
this issue
Nov 9, 2022
Register all implementation of ExtensionAdapter in k8s client extension
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Nov 10, 2022
Fixes: quarkusio#29096 (cherry picked from commit 98f02aa)
pedroh-pereira
pushed a commit
to pedroh-pereira/quarkus
that referenced
this issue
Nov 14, 2022
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Dec 14, 2022
Fixes: quarkusio#29096 (cherry picked from commit 98f02aa)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Dec 14, 2022
Fixes: quarkusio#29096 (cherry picked from commit 98f02aa)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Native binary fails to start when using the
quarkus-kubernetes-client
withknative-client
.Expected behavior
start without issues.
Actual behavior
How to Reproduce?
Reproducer:
Steps:
quarkus.platform.version
is 2.14.0.CR1GreetingResource
class with some usage of the knative client, e.g.:Output of
uname -a
orver
OS name: "linux", version: "5.19.12-200.fc36.x86_64", arch: "amd64", family: "unix"
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.14.0.CR1
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3.8.6
Additional information
No response
The text was updated successfully, but these errors were encountered: