[occm] Allow using internal network ID instead of name in configuration

[pgaxatte]

/kind feature

What happened:

Network names can be modified and when this happens the openstack cloud-controller-manager fails to manage network components. The solution is to edit the configuration and reload the occm.

What you expected to happen:

I would expect a way to configure the occm without relying on the network name and propose to add an internal-network-id configuration field.

How to reproduce it:

Configure occm, rename your network, grab popcorn, watch the world burn.

Anything else we need to know?:

N/A

Environment:

• openstack-cloud-controller-manager(or other related binary) version: latest
• OpenStack version: latest
• Others:

[pgaxatte]

By the way the issue is the same with the public network but this one never changes in our infra so it's less impactful for us.

But it would be nice to have both options (name and ID) for public and internal networks.

[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