Allow network offering to be configurable

[hrak]

/kind feature

Describe the solution you'd like

NetOffering is currently hardcoded as DefaultIsolatedNetworkOfferingWithSourceNatService, but in some setups, these network offerings have been customized and DefaultIsolatedNetworkOfferingWithSourceNatService is not available.

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

Environment:

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

[pmotyka]

Thanks for filing, this seems reasonable and straightforward. Will keep you posted on a resolution timeframe.

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[hrak]

/remove-lifecycle rotten

[thiagolinhares]

hello guys, any update on this issue? It's a feature we would like very much.
Also VPC support, but might be a completely different thread.

[hrak]

I tried implementing this as a setting to CloudStackIsolatedNetwork but ran into a chicken-egg issue with the failure domain waiting for the network to be ready and the network waiting for the failure domain. Need more time to see how we can make defining an explicit CloudStackIsolatedNetwork work (currently most use-cases rely on the network either being there already or being auto-created if it doesnt exist)

[g-gaston]

Moving to v0.5.0 since this is a new feature and we are only prioritizing vital bugfixes for v0.4.9