-
Notifications
You must be signed in to change notification settings - Fork 502
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
images: Use OS codenames to construct clearer versions for Debian images #1496
Conversation
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
4a6b261
to
1cf4358
Compare
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.
/lgtm
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.
/lgtm
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.
/lgtm
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.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, dims, hasheddan, justaugustus, saschagrunert, xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks everyone! |
/test pull-release-test |
1 similar comment
/test pull-release-test |
What type of PR is this?
/kind cleanup feature design
/area dependency
What this PR does / why we need it:
Currently the Debian base images we build encode no particularly useful information in the image tag, outside of some yet-to-be-defined SemVer versioning.
A rough example would be:
k8s.gcr.io/build-image/debian-base:v2.1.3
In this case, the version numbers are meant to mean the following:
2
: the v2 instance of these images, which in this case are built on Debian Buster (compared to v1, built on Debian Stretch)1
: we bumped the minor version when we migrated the image building to K8s Infra in cleanup: Base image workflow improvements kubernetes#906653
: we bump the patch version to trigger a new build when there are negligible changes to the Makefile/DockerfileThis PR sets Debian base image tags to use the following nomenclature:
<os-codename>-v<version>
(example:buster-v0.0.0
)The first part of the image tag encodes the Debian OS codename e.g.,
buster
,stretch
, while the second part of the tag is a SemVer-compliant tag (which we can define a policy around at a later date).This has some parallels to the kube-cross image tags (example:
v1.15.0-1
), which encodes the upstream Golang version (v1.15.0
), alongside an additional tag,-1
./hold for any discussion
/assign @tpepper @hasheddan @saschagrunert @cpanato
cc: @kubernetes/release-engineering @dims @BenTheElder
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?