conformance status for /docs/getting-started-guides/fedora/fedora_manual_config.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/fedora_manual_config.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 pull kubernetes and etcd package from Fedora repository, and it looks like the user gets 1.9.1, which is a good sign. The version of etcd is 3.2.7, and I'm not so sure about our current recommendations, but it seems a little older then I'd hope.

Also, it doesn't look kubeadm is available in the upstream distro repo, and kube-apiserver, kube-controller-manager, kube-scheduler & kube-proxy are installed, along with (quite surprisingly) hyperkube.

> docker run -ti fedora dnf install kubernetes etcd
Fedora 27 - x86_64 - Updates                                                                                                                                                                                  3.0 MB/s |  19 MB     00:06    
Fedora 27 - x86_64                                                                                                                                                                                            3.3 MB/s |  58 MB     00:17    
Last metadata expiration check: 0:00:07 ago on Tue Feb 13 12:14:46 2018.
Dependencies resolved.
=============================================================================================
 Package                             Arch      Version                       Repository Size
=============================================================================================
Installing:
 kubernetes                          x86_64    1.9.1-2.fc27                  updates    44 k
Installing dependencies:

...

 docker                              x86_64    2:1.13.1-44.git584d391.fc27   updates    20 M
 docker-common                       x86_64    2:1.13.1-44.git584d391.fc27   updates    85 k
 docker-rhel-push-plugin             x86_64    2:1.13.1-44.git584d391.fc27   updates    1.7 M
 kubernetes-client                   x86_64    1.9.1-2.fc27                  updates    24 M
 kubernetes-master                   x86_64    1.9.1-2.fc27                  updates    40 M
 kubernetes-node                     x86_64    1.9.1-2.fc27                  updates    23 M

...

Transaction Summary
=============================================================================================
Install  62 Packages

Total download size: 150 M
Installed size: 855 M
Is this ok [y/N]: N
Operation aborted.

However, Docker version 1.13.1 is a year old, but I don't suppose it's our problem.

[errordeveloper]

If this guide migrated to kubeadm, it would be much smaller and compliance would be out of the question.

[chrisnegus]

As suggested here, I rewrote this doc and the associated multi-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.