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.

Sign up for GitHub

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

Jump to bottom

Update docs to use v1beta2 API instead of v1beta1 #1731

Closed
xmudrii opened this issue Jan 10, 2022 · 0 comments · Fixed by kubermatic/docs#906
Closed

Update docs to use v1beta2 API instead of v1beta1 #1731

xmudrii opened this issue Jan 10, 2022 · 0 comments · Fixed by kubermatic/docs#906
Assignees
@xmudrii
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/high sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Milestone
KubeOne 1.4

Comments

@xmudrii
Copy link
Member

xmudrii commented Jan 10, 2022

What feature would you like to be added?

Docs are currently based on the v1beta1 API. Considering that the v1beta1 API is deprecated, we should update docs to use the v1beta2 API.

What are use cases of the feature?

  • The v1beta2 API is used in docs

Relevant to #1539
@xmudrii xmudrii added kind/documentation Categorizes issue or PR as related to documentation. priority/high sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Jan 10, 2022
@xmudrii xmudrii added this to the KubeOne 1.4 milestone Jan 10, 2022
@xmudrii xmudrii self-assigned this Jan 14, 2022
@xmudrii xmudrii mentioned this issue Jan 14, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xmudrii xmudrii

Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/high sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Projects
None yet
Milestone
KubeOne 1.4
Development

Successfully merging a pull request may close this issue.

Update the KubeOne docs to use the v1beta2 API instead of v1beta1 xmudrii/docs
1 participant
@xmudrii