🐛 allow switching from filter.name to id of network and subnets in OSC spec

[k8s-infra-cherrypick-robot]

This is an automated cherry-pick of #2518

/assign mnaser

/cherrypick release-0.11 release-0.10

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name	Link
🔨 Latest commit	c81d89e
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/681e0d2ae810bd0008dcc9b7
😎 Deploy Preview	https://deploy-preview-2540--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mnaser]

/lgtm

[lentzi90]

Technically we should not backport "features" (:sparkles: ). On the other hand, we can probably consider this a bug :bug: and then it is fine to backport

[mnaser]

I think it's more of a bug than a feature to be honest, since this blocks our ability to upgrade clusters when we transitioned to using IDs instead of names to be honest.

[lentzi90]

/retitle [release-0.12] 🐛 allow switching from filter.name to id of network and subnets in OSC spec

[lentzi90]

/retitle 🐛 allow switching from filter.name to id of network and subnets in OSC spec

[lentzi90]

/approve
I'm fine treating this as a bug also

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [lentzi90]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-infra-cherrypick-robot]

@k8s-infra-cherrypick-robot: new pull request created: #2541

Details

In response to this:

This is an automated cherry-pick of #2518

/assign mnaser

/cherrypick release-0.11 release-0.10

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.