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

Decide what API group should be used for the v1 API #1548

Closed
xmudrii opened this issue Sep 28, 2021 · 2 comments
Closed

Decide what API group should be used for the v1 API #1548

xmudrii opened this issue Sep 28, 2021 · 2 comments
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API 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 Sep 28, 2021

We were discussing using <product-name>.k8c.io API groups (e.g. kubermatic.k8c.io). Considering we're currently using the kubeone.io API group, we should decide do we want to keep it or switch to kubeone.k8c.io.
@xmudrii xmudrii added kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API priority/high sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Sep 28, 2021
@xmudrii xmudrii added this to the KubeOne 1.4 milestone Sep 28, 2021
@xmudrii
Copy link
Member Author

xmudrii commented Sep 28, 2021

xref #1539

@kron4eg
Copy link
Member

kron4eg commented Dec 3, 2021

@xmudrii Seems like it’s done

@kron4eg kron4eg closed this as completed Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API 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

No branches or pull requests
2 participants
@kron4eg @xmudrii