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

Bump clusterctl metadata to v1beta1 #1256

Closed
Tracked by #1249
randomvariable opened this issue Sep 24, 2021 · 2 comments
Closed
Tracked by #1249

Bump clusterctl metadata to v1beta1 #1256

randomvariable opened this issue Sep 24, 2021 · 2 comments
Labels
area/release kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@randomvariable
Copy link
Member

/kind feature
/area release
/milestone v0.8.0
/priority important-soon

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
For v1beta1 support, we should bump our metadata to v1beta1

Anything else you would like to add:

Depends on #1252
Depends on #1253

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/release priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 24, 2021
@randomvariable randomvariable added this to the v0.8.0 milestone Sep 24, 2021
@gab-satchi
Copy link
Member

fixed by #1263
/close

@k8s-ci-robot
Copy link
Contributor

@gab-satchi: Closing this issue.

In response to this:

fixed by #1263
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants