I am using a single node setup for k8s on CentOS7, however the kubernetes stack in infra stack is stuck in creating mode since a long time. Is there an issue with the OS?
I have been having the same issue. I have tried with CentOS, CoreOS, and Debian on single and multi host k8 clusters. All fail as you have depicted above.
I’m using rancher/server:stable on DigitalOcean.
The above setup was hitting serious CPU and memory constraints (load 11+, lots of swapping). What droplet size are you running @taw? And I need a little more info to reproduce (OS (
uname -r), Docker
@superseb My bad. I increased memory on my nodes to compensate for the rancher overhead and everything works fine.
My cluster load tends to be CPU bound so I rarely look at memory, I added an extra gig to each node and the k8 system spun up fine.
I’m enjoying Rancher. Thanks so much for the work you guys have done. I’m excited to test out 2.0.