Add a tutorial for setting up a 3-node Kubernetes cluster on Debian with Flannel for networking, with working DNS and the web dashboard

[howa]

Hi,

first of all thanks for your great work!!

However ... Having fragmented tutorials will not help when trying to get a grip on Kubernetes. Existing tutorials on setting up a cluster will fail after a few days as underlying Specs and processes are permanently changing.

Suggestion: Make one tutorial that describes how to SUCCESSFULLY

• set-up a 3 Node cluster on Debian x (where each of the Debian servers is in a minimal state, i.e. no desktop version)
• with Flannel as the CNI plugin
• in which 2 pods can successfully communicate between each other (DNS working)
• a service from outside the cluster is reachable
• have the dashboard running and is reachable from outside with a proper port forwarding enabled once the server starts

And keep the tutorial up-to date so it will be working for anyone at anytime who uses it in order to learn Kubernetes. If the the single steps in the tutorial are annotated well and references to sources are given, this tutorial will constitute a landmark resource for Kubernetes going forward serving the community as a reference.

Best Holger

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[sftim]

/retitle Add a tutorial for setting up a 3-node Kubernetes cluster on Debian with Flannel for networking, with working DNS and the web dashboard

/language en /kind feature

[sftim]

This is quite a specific request. A page like that is hard to maintain, and there's a cardinality issue: if we document for Debian and Flannel, what about all the other combinations? CRI-O, Calico, Ubuntu? containerd, flannel, Fedora? There are many of these.

It might work better as a blog article unless we can find a hidden supply of documentation maintainers.

/priority awaiting-more-evidence

[sftim]

There's a similar challenge with https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Setting up this kernel is only really useful if you combine it with a libc, a DNS resolver, a root filesystem, etc. However the docs for Linux itself don't cover all the detail you'd need it to, and that's left for other projects to cover.

Right now there isn't a good Kubernetes equivalent to https://www.linuxfromscratch.org/

Maybe one day there will be.

[howa]

Point(s) taken: Difficult to scope on specific stack, for instance: Debian 11 CRI-O Flannell As other providers being neglected. However: Readers will gradually replace components as appropriate. Main objective will be achieved - Have a working set-up in a lab to test and play around. Maintaining of the tutorial While this point is valid it actually is the core idea of the whole exercise. Ensuring that a working set-up can be deployed at all times and is indeed working. This could be supported by some sort of continuos integration testing by automatically spawning the 3 node cluster by running the instalment instructions provided with the tutorial. If failing, the script / tutorial needs amendment.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sftim]

/close not-planned

[k8s-ci-robot]

@sftim: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/website/issues/40870#issuecomment-1952159487): >/close not-planned Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.