[occm] Unable to use Loadbalancer Classes in Helm Chart

[shaardie]

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:

Due to the helper Script in the Helm Chart, it is not possible to create Loadbalancer Classes as own Sections in the cloudConfig.

What you expected to happen:

That I can define my own Loadbalancer Classes in the Helm Chart.

How to reproduce it:

Try to define Loadbalancer Class in the Helm Chart cloudConfig

Anything else we need to know?: Wouldn't it be easier to skip the whole templating stuff and simply putting the content of cloudConfig into the secret?

Something like:

cloudConfig: |-
    [Global]
    auth-url=...
    application-credential-id=...
    ...
    [LoadBalancer]
    network=...
    subnet-id=...
    ...
    [LoadBalancerClass "ipv6"]
    network-id=...
    ...

[zakthan]

I have the exact same issue I have prepared this PR for that: https://github.com/kubernetes/cloud-provider-openstack/pull/1950 It worked for me

[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

[Lirt]

Fix for this issue was merged in https://github.com/kubernetes/cloud-provider-openstack/pull/1953.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[shaardie]

As far as I understood it, this is already fixed with https://github.com/kubernetes/cloud-provider-openstack/pull/1953. So closing is okay.