Open Nurlan199206 opened 4 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
What happened?
What did you expect to happen?
installed cluster
How can we reproduce it (as minimally and precisely as possible)?
3 master node, 2 worker nodes
OS
Ubuntu 22.04
Version of Ansible
2.16.9
Version of Python
3.10.12
Version of Kubespray (commit)
2d194af85
Network plugin used
calico
Full inventory with variables
Command used to invoke ansible
ansible-playbook -i /home/nurlan/kubespray/inventory/mycluster/hosts.yaml -bkK -u nurlan --become-user=root cluster.yml
Output of ansible run
Anything else we need to know
No response