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

Issue upgrading Kubernetes cluster from 1.26 to 1.27 due to expired APT keys #3460

Open
BerkayIlhan opened this issue Nov 13, 2024 · 3 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/regression Categorizes issue or PR as related to a regression from a prior release. priority/normal Not that urgent, but is important sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.

Comments

@BerkayIlhan
Copy link

BerkayIlhan commented Nov 13, 2024

I'm experiencing an issue while upgrading my Kubernetes cluster from version 1.26 to 1.27 with KubeOne. The old APT keys required for the upgrade have expired, blocking the process. I see that a fix is available using a new key, as discussed in kubernetes/release issue #3818 , but this update hasn’t been integrated into KubeOne yet. Could you please update the key in KubeOne or suggest a workaround?

Thanks for your help!

@xmudrii
Copy link
Member

xmudrii commented Nov 13, 2024

Hello @BerkayIlhan, thanks for the report!

As described in the upstream issue, this is because the Kubernetes v1.27 repository doesn't have the latest GPG key. KubeOne is always downloading the key from the repository for the target Kubernetes version (v1.27 in your case).

Unfortunately, there's no easy way to mitigate this within KubeOne, but we're working with the upstream community to fix this as soon as possible. If it doesn't get fixed by the end of the week, we'll issue a fix for KubeOne to mitigate this issue.

Thank you for your patience!

/assign

@xmudrii xmudrii added priority/high sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. kind/regression Categorizes issue or PR as related to a regression from a prior release. release-blocker labels Nov 13, 2024
@BerkayIlhan
Copy link
Author

Any update on this?

@xmudrii
Copy link
Member

xmudrii commented Jan 6, 2025

I don't have capacity to work on this issue at the moment, but if anyone would like to pick it up, I would be happy to provide guidance!
/unassign
/good-first-issue

@xmudrii xmudrii added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. priority/normal Not that urgent, but is important and removed priority/high labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/regression Categorizes issue or PR as related to a regression from a prior release. priority/normal Not that urgent, but is important sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Projects
None yet
Development

No branches or pull requests

2 participants