You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to add a feature-gates and enable authentication.k8s.io/v1alpha1 using the role but I couldn't.
I installed my cluster using tag: 1.37.0 of the lablabs/ansible-role-rke2 and now I want to add add a feature-gates and enable authentication.k8s.io/v1alpha1 using re-play the deployment playbook. this is my deployment playbook:
included: /Projects/Kubernetes-Lab/roles/ansible-role-rke2/tasks/change_config.yml for kuber-1 => (item=kuber-1)
included: /Projects/Kubernetes-Lab/roles/ansible-role-rke2/tasks/change_config.yml for kuber-2 => (item=kuber-2)
included: /Projects/Kubernetes-Lab/roles/ansible-role-rke2/tasks/change_config.yml for kuber-3 => (item=kuber-3)
TASK [ansible-role-rke2 : Restart RKE2 service on kuber-1] *************************************************************************************
And stuck here. Restarting master node 1 is not successful. the rke2-server service can not started due to these logs:
Nov 01 14:54:46 kuber-1 rke2[699]: time="2024-11-01T14:54:46+03:30" level=info msg="Container for etcd is running"
Nov 01 14:54:46 kuber-1 rke2[699]: time="2024-11-01T14:54:46+03:30" level=info msg="Container for kube-apiserver not found (no matching container found), retrying"
Nov 01 14:54:48 kuber-1 rke2[699]: time="2024-11-01T14:54:48+03:30" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
Nov 01 14:54:53 kuber-1 rke2[699]: time="2024-11-01T14:54:53+03:30" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
Nov 01 14:54:56 kuber-1 rke2[699]: time="2024-11-01T14:54:56+03:30" level=info msg="Waiting for API server to become available"
Nov 01 14:54:58 kuber-1 rke2[699]: time="2024-11-01T14:54:58+03:30" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
Nov 01 14:55:02 kuber-1 rke2[699]: time="2024-11-01T14:55:02+03:30" level=info msg="Waiting for API server to become available"
Nov 01 14:55:03 kuber-1 rke2[699]: time="2024-11-01T14:55:03+03:30" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
But new configs are placed in /etc/rancher/rke2/config.yaml :
Summary
I wanted to add a feature-gates and enable authentication.k8s.io/v1alpha1 using the role but I couldn't.
I installed my cluster using tag: 1.37.0 of the lablabs/ansible-role-rke2 and now I want to add add a feature-gates and enable authentication.k8s.io/v1alpha1 using re-play the deployment playbook. this is my deployment playbook:
Playbook ran until these tasks:
And stuck here. Restarting master node 1 is not successful. the rke2-server service can not started due to these logs:
But new configs are placed in /etc/rancher/rke2/config.yaml :
Also apparmor and ufw service are disabled and stopped.
How can I solve this issue?
Issue Type
Bug Report
Ansible Version
Steps to Reproduce
Expected Results
kubectl auth whoami become available. but rke2-server is not available after new args.
Actual Results
The text was updated successfully, but these errors were encountered: