Umbrella Issue: Remove Third-Party Content

[Davanum Srinivas]

Dear Steering,

SIG-Docs seems to have started down this path ... Do we have an opinion? Do we need to have an opinion?

https://github.com/kubernetes/website/issues/15748 

Thanks,

Dims

--

Davanum Srinivas :: https://twitter.com/dims

[Clayton Coleman]

This seems.... fraught.  I don’t see a concise summary - can we get one?

I would expect the position of “only CNCF content” to be as fraught as “any content in the world”.  I would expect our project to make a meaningful effort to document (without unduly prejudicing or biasing towards particular providers) integrations and conformant distribution workflows.  What do other communities do?

--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CANw6fcHzi%2B2s4z2o41Pd%3DFcdLnJNYWGdeXMZ%2BqCvfWvYQDRqLg%40mail.gmail.com.

[Brandon Philips]

I wrote my thoughts: https://github.com/kubernetes/website/issues/15748#issuecomment-531422298

tl;dr they need a KEP to define what is in and out of scope. This isn't the first time this discussion has happened, in fact I am on a PR where we are questioning Linux Kernel flags that are sane defaults for Kubernetes to use.

Brandon

To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAH16Sh%2B6nw6SULXkX%2BYu0RahjbvhzA9AfXnpvv%2BM5Sb8d37f6Q%40mail.gmail.com.

[Joe Beda]

Yeah – this seems to be really complicated.  Agree on KEP.

 

There are some places where clearly things are too vendory.  We don’t want the project docs to be overly tied to any single commercial product.  (less so with other openly governed oss projects)

 

But there are places where we *should* have some pointers.  Specifically I’m thinking about installing networking as part of a kubeadm cluster.  That documentation is super useful and it does a decent job of pointing to external solutions without making it be about those solutions.  See how the vendor specific content is restricted to a set of tabs without any favorites: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network.

 

We should focus on making users successful first and being “pure” second.

 

Joe

To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAHHNuYfHnmNjpEGjz2%2BbyDzwDLzr%2B%3DeZvmCDDhYTCPBJ7UJ6wQ%40mail.gmail.com.

[Brian Grant]

I responded on the issue.

I did some digging and could find no trace explaining the origin of the requirement other than the issue filed by Zach last month.

To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/FD671155-AED2-43C1-9A85-0D704877B675%40vmware.com.