Closed jeremytourville closed 3 years ago
@jeremytourville It's hard to say what's happening here without seeing the play or task that is failing. This seems like the problem is with the https://galaxy.ansible.com/geerlingguy/k8s more than something in the modules of this collection though. According to Galaxy, @geerlingguy hasn't made a release of that content in 8 months. We've made a few significant releases of this content in that time though.
I'd suggest trying what's in that content's source repo and go from there to determine wherein lies the problem.
I greatly appreciate the comment to help troubleshoot. I hadn't thought of getting the latest from the content source repo. I'll try that and report back. I did update the failure to reflect which play/task was failing. I'm also glad you pointed out the last update is old relative to the K8s content updates. I think I was focused on finding a role that had a good score vs staying current.
ok, I found a newer kubernetes roles to run https://galaxy.ansible.com/geerlingguy/kubernetes and was able to get the master built without issue. I'd expect the nodes should go smoothly at this point. I am satisfied to close this. Thanks again!
@jeremytourville - Yeah, sorry about that—note that my collections on galaxy are a lot harder to maintain than the individual roles, so for the time being I am a lot more lazy about updating them (it's like a 4 part process right now).
Stick to the individual roles instead. (Annoyingly, Ansible Galaxy lists collections before roles in searches, which gives them some sort of implied superiority...)
SUMMARY
K8s module fails stating name is required to patch v1.Namespace I am running the following playbook https://galaxy.ansible.com/geerlingguy/k8s
ISSUE TYPE
COMPONENT NAME
!component =lib/ansible/modules/clustering/k8s/k8s.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
ansible control node
CentOS Linux release 8.2.2004 (Core)
target host being configured
CentOS Linux release 8.3.2011
kubectl verison
STEPS TO REPRODUCE
run playbook connecting to target
ansible-playbook kubernets_cluster.yml --ask-pass -k -vvv
(unsure what I can do further to debug/troubleshoot)EXPECTED RESULTS
playbook should complete
ACTUAL RESULTS