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.

Sign up for GitHub

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

Jump to bottom

Certify kubeadm v1.7 as a Conformant Kubernetes deployment #637

Closed
stealthybox opened this issue Jan 3, 2018 · 2 comments
Closed

Certify kubeadm v1.7 as a Conformant Kubernetes deployment #637

stealthybox opened this issue Jan 3, 2018 · 2 comments
Labels
area/test area/upgrades kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@stealthybox
Copy link
Member

Run the same steps as described in cncf/k8s-conformance#62.
Upload the same files to v1.7/.

/area testing
/area upgrades
/kind documentation
/priority important-soon
@k8s-ci-robot k8s-ci-robot added area/test area/upgrades kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 3, 2018
@stealthybox
Copy link
Member Author

Related #617 #616

@luxas
Copy link
Member

luxas commented Jan 3, 2018

I spoke to @dankohn and the v1.7 submission period is now closed.
We know kubeadm has been steadily conformant in automated e2e infra since v1.6 when it went beta, so in the end it doesn't matter much whether we have our results there or not, anyone can go to https://k8s-testgrid.appspot.com/sig-cluster-lifecycle-all#periodic-kubeadm-gce-1.7 and see for themselves that everything's ok.

Thanks for filing the issue though

@luxas luxas closed this as completed Jan 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/test area/upgrades kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stealthybox @luxas @k8s-ci-robot