# Replicated upgrade from 2.38.0 to 2.49.0 leaves kubeadm and kubelet at version 1.15.3 **URL:** \ **Category:** Supporting your customers\ **Created:** [January 7, 2021, 2:30am UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485 "2021-01-07T02:30:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![MANI\_M](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mani_m/32/136_2.png) [@MANI\_M](https://community.replicated.com/u/MANI_M)\ **Post date:** [January 7, 2021, 2:30am UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485/1 "2021-01-07T02:30:51Z")
Hey There, We recently upgraded replicated to v2.49.0. This version is supposed to upgrade Kubernetes from **v.1.15.3** to **v.1.15.12** and it did. After the upgrade, we noticed that the Kubernetes server is upgraded to v.1.15.12 but `kubeadm` and `kubelet` are still left at `v.1.15.3`. I went through the install script and found that we are force upgrading kubeadm to `v.1.15.12` with `kubeadm upgrade apply "v$k8sVersion" --yes --config /opt/replicated/kubeadm.conf --force` and then we are replacing `kubeadm` binary from archives folder. Even I tried upgrading it manually by running `kubeadm upgrade apply v.1.15.12` it returns back `[upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.15.12". Enjoy!` but kubeadm version still returns v.1.15.3. Any ideas why kubeadm and kubectl were left out and how to get it upgraded? In case I need to upgrade kubeadm binary manually how can that be done? I couldn’t find the binaries anywhere on the internet. Should I compile and get it replaced? ---
**Author:** ![areed](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/areed/32/12_2.png) [@areed](https://community.replicated.com/u/areed)\ **Post date:** [January 8, 2021, 1:52am UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485/2 "2021-01-08T01:52:29Z")
Did you use the `kubernetes-upgrade-patch-version` flag? ---
**Author:** ![MANI\_M](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mani_m/32/136_2.png) [@MANI\_M](https://community.replicated.com/u/MANI_M)\ **Post date:** [January 8, 2021, 2:02pm UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485/3 "2021-01-08T14:02:44Z")
Nope, I was informed to re-run the script from the docs. Let me try that. Thanks. ---
**Author:** ![ethanm](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/ethanm/32/11_2.png) [@ethanm](https://community.replicated.com/u/ethanm)\ **Post date:** [January 8, 2021, 6:39pm UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485/4 "2021-01-08T18:39:57Z")
For reference, optional installer flags can be found here [https://help.replicated.com/docs/kubernetes/customer-installations/installing/](https://help.replicated.com/docs/kubernetes/customer-installations/installing/) ```auto kubernetes-upgrade-patch-version Upgrade to the latest available patch release of Kubernetes ``` ---
**Author:** ![MANI\_M](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mani_m/32/136_2.png) [@MANI\_M](https://community.replicated.com/u/MANI_M)\ **Post date:** [January 9, 2021, 4:04am UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485/5 "2021-01-09T04:04:35Z")
@areed, @ethanm The upgrade gets stuck for hours waiting for rook/ceph’s health report. Here you go with the screenshot. ![image](https://canada1.discourse-cdn.com/flex030/uploads/replicated/original/1X/fcc81fb4cbd4a95c9ee58e579f59c05c2fbe4a61.png) Rook doesn’t come up. When I tried checking docker containers using `docker ps -a` all I can see is ceph containers( **k8s\_envoy-initconfig\_contour\*, k8s\_init-mon-fs\_rook-ceph-mon-a-\*** ) getting exited and there are no logs for them. ---
**Author:** ![ethanm](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/ethanm/32/11_2.png) [@ethanm](https://community.replicated.com/u/ethanm)\ **Post date:** [January 12, 2021, 11:22pm UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485/6 "2021-01-12T23:22:34Z")
Can you get the ceph status or a support bundle? [http://community.replicated.com/t/kots-how-can-i-generate-a-support-bundle-if-i-cannot-access-the-admin-console](http://community.replicated.com/t/kots-how-can-i-generate-a-support-bundle-if-i-cannot-access-the-admin-console) ```auto kubectl -n rook-ceph exec $(kubectl -n rook-ceph get pods -l app=rook-ceph-operator --no-headers | awk '{print $1}') -- ceph status ``` ---
**Author:** ![MANI\_M](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mani_m/32/136_2.png) [@MANI\_M](https://community.replicated.com/u/MANI_M)\ **Post date:** [January 19, 2021, 2:32am UTC](https://community.replicated.com/t/replicated-upgrade-from-2-38-0-to-2-49-0-leaves-kubeadm-and-kubelet-at-version-1-15-3/485/7 "2021-01-19T02:32:04Z")
@ethanm Thanks for the help. I’ve fixed the issue by manually downloading `kubelet` and `kubeadm` binaries and replacing them.