-
Notifications
You must be signed in to change notification settings - Fork 14
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
45 support for garden linux images #46
45 support for garden linux images #46
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to me:
- 22 is supported for two weeks => remove
- 11 is supported until year end => remove
- 17+21 should be enough, and for a BETA jdk-only should be okay
@RealCLanger what do you think? what is about the changed debian install scripts?
Thanks, tried to follow the structure you have and keep it consistent with the rest of the Dockerfiles. I'm happy with all options: As the change in the installation procedure should have to my understanding limited impact on the container base image consumer, it may be sufficient to enhance the Dockerfiles with next update by your automation and just overwrite them. |
@pnpavlov I have now updated the script that generates the docker files and then generated the files. Please check and update this PR. |
515b898
to
156f322
Compare
@RealCLanger, PR updated to include only a .github/workflows/publish-container-images.yaml GH action. After merge, it should enable engineers with right level of access to trigger a release of individual SapMachine release based on specific Garden Linux version. Unfortunately afaik it's not possible to test by triggering the proposed GH Action from a PR (for good reasons). Could you please review, merge, test if running the GH Action with sapMachineVersion: 23 and gardenLinuxVersion: 1592 produces as expected new tagged images in https://github.com/SAP/SapMachine/pkgs/container/sapmachine/versions?filters%5Bversion_type%5D=tagged. If granted permissions temporary in SapMachine-Infrastructure I'm happy to test myself too. |
Fixes: #45
Includes the dockerfiles used for publishing https://github.com/orgs/SAP/packages/container/sapmachine/versions?filters%5Bversion_type%5D=tagged and a skeleton for a GitHub action that can publish images for future SapMachine versions against a specific Garden Linux release.
It should be possible to test the workflow with something like, but not done because of permissions and not sure if this makes sense to run or should be enhanced further first.
Test performed:
then applying deployment with two replicas of ghcr.io/sap/sapmachine:21-jdk-gl-1592 with topologySpreadConstraints to make sure deployment happens to both nodes