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

update gomega #945

Closed
mkumatag opened this issue Nov 3, 2022 · 1 comment · Fixed by #952
Closed

update gomega #945

mkumatag opened this issue Nov 3, 2022 · 1 comment · Fixed by #952
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.

Comments

@mkumatag
Copy link
Member

mkumatag commented Nov 3, 2022

/kind cleanup
/area provider/ibmcloud

What steps did you take and what happened:
update gomega, currently depends on kubernetes-sigs/cluster-api#7458

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 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 Nov 3, 2022
@Amulyam24
Copy link
Contributor

@mkumatag , this has been taken care of in the latest gomega update -#952

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