Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes 1.30 Support #11109

Closed
yankay opened this issue Apr 23, 2024 · 2 comments · Fixed by #11343
Closed

Kubernetes 1.30 Support #11109

yankay opened this issue Apr 23, 2024 · 2 comments · Fixed by #11343
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@yankay
Copy link
Member

yankay commented Apr 23, 2024

What would you like to be added

Kubernetes 1.30 Support

Why is this needed

Kubernetes 1.30 is released, so the kubespray can support it. See:

I think the target version of kubespray will be 2.25.0

@yankay yankay added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 23, 2024
@yankay yankay mentioned this issue Apr 24, 2024
@mvarendorff2
Copy link

Out of curiosity: With 2.25.0 having been released, would the new target version be 2.25.x or 2.26.0?

tmurakam added a commit to tmurakam/kubespray that referenced this issue May 29, 2024
tmurakam added a commit to tmurakam/kubespray that referenced this issue Jun 4, 2024
Add hashes to crictl, crio, kubelet, kubectl and kubeadm
tmurakam added a commit to tmurakam/kubespray that referenced this issue Jun 19, 2024
Add hashes to crictl, crio, kubelet, kubectl and kubeadm
tmurakam added a commit to tmurakam/kubespray that referenced this issue Jun 20, 2024
Add hashes to crictl, crio, kubelet, kubectl and kubeadm
k8s-ci-robot pushed a commit that referenced this issue Jul 2, 2024
Add hashes to crictl, crio, kubelet, kubectl and kubeadm
@bogd
Copy link
Contributor

bogd commented Jul 3, 2024

Just tested this (I have been waiting for the PR to be merged for a while :) ), and the upgrade of an existing cluster breaks here:

TASK [kubernetes/control-plane : Kubeadm | Upgrade first master] ************************************************
Wednesday 03 July 2024  17:18:34 +0000 (0:00:01.906)       0:31:56.562 ******** 
FAILED - RETRYING: [k8s-staging-01-master]: Kubeadm | Upgrade first master (3 retries left).
FAILED - RETRYING: [k8s-staging-01-master]: Kubeadm | Upgrade first master (2 retries left).
FAILED - RETRYING: [k8s-staging-01-master]: Kubeadm | Upgrade first master (1 retries left).
fatal: [k8s-staging-01-master]: FAILED! => {"attempts": 3, "changed": true, "cmd": ["timeout", "-k", "600s", "600s", "/usr/local/bin/kubeadm", "upgrade", "apply", "-y", "v1.30.2", "--certificate-renewal=True", "--config=/etc/kubernetes/kubeadm-config.yaml", "--ignore-preflight-errors=all", "--allow-experimental-upgrades", "--etcd-upgrade=false", "--force"], "delta": "0:00:00.083731", "end": "2024-07-03 17:18:55.750605", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2024-07-03 17:18:55.666874", "stderr": "can not mix '--config' with arguments [allow-experimental-upgrades certificate-renewal etcd-upgrade force yes]\nTo see the stack trace of this error execute with --v=5 or higher", "stderr_lines": ["can not mix '--config' with arguments [allow-experimental-upgrades certificate-renewal etcd-upgrade force yes]", "To see the stack trace of this error execute with --v=5 or higher"], "stdout": "", "stdout_lines": []}

Upgrading from v1.29.3 to v1.30.2, using ansible 2.16.8.

Opened #11350 to track this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants