Timeout for waiting for MetalLB pod contatiner should be increased

[abhishek-sa1]

What happened?

Currently the timeout set for metallb pods to be in running state is 2m.

What I have observed is sometimes it takes little more than 2m for pods to be up and because of the timeout set, the playbook fails with error msg.

Can we have a timeout set using some variable which can be customizable? Or can we increase the timeout?
I am importing cluster.yml playbook as an ansible collection and because of failure in metallb waiting, my calling playbook is failing which i need to avoid.

What did you expect to happen?

metallb waiting time should be configurable/ If the metallb pods are not up, metallb installation should fail and other tasks in cluster.yml should proceed.

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

not reproduceable always. running cluster.yml.

OS

root@lilycp:~# uname -srm
Linux 5.15.0-78-generic x86_64

root@lilycp:~# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
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

root@lilycp:~# ansible --version
ansible [core 2.14.15]
config file = None
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.9/dist-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.9.18 (main, Aug 25 2023, 13:20:14) [GCC 11.4.0] (/usr/bin/python3.9)
jinja version = 3.1.2
libyaml = True

Version of Python

3.9.18

Version of Kubespray (commit)

kubernetes_sigs.kubespray ansible collection 2.23.2

Network plugin used

calico

Full inventory with variables

kube_version: "v1.26.12"
container_manager: "containerd"
dashboard_enabled: true
helm_enabled: true
kube_network_plugin: "calico"
metallb_enabled: true
metallb_speaker_enabled: true
kube_proxy_strict_arp: true
kube_proxy_mode: 'iptables'
override_system_hostname: false
populate_inventory_to_hosts_file: false
enable_nodelocaldns: false
unsafe_show_logs: true

Command used to invoke ansible

through collections

Output of ansible run

Anything else we need to know

No response

[abhishek-sa1]

Raised new issue as this is closed #11098

[tico88612]

Extending the timeout is fine with me, but I'm wondering if there is a need for blocking?
Maybe additional app installations don't require failing the entire playbook?