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

kube-cross: Build v1.22-dev-1 image using etcd v3.5.0 #2123

Closed
wants to merge 3 commits into from

Conversation

justaugustus
Copy link
Member

What type of PR is this?

/kind feature
/area dependency

What this PR does / why we need it:

Part of kubernetes/kubernetes#102294.
(cc: @serathius @pacoxu)

  • kube-cross: Build v1.21-go1.16.5-1 image
  • kube-cross: Build v1.22-go1.16.5-1 image
  • kube-cross: Build v1.22-dev-1 image using etcd v3.5.0

This PR includes a version pattern change to encode more information into the
image tag:

v<kubernetes-release>-<config-identifier>-<revision>

The v1.22-go1.16.5-1 and v1.21-go1.16.5-1 image should be roughly equivalent to v1.16.5-1.

Signed-off-by: Stephen Augustus [email protected]

/assign @saschagrunert @hasheddan @cpanato @puerco
cc: @kubernetes/release-engineering

Which issue(s) this PR fixes:

Special notes for your reviewer:

/hold I'm not married to this tag change, so open to suggestions.
Ideally, I'd like to accomplish the following:

  • at a glance, understand what branch the image should be used for
  • have an image variant (dev) that allows us to test when we change dependencies that are not Golang

I'll make changes to the canary variant as part of #2117.

Does this PR introduce a user-facing change?

- kube-cross: Build v1.21-go1.16.5-1 image
- kube-cross: Build v1.22-go1.16.5-1 image
- kube-cross: Build v1.22-dev-1 image using etcd v3.5.0 

This is a version pattern change to encode more information into the
image tag:

v<kubernetes-release>-<config-identifier>-<revision>

The image should be roughly equivalent to v1.16.5-1.

Signed-off-by: Stephen Augustus <[email protected]>
@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. release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Jun 16, 2021
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority labels Jun 16, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justaugustus

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

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 16, 2021
@justaugustus
Copy link
Member Author

(The dependencies test is likely going to fail)

GO_VERSION: '1.16.5'
IMAGE_VERSION: 'v1.22-dev-1'
PROTOBUF_VERSION: '3.7.0'
ETCD_VERSION: 'v3.5.0'
Copy link
Member

Choose a reason for hiding this comment

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

remind me why etcd is included in kube-cross?

Copy link
Member

Choose a reason for hiding this comment

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

possibly the the integration tests dockerized (e.g. on mac)?
would like to see this verified or we can just remove it.

Copy link
Member Author

Choose a reason for hiding this comment

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

@BenTheElder -- #2124 builds an image without etcd, but I haven't had time this week to test just yet.

Copy link
Member Author

Choose a reason for hiding this comment

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

@k8s-ci-robot
Copy link
Contributor

@justaugustus: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-release-verify d7135c6 link /test pull-release-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@@ -1,25 +1,35 @@
variants:
dev:
Copy link
Member

Choose a reason for hiding this comment

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

what's the difference between dev, canary, and 1.22?

@liggitt
Copy link
Member

liggitt commented Jun 16, 2021

A few random thoughts:

  • I think I like the per-release addressability, so that the same go version with different proto generators doesn't need to use -legacy tags ad-hoc
  • I'm not sure why we're building etcd into these images... if it's really just used for the build, maybe we don't need it?
  • It's not clear to me what the VERSION file in master would reference... the dev image or the 1.22 image (currently)
  • I thought were hoping to move in the direction of allowing the go version to be selected from within k/k itself, so we could bump a go version and have it be effective in all builds/CI jobs without needing to mess with test-infra stuff in parallel (cc @BenTheElder)

@justaugustus
Copy link
Member Author

/hold for testing a different approach in #2124

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 16, 2021
@k8s-ci-robot
Copy link
Contributor

@justaugustus: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@justaugustus
Copy link
Member Author

Due to Debian bullseye and Golang 1.17 upstream image updates happening roughly in tandem, the latest image builds shifted to using bullseye, instead of buster by default (ref: #2218).

I'm combining this PR with go1.17 image updates in #2211 to tackle this all at once and minimize the image promotion churn.

/close

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closed this PR.

In response to this:

Due to Debian bullseye and Golang 1.17 upstream image updates happening roughly in tandem, the latest image builds shifted to using bullseye, instead of buster by default (ref: #2218).

I'm combining this PR with go1.17 image updates in #2211 to tackle this all at once and minimize the image promotion churn.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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 cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants