Good video, nice and clear. I am on 11.9 and need to get to 15.3. From what I have read, I have to go to 12 then 13 then 14 then 15. That is a lot of files to config for each version of kubespray.
Hi Mathew, thats what I too understood from the documentation. But its very unusual that in a production real world situation anyone would jump from 11.x to 15.x. Slow incremental upgrade is fine. Because there will be lots of changes between these two versions.
How to renew kubespray Kubernetes Cluster certificate.I' getting Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2023-07-13T12:32:50Z is after 2023-07-12T10:37:48Z this error while accessing Kubespray K8 cluster.
Thank you for the video. Can I use the same steps to update the patch version, and not the minor version? and what happens with certificates? Are new certificates generated for kubelets and other cluster elements when updating?
Hi, thanks for watching. I guess the certificates will be re-issues when upgrading but I am not sure. Haven't looked at the certificates after upgrading.
Hi Venkat, I have 8 node cluster HA mode and i want to upgrade the same from 1.11 to 1.12 so i have one query if upgrade fails or something wrong happen with cluster do we have rollback option available for this as well through kubespray....
Hi Nitin, thanks for watching. I just glanced at the documentation and there was no clear instructions on rollback. I guess when the upgrade fails, you will have to update the playbook to older version and re-run it. The node that was partially updated and failed will be rolled back while other nodes that haven't been upgraded will not be touched as you know Ansible is idempotent.
Hi Venkat , Thanks for the video . I have one query regarding update from v1.16 to v1.18. Though i could able to upgrade from v1.15 to v1.16 but not able to upgrade the same cluster to v1.18. I saw the file roles/default/download/main.yml there is not entry for v1.18. Can you suggest what i need to do?
Hi , there are multiple errors coming to run the playbook, for example fatal: [localhost]: FAILED! => {"msg": "template error while templating string: expected token '=', got 'end of statement block'. String: {% set test %}It works{% endset %}{{ test == 'It works' }}"}
Hi Venkat, i have a question here, if for some reason ansible fails to upgrade any of the worker node or master node, would ansible playbook rollback to older version?
HI Kasim, thanks for watching. I don't think it will rollback any changes. Its an automation tool and does what it is told to do :) If for some reason a node fails during the upgrade or the upgrade fails on that node, understand why it failed and rectify it or just remove and add the node. There are ansible playbooks to remove a node and re-add it by updating the inventory file. This will be covered in tomorrow's video. Thanks.
Can we configure kubespray to manage existing cluster not deployed from kubespray. if i installed k8s using kubeadm, can i manage (add,delete,upgrade) using kubespray.
Hi Raj, thanks for watching. Although you can do it, it will be a whole lot of work. You can modify the playbooks accordingly as per your existing Kubernetes deployment. You can do a dry run to see what ansible (Kubespray) will change in your cluster.
@@justmeandopensource Thanks for the reply. What tool would you recommend i.e., kubeadm or kubespray to provision k8s cluster in bare metal for production?
@@ravipacc I would use Kubespray. Kubeadm is manual method. Infact kubespray uses kubeadm to provision the cluster but through automation using ansible playbooks.
can I configure kubespray to manage existing Kubernetes cluster provisioned with kubeadm? The goal is to upgrade the Kubernetes cluster using kubespray, which is provisioned using ansilbe+ kubeadm. I really appreciate it if you can help me solving this issue
Hello congratulations for the video, I saw in the documentation that there is a safe upgrade and an insecure upgrade. What would that be in this case? I also saw that in the documentation they pass a parameter -e Example below: ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.19.7 -e upgrade_cluster_setup=true
Does any one have this error: 'dict object' has no attribute 'v1.20.4'. I am on Ansible 2.9.6, python 3.8.5, k8s 1.19.4. Trying to run "ansible-playbook -i inventory/prod/hosts.yml -b upgrade-cluster.yml -e kube_version=v1.20.4 -K -v " gives me that error.
The k8s 1.24 is with containerd. The snapshots subfolder got deleted hence Control plane master KubeScheduler is not coming up. Here is the msg. Any suggestion how to recover. kube-scheduler: failed to create containerd container: failed to create prepare snapshot dir : stat /data/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots: no such file or directory Warning BackOff kubelet Back-off restarting failed container
Good video, nice and clear.
I am on 11.9 and need to get to 15.3. From what I have read, I have to go to 12 then 13 then 14 then 15. That is a lot of files to config for each version of kubespray.
Hi Mathew, thats what I too understood from the documentation. But its very unusual that in a production real world situation anyone would jump from 11.x to 15.x. Slow incremental upgrade is fine. Because there will be lots of changes between these two versions.
Great video Venkat, tks!!
Thanks Leonardo
Thank you Venkat
Hi Murat, thanks for watching.
Thank you very much, awesome
Hi Olivier, thanks for watching.
How to renew kubespray Kubernetes Cluster certificate.I' getting Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2023-07-13T12:32:50Z is after 2023-07-12T10:37:48Z
this error while accessing Kubespray K8 cluster.
Nice video!
Hi Mauricio, thanks for watching.
Thank you for the video.
Can I use the same steps to update the patch version, and not the minor version? and what happens with certificates? Are new certificates generated for kubelets and other cluster elements when updating?
Hi, thanks for watching. I guess the certificates will be re-issues when upgrading but I am not sure. Haven't looked at the certificates after upgrading.
Hey, nice video, what about the kubespray versions you used (initial install and upgrade) Thx !
If I could, give 5 like for your simplicity on explain
HI Adonai, many thanks for watching this video.
Hi Venkat, I have 8 node cluster HA mode and i want to upgrade the same from 1.11 to 1.12 so i have one query if upgrade fails or something wrong happen with cluster do we have rollback option available for this as well through kubespray....
Hi Nitin, thanks for watching. I just glanced at the documentation and there was no clear instructions on rollback. I guess when the upgrade fails, you will have to update the playbook to older version and re-run it. The node that was partially updated and failed will be rolled back while other nodes that haven't been upgraded will not be touched as you know Ansible is idempotent.
Hi Venkat , Thanks for the video . I have one query regarding update from v1.16 to v1.18. Though i could able to upgrade from v1.15 to v1.16 but not able to upgrade the same cluster to v1.18. I saw the file roles/default/download/main.yml there is not entry for v1.18. Can you suggest what i need to do?
Hi Pawan, thanks for watching. So you could upgrade from 1.15 to 1.16 and not from 1.16 to 1.18. Have you tried going through 1.17?
what happen to inside cluster certificate?
How to renew certificate using kubespray
Please help
Hi , there are multiple errors coming to run the playbook, for example fatal: [localhost]: FAILED! => {"msg": "template error while templating string: expected token '=', got 'end of statement block'. String: {% set test %}It works{% endset %}{{ test == 'It works' }}"}
Hi Venkat, i have a question here, if for some reason ansible fails to upgrade any of the worker node or master node, would ansible playbook rollback to older version?
HI Kasim, thanks for watching. I don't think it will rollback any changes. Its an automation tool and does what it is told to do :) If for some reason a node fails during the upgrade or the upgrade fails on that node, understand why it failed and rectify it or just remove and add the node. There are ansible playbooks to remove a node and re-add it by updating the inventory file. This will be covered in tomorrow's video. Thanks.
@@justmeandopensource thanks Venkat
@@kasimshaik You are welcome. Cheers
Remember Kasim, this playbook is only valid for cluster provisioned by itself.
Absolutely.
Can we configure kubespray to manage existing cluster not deployed from kubespray. if i installed k8s using kubeadm, can i manage (add,delete,upgrade) using kubespray.
Hi Raj, thanks for watching. Although you can do it, it will be a whole lot of work. You can modify the playbooks accordingly as per your existing Kubernetes deployment. You can do a dry run to see what ansible (Kubespray) will change in your cluster.
@@justmeandopensource Thanks for the reply. What tool would you recommend i.e., kubeadm or kubespray to provision k8s cluster in bare metal for production?
@@ravipacc I would use Kubespray. Kubeadm is manual method. Infact kubespray uses kubeadm to provision the cluster but through automation using ansible playbooks.
can I configure kubespray to manage existing Kubernetes cluster provisioned with kubeadm?
The goal is to upgrade the Kubernetes cluster using kubespray, which is provisioned using ansilbe+ kubeadm.
I really appreciate it if you can help me solving this issue
Hello congratulations for the video, I saw in the documentation that there is a safe upgrade and an insecure upgrade. What would that be in this case?
I also saw that in the documentation they pass a parameter -e
Example below:
ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.19.7 -e upgrade_cluster_setup=true
Does any one have this error: 'dict object' has no attribute 'v1.20.4'.
I am on Ansible 2.9.6, python 3.8.5, k8s 1.19.4. Trying to run "ansible-playbook -i inventory/prod/hosts.yml -b upgrade-cluster.yml -e kube_version=v1.20.4 -K -v " gives me that error.
The k8s 1.24 is with containerd.
The snapshots subfolder got deleted hence Control plane master KubeScheduler is not coming up. Here is the msg. Any suggestion how to recover.
kube-scheduler: failed to create containerd container: failed to create prepare snapshot dir : stat /data/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots: no such file or directory Warning BackOff kubelet Back-off restarting failed container
I honestly only use tools you talk about.