Adopt CAPI v1beta2 conditions

[chrischdi]

trafficstars

Describe the solution you'd like

TODOs to adopt v1beta2 conditions in CAPV

• [ ] add API types for v1beta2 to v1beta1 status
• [ ] Implement conditions
  • [ ] Paused
    • [ ] Replace usage of ClusterUnpausedAndInfrastructureReady
  • [ ] ...

cc @fabriziopandini @sbueringer

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

Environment:

• Cluster-api-provider-vsphere version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[sbueringer]

Thx!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sbueringer]

/remove-lifecycle stale

[sbueringer]

cc @chrischdi Let's close this tomorrow :)

[chrischdi]

/close

We will do a round of manual validation though.

[k8s-ci-robot]

@chrischdi: Closing this issue.

In response to this:

/close

We will do a round of manual validation though.

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-sigs/prow repository.