Skip to content
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

Merged
merged 1 commit into from
Aug 18, 2020

Conversation

justaugustus
Copy link
Member

@justaugustus justaugustus commented Aug 18, 2020

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:

  • x (MAJOR) --> 2: the v2 instance of these images, which in this case are built on Debian Buster (compared to v1, built on Debian Stretch)
  • y (MINOR) --> 1: we bumped the minor version when we migrated the image building to K8s Infra in cleanup: Base image workflow improvements kubernetes#90665
  • z (PATCH) --> 3: we bump the patch version to trigger a new build when there are negligible changes to the Makefile/Dockerfile

This 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?

images: Use OS codenames to construct clearer versions for Debian images

@k8s-ci-robot k8s-ci-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Aug 18, 2020
@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Aug 18, 2020
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. kind/design Categorizes issue or PR as related to design. area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 18, 2020
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 18, 2020
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
@k8s-ci-robot k8s-ci-robot added the area/release-eng Issues or PRs related to the Release Engineering subproject label Aug 18, 2020
Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 18, 2020
Copy link
Member

@cpanato cpanato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link
Contributor

@hasheddan hasheddan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@dims
Copy link
Member

dims commented Aug 18, 2020

/approve
/lgtm

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@justaugustus
Copy link
Member Author

Thanks everyone!
/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 18, 2020
@justaugustus
Copy link
Member Author

/test pull-release-test

1 similar comment
@justaugustus
Copy link
Member Author

/test pull-release-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/dependency Issues or PRs related to dependency changes area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/design Categorizes issue or PR as related to design. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants