Upgrade Kubernetes from v1.26.12 to v1.27.0 with add-ons in a Single-Node Cluster Using Kubespray v2.25 · kubernetes-sigs/kubespray#11498

Metriche repository

Star: (10.380 star)
Metriche merge PR: (Merge medio 25g) (26 PR mergiate in 30 g)

Descrizione

What happened?

I have a single-node cluster with Kubernetes v1.26.12 installed using Kubespray 2.23. I am trying to upgrade the Kubernetes version to v1.27.0 using upgrade_cluster.yml playbook from Kubespray v2.25, with the following variables passed in a file 'k8s_var.yml' (using -e flag):

kube_version: "v1.27.0" deploy_container_engine: false skip_http_proxy_on_os_packages: true dashboard_enabled: false helm_enabled: true kube_network_plugin: "calico" kube_service_addresses: "10.233.0.0/18" kube_pods_subnet: "10.233.64.0/18" metallb_enabled: true metallb_speaker_enabled: true metallb_namespace: "metallb-system" kube_proxy_strict_arp: true kube_proxy_mode: 'iptables' metallb_config: address_pools: primary: ip_range: - "10.11.0.100-10.11.0.150" auto_assign: true layer2: - primary

However, the playbook fails with the below error:

The metallb-speaker pod is running but metallb-controller pod is in Pending state.

Additionally, metallb-controller pod events reports: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling (I am assuming since the node is in cordoned state, it is marked as unavailable for scheduling new pods. Hence the above error)

What did you expect to happen?

The upgrade_cluster.yml should have executed successfully, when metallb is enabled on the cluster.

How can we reproduce it (as minimally and precisely as possible)?

Deploy Kubernetes v1.26.12 (using Kubespray 2.23) on a single-node cluster.
Clone Kubespray 2.25 source code on the node
Create a vars file - 'k8s_var.yml' and keep the following variables:

kube_version: "v1.27.0" deploy_container_engine: false skip_http_proxy_on_os_packages: true dashboard_enabled: false helm_enabled: true kube_network_plugin: "calico" kube_service_addresses: "10.233.0.0/18" kube_pods_subnet: "10.233.64.0/18" metallb_enabled: true metallb_speaker_enabled: true metallb_namespace: "metallb-system" kube_proxy_strict_arp: true kube_proxy_mode: 'iptables' metallb_config: address_pools: primary: ip_range: - "10.11.0.100-10.11.0.150" auto_assign: true layer2: - primary

Create an inventory - k8s_inv.ini as shown below:

[kube_control_plane] localhost ansible_connection=local

[kube_node] localhost ansible_connection=local

[etcd] localhost ansible_connection=local

[k8s_cluster] localhost ansible_connection=local

Run the upgrade_cluster.yml playbook using below command: ansible-playbook upgrade-cluster.yml -b -i /k8s_inv.ini -e @/k8s_var.yml

OS

Ubuntu 22.04.3 LTS VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy

Version of Ansible

ansible [core 2.16.10] config file = None configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/local/lib/python3.11/dist-packages/ansible ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections executable location = /usr/local/bin/ansible python version = 3.11.9 (main, Apr 6 2024, 17:59:24) [GCC 11.4.0] (/usr/bin/python3.11) jinja version = 3.1.4 libyaml = False

Version of Python

3.11.9

Version of Kubespray (commit)

0d09b19c6

Network plugin used

calico

Full inventory with variables

Trying to upgrade kubernetes version running on the control plane using below inventory: