Determine canonical list of (run-time) dependencies for Kubernetes

[jberkus]

We need a canonical list of official dependencies for Kubernetes, something we don't currently have. This should appear both in the docs and in the release notes.

For example, this section of the release notes is currently a grab-bag:

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.10.md#external-dependencies

Some of those things should be listed, some shouldn't, and there's certainly stuff that ought to be listed there that isn't.

@jdumars @bgrant0607 @nickchase @zacharysarah

[jberkus]

/sig architecture
/sig release
/sig documentation

[jberkus]

/milestone v1.12
/kind documentation

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[nikhita]

/remove-lifecycle stale

[spiffxp]

/sig cluster-lifecycle
kubeadm does some amount of node-level dependency verifying, perhaps their mechanism is a place to start

Also ref: kubernetes/sig-release#400 for the release team to at least have some kind of documented process to follow in its checklist

[tpepper]

@marpaia fyi

[neolit123]

kubeadm is a consumer only of 2-3 items in the external deps list:

• coredns
• docker

the main consumer of these external deps is the cluster folder, which has to be booted outside of k/k eventually.
if it's booted to a new repo all of it's dependencies can be aggregated in a single document that can be linked to from the main release notes. this will also suggest maintenance from the same folks that will maintain the new cluster repo.

[bgrant0607]

It looks like that dependencies list includes things in the cluster/addons directory, but is missing some obvious things, like etcd.

[MikeSpreitzer]

I suppose this issue is about run-time dependencies. There is also the question of build-time dependencies. Perhaps the title of this issue should be more explicit.

[MikeSpreitzer]

I opened #3749 for the build-time dependencies.

[jberkus]

Spec'd this as run-time dependencies. #3749 is the issue for build-time deps.

[mrbobbytables]

Is this still needed? If so, wouldn't it be an item for k/website if its run-time dependendencies for users?

[LappleApple]

/unassign @jdumars