-
Notifications
You must be signed in to change notification settings - Fork 519
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
[EPIC] Buildpacks-based container image build strategy #439
Comments
18 tasks
manusa
changed the title
Support for Buildpacks
[EPIC] Buildpacks-based container image build strategy
Nov 17, 2023
This comment was marked as resolved.
This comment was marked as resolved.
This was referenced Nov 20, 2023
This was referenced Nov 21, 2023
This was referenced Dec 4, 2023
3 tasks
Shall we close this one? The only open issue should be closed by eclipse-jkube/jkube-integration-tests#371 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As a user, I want to be able to use Eclipse JKube to build container images and deploy them to a Kubernets-compatible cluster for my Java application leveraging Buildpacks, so that I can take advantage and reuse one of the many production ready buildpacks to create an image for my application.
Buildpacks is used by many frameworks, such as Spring Boot, to create container images for an application. There is a curated, community-maintained, growing list of buildpacks to support all kinds of frameworks, libraries, and programming languages.
Currently, JKube can be made compatible with Buildpacks-produced container images by tuning the image name at the buildpacks level, or modifying JKube's resource configuration.
However, this is cumbersome and requires the user to provide additional configurations.
It would be good to have a transparent, seamless integration with Buildpacks (similar to what we have for Jib). This way, a user wouldn't need to worry about additional configurations and could simply leverage Buildpacks by configuring it as JKube's container image build strategy.
Tasks
https://docs.google.com/document/d/1HYSEad6pLBvtHJqyCmNdUUTE3lhIdCDd1AtmA5p-9MY/
k8s:push
/k8sPush
should work withbuildpacks
build strategy #2464k8s:watch
/k8sWatch
should throw error inbuildpacks
build strategy #2461k8s:debug
throws error when usingbuildpacks
build strategy #2462To be discussed later:
JKube generators should be able to provide opinionated BuildPackConfiguration #2460
Cache buildpack builds in a local docker volume #2463
See also:
Relates to:
The text was updated successfully, but these errors were encountered: