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

Missing conformance docs for 1.10 and 1.11 #273

Closed
spiffxp opened this issue Jul 27, 2018 · 9 comments
Closed

Missing conformance docs for 1.10 and 1.11 #273

spiffxp opened this issue Jul 27, 2018 · 9 comments

Comments

@spiffxp
Copy link
Contributor

spiffxp commented Jul 27, 2018

We have https://github.com/cncf/k8s-conformance/blob/master/docs/KubeConformance-1.9.md but not the 1.10 and 1.11 variants.

ref: #109

I am interested in how these are generated in whether it can be automated so I'll be taking a crack at this.

@lachie83
Copy link
Contributor

lachie83 commented Jul 27, 2018

I would also like to suggest we version pin sonobuoy-conformance.yaml in the root dir of the repo. eg sonobuoy-conformance-1.10.yaml

@spiffxp
Copy link
Contributor Author

spiffxp commented Jul 27, 2018

I can't seem to find any docs for how these were generated but I think I found the PR that added the code. Things are hardcoded. Generating them today would require some manual hacking around. I will start there and see how we can iterate

@brahmaroutu
Copy link
Contributor

#279
#280
Also conformance document is generated using the following step for v1.11 tag.
checkout v1.11
go run test/conformance/walk.go --conformance --url https://github.com/kubernetes/kubernetes/tree/v1.11.0 test

note that url is currently supplied.

@timothysc
Copy link
Member

So this work was originally intended to be autogenerated and published with the main docs for every release.

@spiffxp
Copy link
Contributor Author

spiffxp commented Jul 31, 2018

Thus far it hasn't worked out that way. I haven't been able to dig up a tracking issue for this intention. The code is currently locked into k/k, it would be useful to see if there's a way this could be an out-of-tree tool, but at this point I'll take whatever we can get.

@timothysc
Copy link
Member

The IBM folks, namely @brahmaroutu , we're leading that effort.

@PatrickLang
Copy link

PatrickLang commented Dec 13, 2018

v1.13 too. This is part of what I was asking about at Kubecon - I'm hoping I can refer users to a list of test cases without having to build and run the test tools themselves.

@hh
Copy link
Collaborator

hh commented Jun 17, 2019

#622 Ready for Review / Merging

@hh
Copy link
Collaborator

hh commented May 17, 2021

/close
This is merged!

@cncf-ci cncf-ci closed this as completed May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants