[occm] Annotation for member-subnet-id (revisit)

[shaardie]

This is a revisit of the Issue #1086, because the original author closed that issue.

IMHO it would be a great idea to explicit configure the subnet of the loadbalancer and be able to set the loadbalancer in an external subnet, e.g. for IPv6.

I know there is a workaround as described in https://github.com/kubernetes/cloud-provider-openstack/issues/1086#issuecomment-650176521, but it not very easy to understand and will break silently if somebody changes the internal behavior of this.

I would propose to make a proper feature out of this with a meaningful configuration in the cloud config and also as annotation, something like loadbalancer.openstack.org/member-subnet-id. It would also makes it easier to configure IPv6 loadbalancer in an multi-tenant environment.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[shaardie]

Too bad, I am still very interested in this issue and would also be willing to help here.

/remove-lifecycle stale

[shaardie]

Also for internal Loadbalancer the suggested workaround does not work anymore, since classes can not be used, see #1961