Getting started guide is wrong
Closed this issue · 9 comments
Hello!
I'm trying to reproduce Project Atomic Getting Started Guide and getting access denied when enabling kube-apiserver service with systemctl enable kube-apiserver
Plase update docs.
I'm using centos-atomic.
Current versions of CentOS Atomic have the kubernetes-master pkg removed from the image, to be run from containers. There's info on that here: https://wiki.centos.org/SpecialInterestGroup/Atomic/ContainerizedMaster.
Do you have any plans to write Getting started guide against CentOS version?
@pastukhov
Not's necessarily write a documentation for CentOS, but, instead, to adapt the current documentation for changes of CentOs too. It's possible to reuse what already is done. I'm working on it!
@pastukhov did you managed to solved this issue? I'm trying to replicate the same procedure http://www.projectatomic.io/docs/gettingstarted/ on Centos-Atomic but I'm getting access denied when I hit this commands sudo systemctl enable etcd kube-apiserver kube-controller-manager kube-scheduler
Any clue?
@BubacarrC Did you make units as described in https://wiki.centos.org/SpecialInterestGroup/Atomic/ContainerizedMaster ?
Yes, I made the units and the containers starts to run on my master. However, my nodes are unresponsive when I perform this step on them in forming the cluster. This is my latest issue now. kubectl get node list the nodes and they are on the ready state anyways. Any idea?
You should only need to make those units if you're running centos -- the screen above suggests fedora?
Yes, I made the units and the containers starts to run on my master. However, my nodes are unresponsive when I perform this step on them in forming the cluster. This is my latest issue now. kubectl get node list the nodes and they are on the ready state anyways. Any idea?