In the 'atomic-host-tests' repo[0], we have a test[1] that was based on
the Red Hat docs[2] for setting up a single node kuberenetes cluster.
We had to adapt the test to work with system containers on Fedora 27 and
I made a quick and dirty gist[3] of the steps we ended up with.
Having said that, I'm in agreement with others on the thread for
following the advice from jbrooks on how to move forward. We can adapt
the existing test to use 'kubeadm' or write a new test to use that approach.
-Micah
[0] https://github.com/projectatomic/atomic-host-tests/
[1]
https://github.com/projectatomic/atomic-host-tests/tree/master/tests/k8-cluster
[2]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/getting_started_with_kubernetes/get_started_orchestrating_containers_with_kubernetes
[3] https://gist.github.com/miabbott/549655e4557c7bd9f774f8d45a79cac6
On 02/21/2018 12:34 PM, Chris Negus wrote:
Red Hat has been phasing out support for manually setting up vanilla Kubernetes
on RHEL and RHEL Atomic. While there are still procedures for setting up
Kubernetes in Fedora in the Kubernetes.io documentation, the Kubernetes project
is considering dropping them because they have become outdated:
https://github.com/kubernetes/website/issues/7301
https://github.com/kubernetes/website/issues/7302
In my mind, this means that someone trying out vanilla Kubernetes will start
with some OS outside of the Fedora/RHEL/CentOS ecosystem. My question is, is it
okay to let this content die? Or should we encourage some way to still manually
use Kubernetes on Fedora (Atomic or not)?
-------------
Chris Negus
Red Hat Principal Technical Writer
RHCA, RHCI, RHCX, RHCE
Author of the Linux Bible, 9th Edition
http://amzn.to/1IBA7NF
