conformance results for v1.13/kind

[BenTheElder]

https://github.com/kubernetes-sigs/kind

[luxas]

Thanks @BenTheElder for submitting!

[taylorwaggoner]

@BenTheElder thanks for submitting! The results look great! Could you please submit a signed participation form so that we have contact info on file? You can mark Nonprofit on the form, as there won't be a fee involved. https://github.com/cncf/k8s-conformance/tree/master/participation-form

Thanks!

[BenTheElder]

Absolutely, taking a look now, thank you!

EDIT: I think I need to run this by legal at work first, will follow up when possible.

[dankohn]

I've confirmed with LF legal that we don't need a signed participation agreement since kind is part of Kubernetes. Sorry for extra delay. We'll approve shortly.

Cc @swinslow

[BenTheElder]

Thank you @dankohn 🙏 -- after some further discussion, I wasn't sure if I even needed to? But I'd been waiting for a response from someone with more authority than I 😅

[taylorwaggoner]

You are now Certified Kubernetes
cncf/landscape#1092

[BenTheElder]

Awesome!! Thank you all! 😄

[dankohn]

You categorized kind as a distribution, but I think we would classify it as an installer, since it is using vanilla, upstream Kubernetes. Agree?

https://github.com/cncf/k8s-conformance/blob/master/faq.md#what-is-a-distribution-hosted-platform-and-an-installer

[BenTheElder]

I was not sure on this and followed kops, which is similar and is also listed as a distribution.

Will defer to you on which is correct. It certainly sounds like installer might make more sense.

---

Additional context:

We provide pre-built docker "node" images containing upstream k8s, and kind create cluster without any options will use one of these images. Currently these are at https://hub.docker.com/r/kindest/node until the wg-k8s-infra has a solution for subprojects to officially host images.

The line here seemed iffy since we're within the project but the kubernetes binaries we build ourselves are possibly debateable as "upstream" since while the sources are upstream, the actual binaries are currently built by us when we publish the image.

They do not contain any patches to Kubernetes.

kind can alternatively build and use an image from local Kubernetes sources, or from packages in apt, so I could see it being either.

[dankohn]

I'm going to switch you and also open an issue with kops suggesting that I believe they're an installer. Thanks. -- Dan Kohn <dan@linuxfoundation.org> Executive Director, Cloud Native Computing Foundation https://www.cncf.io +1-415-233-1000 https://www.dankohn.com

…

On Fri, Jan 25, 2019 at 1:27 PM Benjamin Elder ***@***.***> wrote: I was not sure on this and followed kops, which is similar and is also listed as a distribution <https://github.com/cncf/k8s-conformance/blob/bc371efc05b495a34e1500f73d48403097d949ec/v1.10/kops/PRODUCT.yaml#L7> . Will defer to you on which is correct. It certainly sounds like installer might make more sense. ------------------------------ Additional context: We provide pre-built docker "node" images containing upstream k8s, and kind create cluster without any options will use one of these images. Currently these are at https://hub.docker.com/r/kindest/node until the wg-k8s-infra has a solution for subprojects to officially host images. The line here seemed iffy since we're within the project but the kubernetes binaries we build ourselves are possibly debateable as "upstream" since while the sources are upstream, the actual binaries are currently built by us when we publish the image. They do not contain any patches to Kubernetes. kind can alternatively build and use an image from local Kubernetes sources, or from packages in apt, so I could see it being either. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#451 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC8MBua0YPJ5_yeXrfxLsucaTV8kQlx1ks5vG0yPgaJpZM4aN59H> .

[BenTheElder]

Sounds good to me, Thanks!