conformance status umbrella issue

[errordeveloper]

As discussed on the mailing list, we are going enforce conformance rules on getting started guides and remove any guides that result in non-conformant cluster configuration by end of March (i.e. after 1.10 release).

This issue is an umbrella to track progress.

[errordeveloper]

Steps:

• remove guides marked as deprecated (Remove CentOS guide that was already deprecated a while ago #7242)
• remove guides that are effectively deprecated (Remove Fedora guide with deprecated Ansible playbook #7300, Remove outdated rkt guide #7376)
• identify stale guides
  • remove ones that are too old (Remove CoreOS guide that use Kubernetes v0.15.0 #7821)
  • ping authors on any that are a little bit old
• identify guides that are maintained but conformance status is unclear (conformance status for /docs/getting-started-guides/fedora/flannel_multi_node_cluster.md #7301, conformance status for /docs/getting-started-guides/fedora/fedora_manual_config.md #7302)
  • identify guides that do not offer unique value and should be considered for merging
  • identify guides that are maintained and need work to become conformant

[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
/remove-lifecycle stale