search

kubernetes / cloud-provider-openstack

Apache License 2.0
619 stars 610 forks source link

[occm] multi AZ support (without L2 connectivity) for octavia #1298

Closed zetaab closed 3 years ago

zetaab commented 4 years ago

Is this a BUG REPORT or FEATURE REQUEST?: feature

/kind feature

What happened: Now when octavia do have AZ support when provisioning loadbalancers, could we support somekind of topologies when doing loadbalancers? Example: 3 network AZs without L2 between them, which means that floatingips does not move between zones.

What you expected to happen:

I have been thinking to situation that when we provision loadbalancer, it could automatically create loadbalancers to each zone in background (means that instead of 1 IP we do have 3 IPs with 3 zones). My plan was that we could use similar stuff that ELB does: it creates dns name against these zone loadbalancer IPs and monitor them, and remove IPs if the zone is down (TTL is 60seconds). The problem is that at least we would like to use external dns to this instead of designate.

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten

fejta-bot commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

k8s-ci-robot commented 3 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes/cloud-provider-openstack/issues/1298#issuecomment-809173138): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.