Skip to content

move from k8s.io to x-k8s.io #407

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

Closed
jichenjc opened this issue Jul 24, 2019 · 4 comments
Closed

move from k8s.io to x-k8s.io #407

jichenjc opened this issue Jul 24, 2019 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@jichenjc
Copy link
Contributor

/kind bug

see
kubernetes-sigs/cluster-api#1073

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api version:
  • Minikube/KIND version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 24, 2019
@sbueringer
Copy link
Member

I think we should do this with v1alpha2 like CAPA. I don't think we have to migrate our v1alpha1 resource

@sbueringer
Copy link
Member

I would close this issue in favor of: #380 (comment) to not complicate it any further :)

@sbueringer
Copy link
Member

We can close this as the first v1alpha2 PR (which also did this) was merged

@sbueringer
Copy link
Member

@jichenjc

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

No branches or pull requests

3 participants