v1beta1-compatible util functions in v0.11

[pierreprinetti]

I am trying to rebase cluster-api-provider-openstack onto cluster-api v1.11 and I noticed that while some v1beta1 util functions have been saved in util/deprecated/v1beta1 for posterity (thank you!), many are lost.

Would it be possible to save more v1beta1-compatible util functions in util/deprecated/v1beta1? In our case we'd be happy with these packages (I am using the path they had in v1.10.3):

• util
• util/annotations
• util/collections
• util/predicates

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[fabriziopandini]

See #12441 (comment)

[fabriziopandini]

/close

As per kubernetes-sigs/cluster-api-provider-openstack#2611 (comment)

That is: CAPO controllers will consume CAPI v1beta2 objects, but will themselves continue to publish infra objects conforming to CAPI v1beta1. We've been set a deadline of August next year to move to v1beta2, though, so we should probably get on that.

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

/close

As per kubernetes-sigs/cluster-api-provider-openstack#2611 (comment)

That is: CAPO controllers will consume CAPI v1beta2 objects, but will themselves continue to publish infra objects conforming to CAPI v1beta1. We've been set a deadline of August next year to move to v1beta2, though, so we should probably get on that.

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.