Re: [atomic-devel] Upgrade from kubernetes-apiserver to kubernetes-sig-apiserver

[Rares Vernica <rvernica gmail com>]

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: 0d1581533e65756a0822c691cc9ee846bffe4629604bc213b09e175a86c01d6d
              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: cbb9dbf9c8697e9254f481fff8f399d6808cecbed0fa6cc24e659d2f50e05a3e
              GPGSignature: Valid signature by 64E3E7558572B59A319452AAF17E745691BA8335
# systemctl status kubelet
Unit kubelet.service could not be found.

If I rollback it works fine:

# rpm-ostree rollback

...

# atomic host status
State: idle
Deployments:
● centos-atomic-host:centos-atomic-host/7/x86_64/standard
                   Version: 7.1803 (2018-04-03 12:35:38)
                    Commit: cbb9dbf9c8697e9254f481fff8f399d6808cecbed0fa6cc24e659d2f50e05a3e
             PendingCommit: 0d1581533e65756a0822c691cc9ee846bffe4629604bc213b09e175a86c01d6d
            PendingVersion: 7.1804 (2018-05-21 20:57:24)
              GPGSignature: Valid signature by 64E3E7558572B59A319452AAF17E745691BA8335

  centos-atomic-host:centos-atomic-host/7/x86_64/standard
                   Version: 7.1804 (2018-05-21 20:57:24)
                    Commit: 0d1581533e65756a0822c691cc9ee846bffe4629604bc213b09e175a86c01d6d
              GPGSignature: Valid signature by 64E3E7558572B59A319452AAF17E745691BA8335

# systemctl status kubelet
● kubelet.service - Kubernetes Kubelet Server
   Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)

Is this expected behavior or the upgrade is botched?

Cheers,

Rares

On Thu, May 31, 2018 at 9:49 AM, Rares Vernica <rvernica gmail com> wrote:

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/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

atomic install finished with error code 1 and now systemctl enable is acting up. Also, uninstalling it does not work, but I guess that is expected:

# atomic uninstall kubelet
Unable to find 'kubelet' in the following backends: docker, ostree

Thanks,

Rares

On Wed, May 30, 2018 at 4:22 PM, Rares Vernica <rvernica gmail com> wrote:

Hello,

I installed and have been using kubernetes-apiserver and the other related packages installed with:

> atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-apiserver:latest

I wanted to get a more recent version of Kubernetes, so I installed kubernetes-sig-apiserver and the other related packages with:

> atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-sig-apiserver:latest

After restart, when I check the version it seems that the older Kubernetes is still used:

# kubectl version
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.2", GitCommit:"269f928217957e7126dc87e6adfa82242bfe5b1e", GitTreeState:"clean", BuildDate:"2017-07-03T15:31:10Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.2", GitCommit:"269f928217957e7126dc87e6adfa82242bfe5b1e", GitTreeState:"clean", BuildDate:"2017-07-03T15:31:10Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

How can I enable and use Kubernetes from the newer kubernetes-sig-apiserver packages?

Thanks!

Rares