-
Notifications
You must be signed in to change notification settings - Fork 9
Upstream Kubernetes docs for Fedora need review/update #1
Comments
(While I originally thought there was a problem with the upstream instructions, I figured out today I did have a bug in my config file changes, so kubelet wasn't starting, and hence the node was correctly being reported as not ready) |
So, main issue here is that it needs to be updated to Fedora23/24? |
Yeah, having finally debugged the problem with my own installation, I think that's the main thing. The other items that I found a bit confusing/surprising:
|
Well, at this point you're getting into Kubernetes docs issues, not specifically Fedora. That's how Kubernetes looks at "single node", it's kind of like European floor numbering ;-) I'd love to hear your experience with doing Ansible, if you get around to testing that. |
Yeah, I think the only bit in scope for the Fedora Cloud team here is to keep an eye on the accuracy of the upstream Kubernetes docs - either by updating them directly, or moving them downstream into the Fedora Cloud documentation, and proposing replacing the upstream docs with pointers to the Fedora Cloud ones. As far as trying out Ansible goes, I now have a working setup on my laptop based on a simple "k8s-all-in-one" service definition [1], so I'm unlikely to try any other "from scratch" setup methods any time soon. [1] https://github.com/ncoghlan/container-utils/blob/master/services/k8s-all-in-one.service |
@ncoghlan yeah, I've wondered why we don't offer dev/demo examples using all-in-one. Maybe I need to write one. |
@jberkus If you have not yet started writing the Doc, I can take up this issue :-). |
I was recently trying to get Kubernetes running on my laptop, and went through http://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/
I ended up with the system with a "Not Ready" node (which I haven't managed to debug yet), but noticed a couple of other problems:
yum
)The text was updated successfully, but these errors were encountered: