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 File /etc/kubernetes/kubelet already exists systemctl daemon-reload systemctl enable kubelet <1># systemctl enable kubelet Failed to execute operation: Access denied <1># systemctl daemon-reload # systemctl enable kubelet Failed to execute operation: No such file or directory On Thu, May 31, 2018 at 11:41 AM, Dusty Mabe <du...@dustymabe.com> wrote: > > > 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) > > Commit: 0d1581533e65756a0822c691cc9ee8 > 46bffe4629604bc213b09e175a86c01d6d > > GPGSignature: Valid signature by > 64E3E7558572B59A319452AAF17E745691BA8335 > > > > ostree://centos-atomic-host:centos-atomic-host/7/x86_64/standard > > Version: 7.1803 (2018-04-03 12:35:38) > > Commit: cbb9dbf9c8697e9254f481fff8f399 > d6808cecbed0fa6cc24e659d2f50e05a3e > > GPGSignature: Valid signature by > 64E3E7558572B59A319452AAF17E745691BA8335 > > # systemctl status kubelet > > Unit kubelet.service could not be found. > > > > This is expected. The kubelet was removed recently in favor of running > kubernetes > /openshift via containers. > > Dusty >
