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

Lighter weight make for conformance dependencies, better script and manifest #74608

Conversation

dims
Copy link
Member

@dims dims commented Feb 26, 2019

What type of PR is this?
/kind feature

What this PR does / why we need it:

  • Update Makefile to make it easier for folks to build/run dependencies and image
  • Add a manifest with a specific namespace to run things in
  • Add a script that can be reused in a CI job (and can be run against say a local kind cluster)

Which issue(s) this PR fixes:

Related to #69777

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

Change-Id: I78cff10231eabd53b1fc7bdd1526c861179e135a
Change-Id: I137180ed781edd4a9877cabe039e40a72aa71366
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/feature Categorizes issue or PR as related to a new feature. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/release Categorizes an issue or PR as relevant to SIG Release. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 26, 2019
@dims
Copy link
Member Author

dims commented Feb 26, 2019

/assign @timothysc @ixdy

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 26, 2019
spec:
containers:
- name: conformance-container
image: staging-k8s.gcr.io/conformance-amd64:v1.14-alpha4
Copy link
Member

Choose a reason for hiding this comment

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

do we want to hardcode this version in here?

also why staging-k8s?

Copy link
Member Author

Choose a reason for hiding this comment

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

will fix. these are from the code that already exists, will have to change that

@dims dims force-pushed the lighter-weight-make-for-conformance-dependencies branch 2 times, most recently from 09424f3 to 35476ac Compare February 27, 2019 02:40
Change-Id: I1eb673fe37b5e8a719f9095473765c80fb7f2347
@dims dims force-pushed the lighter-weight-make-for-conformance-dependencies branch from 35476ac to 87d9903 Compare February 27, 2019 12:39
@dims
Copy link
Member Author

dims commented Feb 27, 2019

/test pull-kubernetes-integration

1 similar comment
@dims
Copy link
Member Author

dims commented Feb 27, 2019

/test pull-kubernetes-integration

@dims dims changed the title Lighter weight make for conformance dependencies Lighter weight make for conformance dependencies, better script and manifest Feb 27, 2019
Change-Id: Ib0d6f681be3537f0cbfcae1dc254f1c42a04be66
@dims
Copy link
Member Author

dims commented Feb 27, 2019

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Feb 27, 2019
@k8s-ci-robot k8s-ci-robot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Feb 27, 2019
Copy link
Member

@timothysc timothysc left a comment

Choose a reason for hiding this comment

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

Generally lgtm , but I'm conflicted on the landing zone for some of this vs. under build as a set of image artifacts.

/lgtm
/hold

/cc @stevesloka @ixdy

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Feb 27, 2019
@k8s-ci-robot
Copy link
Contributor

@timothysc: GitHub didn't allow me to request PR reviews from the following users: stevesloka.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Generally lgtm , but I'm conflicted on the landing zone for some of this vs. under build as a set of image artifacts.

/lgtm
/hold

/cc @stevesloka @ixdy

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.

@dims
Copy link
Member Author

dims commented Feb 27, 2019

/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 Feb 27, 2019
@k8s-ci-robot k8s-ci-robot merged commit b2e9b2a into kubernetes:master Feb 27, 2019

REGISTRY?=staging-k8s.gcr.io
REGISTRY?=k8s.gcr.io
Copy link
Member

Choose a reason for hiding this comment

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

this should have remained staging - you can't push to k8s.gcr.io directly, only to staging.

Copy link
Member Author

Choose a reason for hiding this comment

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

aha. will fix in a next rev

@mtaufen
Copy link
Contributor

mtaufen commented Feb 28, 2019

FYI @dims @ixdy make quick-release fails for me after this PR on a fresh Kubernetes clone. I think this is because it created both dockerized and local directories, but the local directory doesn't have ginkgo (and possibly other things?) in it.

Error message:

+++ [0228 15:38:34] Building conformance image for arch: amd64
cp: cannot stat '/usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/cluster/images/conformance/../../../_output/local/bin/linux/amd64/ginkgo': No such file or directory
make[1]: *** [build] Error 1
!!! [0228 15:38:34] Call tree:
!!! [0228 15:38:34]  1: /usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/build/lib/release.sh:424 kube::release::build_conformance_image(...)
!!! [0228 15:38:34]  2: /usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [0228 15:38:34]  3: /usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [0228 15:38:34]  4: /usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [0228 15:38:34]  5: build/release.sh:45 kube::release::package_tarballs(...)
+++ [0228 15:38:39] Deleting docker image k8s.gcr.io/kube-scheduler:v1.15.0-alpha.0.619_aaf40dd13c6eb5
+++ [0228 15:38:39] Deleting docker image k8s.gcr.io/kube-proxy:v1.15.0-alpha.0.619_aaf40dd13c6eb5
+++ [0228 15:38:40] Deleting docker image k8s.gcr.io/cloud-controller-manager:v1.15.0-alpha.0.619_aaf40dd13c6eb5
+++ [0228 15:38:40] Deleting docker image k8s.gcr.io/kube-controller-manager:v1.15.0-alpha.0.619_aaf40dd13c6eb5
+++ [0228 15:38:41] Deleting docker image k8s.gcr.io/kube-apiserver:v1.15.0-alpha.0.619_aaf40dd13c6eb5
+++ [0228 15:38:45] Deleting hyperkube image k8s.gcr.io/hyperkube-amd64:v1.15.0-alpha.0.619_aaf40dd13c6eb5
!!! [0228 15:38:45] previous Docker build failed
!!! [0228 15:38:45] Call tree:
!!! [0228 15:38:45]  1: /usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [0228 15:38:45]  2: /usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [0228 15:38:45]  3: /usr/local/google/home/mtaufen/go-tools/src/k8s.io/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [0228 15:38:45]  4: build/release.sh:45 kube::release::package_tarballs(...)
+++ [0228 15:38:46] Building tarball: node windows-amd64
!!! [0228 15:38:54] previous tarball phase failed
Makefile:426: recipe for target 'quick-release' failed
make: *** [quick-release] Error 1

@dims
Copy link
Member Author

dims commented Mar 1, 2019

@mtaufen let me try that

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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. 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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note-none Denotes a PR that doesn't merit a release note. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/release Categorizes an issue or PR as relevant to SIG Release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants