Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[occm] Multi region support information #2543

Closed
sebastienmusso opened this issue Feb 8, 2024 · 4 comments
Closed

[occm] Multi region support information #2543

sebastienmusso opened this issue Feb 8, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@sebastienmusso
Copy link

sebastienmusso commented Feb 8, 2024

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
We are currently testing kubernetes deployment on several openstack clusters.
We deployed one occm by openstack and enabled OS_CCM_REGIONAL.
OCCM is mostly used for cloud-node and cloud-node-lifecycle services

What you expected to happen:
All seems to work as expected, az1 occm delete node with az1 prefix in providerID field as expected.
Node are added to the cluster with the right provider ID

Anything else we need to know?:
What is missing in order to consider this feature as GA ?
is this testing case ?
How could we help for this suject

Environment:

  • openstack-cloud-controller-manager version: v1.29.0
  • OpenStack version: Queen (17.6.0)
  • Others: kubernetes 1.26.10 / 1.27.8
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 8, 2024
@sebastienmusso sebastienmusso changed the title [OCCM] Multi region support information [occm] Multi region support information Feb 8, 2024
@dulek
Copy link
Contributor

dulek commented Feb 8, 2024

What makes you think this is not a supported thing? Anyway if you want to contribute to this feature, we certainly don't have a CI job testing it, so that sounds like a fair first step.

@sebastienmusso
Copy link
Author

sebastienmusso commented Feb 8, 2024

@dulek
the "alpha" in occm doc
make me think that

@dulek
Copy link
Contributor

dulek commented Feb 8, 2024

@dulek the "alpha" in occm doc make me think that

Ah, here it is! Well, looks like nobody looked at this for 2 years, it should be out of alpha by this time, though I'm not sure how many installations do that and how production-proven it is.

My idea to move forward would probably be to ask about the feature on the #provider-openstack on the K8s Slack. As a next step let's also make it a general option and not just a hacky env var. Then I guess we can assume that we'll try fixing issues as we go. And obviously my CI remark still stays.

@sebastienmusso
Copy link
Author

Happy to ear that @dulek

let me look at the CI process and maybe submit a pr (with doc up to date)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants