conformance status for /docs/getting-started-guides/fedora/flannel_multi_node_cluster.md

[errordeveloper]

Per #7278, we are looking to identify guides that are stale vs actively maintained but need work to become conformant.

From the content of /docs/getting-started-guides/fedora/flannel_multi_node_cluster.md it is unclear what version of Kubernetes user will get and whether resulting cluster will be conformant or not.

PING owners/approvers/contributors @dchen1107 @aveshagarwal @eparis @thockin @steveperry-53

[errordeveloper]

This guide is dependent on /docs/getting-started-guides/fedora/fedora_manual_config.md, so we should be discussing #7302 first.

[errordeveloper]

In this guide, user is asked to install flannel package, and the version of flannel user gets is a year old 0.7.0, while the latest 0.10.0 was released less than a month ago.

[errordeveloper]

If this guide migrated to kubeadm, it would be much smaller and compliance would be out of the question, also it could offer users an option to run any network addon as a DaemonSet.

[chrisnegus]

As suggested here, I rewrote this doc and the associated singlei-node Fedora guide to use kubeadm. See #8009.

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.