[OCCM] Add --cluster-name=$(CLUSTER_NAME) support

[jichenjc]

What this PR does / why we need it:

Which issue this PR fixes(if applicable):
fixes #1807

Special notes for reviewers:

Release note:

NONE

[jichenjc]

/retest-required

[k8s-ci-robot]

@jichenjc: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
openstack-cloud-controller-manager-e2e-conformance-test	2875856	link	true	/test openstack-cloud-controller-manager-e2e-conformance-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[lingxiankong]

I don't think using nodeName is a good idea, maybe just set a default value kubernetes?

[lingxiankong]

/lgtm

[ramineni]

Thanks.

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ramineni

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ramineni]

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

[powellchristoph]

Could we get a new Chart version? I've run into this exact problem.

[jichenjc]

@lingxiankong @ramineni does this need a bump of OCCM version (e.g 1.23=>1.23.1 )
or a separate flow of release a new chart? I didn't do it personally before and I can do it if any doc we have

[lingxiankong]

As we are still in the dev cycle, it's not possible to do a chart release given the code is not officially released, and this change is kind of "new feature", so it doesn't fit into the backport policy neither. We have to wait until the next release.