OK, makes sense. Any ideas on why kublet does not install successfully
after update?
# atomic install --system --system-package=no --name kubelet
registry.centos.org/centos/kubernetes-sig-kubelet:latest
Extracting to /var/lib/containers/atomic/kubelet.0
File /etc/kubernetes/config already exists
On 05/31/2018 02:05 PM, Rares Vernica wrote:
> I just realized that my problem is related to atomic host update:
>
> # atomic host status
> State: idle
> Deployments:
> ● ostree://centos-atomic-host:centos-atomic-host/7/x86_64/standard
> Version: 7.1804 (2018-05-21 20:57:24)
I just realized that my problem is related to atomic host update:
# atomic host status
State: idle
Deployments:
● ostree://centos-atomic-host:centos-atomic-host/7/x86_64/standard
Version: 7.1804 (2018-05-21 20:57:24)
Commit: 0d1581533e65756a0822c691cc9ee8
46b
I think I got the master to work, but the nodes are in a strange state now:
# atomic install --system --system-package=no --name kubelet
registry.centos.org/centos/kubernetes-sig-kubelet:latest
Extracting to /var/lib/containers/atomic/kubelet.0
File /etc/kubernetes/config already exists
File /etc/
