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

Investigate the issue with the kube-apiserver not serving all resource on Kubernetes 1.20 clusters #1222

Closed
xmudrii opened this issue Jan 20, 2021 · 2 comments
Assignees
Labels
Epic kind/bug Categorizes issue or PR as related to a bug. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Milestone

Comments

@xmudrii
Copy link
Member

xmudrii commented Jan 20, 2021

No description provided.

@xmudrii xmudrii changed the title Investigate the issue with the kube-apiserver not serving all resource for Kubernetes 1.20 clusters Investigate the issue with the kube-apiserver not serving all resource on Kubernetes 1.20 clusters Jan 20, 2021
@xmudrii xmudrii self-assigned this Jan 20, 2021
@xmudrii xmudrii added kind/bug Categorizes issue or PR as related to a bug. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Jan 20, 2021
@slamdev
Copy link

slamdev commented Jan 27, 2021

@xmudrii does it affect 1.21 as well? from release notes of v1.2.0-beta.0 it is unclear if it's safe to use 1.21 or not...

@xmudrii
Copy link
Member Author

xmudrii commented Jan 27, 2021

@slamdev Kubernetes 1.21 is currently under development, so it's not possible to provision 1.21 clusters with KubeOne. This appears to be an upstream issue and we're currently investigating what might cause it and how to fix it. We'll report back here once we have some additional details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic kind/bug Categorizes issue or PR as related to a bug. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Projects
None yet
Development

No branches or pull requests

4 participants