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 cluster-api from to 1.2.1 #807

Closed
mkumatag opened this issue Aug 13, 2022 · 0 comments · Fixed by #809
Closed

bump cluster-api from to 1.2.1 #807

mkumatag opened this issue Aug 13, 2022 · 0 comments · Fixed by #809
Assignees
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Milestone

Comments

@mkumatag
Copy link
Member

/kind cleanup
/area provider/ibmcloud

What steps did you take and what happened:
New tag is created here - https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.2.1 but release is yet to be created, once we have release created and the images pushed lets update the version to 1.2.1 wherever required.

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):
@mkumatag mkumatag added this to the 0.3 milestone Aug 13, 2022
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/provider/ibmcloud Issues or PRs related to ibmcloud provider labels Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants