-
Notifications
You must be signed in to change notification settings - Fork 350
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
JVM trait refactoring #5476
Comments
squakez
added a commit
to squakez/camel-k
that referenced
this issue
May 9, 2024
* Added `jar` parameter which is automatically populated with the Kit executable Jar * Deprecated `print-command` in order to let distroless to work OOTB Ref apache#5476
squakez
added a commit
to squakez/camel-k
that referenced
this issue
May 9, 2024
* Added `jar` parameter which is automatically populated with the Kit executable Jar * Deprecated `print-command` in order to let distroless to work OOTB Ref apache#5476
squakez
added a commit
to squakez/camel-k
that referenced
this issue
May 9, 2024
squakez
added a commit
to squakez/camel-k
that referenced
this issue
May 21, 2024
* Added `jar` parameter which is automatically populated with the Kit executable Jar * Deprecated `print-command` in order to let distroless to work OOTB Ref apache#5476
squakez
added a commit
to squakez/camel-k
that referenced
this issue
May 21, 2024
squakez
added a commit
to squakez/camel-k
that referenced
this issue
May 23, 2024
* add more unit test * enable the trait for synthetic Kits * add documentation on the jvm trait usage Closes apache#5476
squakez
added a commit
to squakez/camel-k
that referenced
this issue
May 28, 2024
* add more unit test * enable the trait for synthetic Kits * add documentation on the jvm trait usage Closes apache#5476
squakez
added a commit
that referenced
this issue
May 29, 2024
* add more unit test * enable the trait for synthetic Kits * add documentation on the jvm trait usage Closes #5476
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following up a brief analysis done for #5462 I realized we may need a few changes to the JVM trait in order to be able to really run as non-root Integration Pods. Taking the opportunity of this requirement, we should work in order to allow the following sub-features for this trait:
Execute the binary jar built in the container (as a default a quarkus jar app, later any other runtime jar app): Evaluate how we can fully support fa(s)t-jar execution #5539print-command
that forces the presence of a shell)The text was updated successfully, but these errors were encountered: