Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Track upstream releases better #25

Closed
chuckha opened this issue Jul 12, 2018 · 3 comments
Closed

Track upstream releases better #25

chuckha opened this issue Jul 12, 2018 · 3 comments
Assignees
@timothysc

Comments

@chuckha
Copy link
Member

chuckha commented Jul 12, 2018

Since releasing is manual, we track the first few release of k8s and then assume the conformance tests are not changing for the release. We need to track our v1.x tags with release-1.x upstream.
@timothysc
Copy link
Member

We need to move kube-conformance upstream and have that be part of the release artifacts of upstream imo. We've carried this debt for too long.

@timothysc timothysc mentioned this issue Jul 13, 2018
Merged
@johnSchnake
Copy link
Contributor

The kube-conformance image is now maintained upstream so this issue should get closed once we start to use it. As of now it hasn't been released yet so we are holding off on that being the default.

xref #4

@johnSchnake
Copy link
Contributor

Going to close this since the upstream will start using this. We should have a small # of releases left.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@timothysc timothysc

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chuckha @timothysc @johnSchnake