Remove etcd LB
Bug #1775684 reported by
Feilong Wang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
In Progress
|
Undecided
|
Feilong Wang | ||
Bug Description
Based on current design, Magnum will create LB with VIP for etcd. However, given the etcd cluster is created for k8s cluster and user can easily login to nodes to access the etcd service. It's not necessary to provide a loadbalancer for etcd, especially given it will cost at least 2 VMs and 1 floating ip.
| Changed in magnum: | |
| assignee: | nobody → Feilong Wang (flwang) |
| Changed in magnum: | |
| status: | New → In Progress |
| summary: |
- Deprecate etcd LB + Remove etcd LB |
Revision history for this message
| Pawel Kubica (pawcykca) wrote | #1 |
To post a comment you must log in.
What was the purpose of introducing the etcd Load Blanacer? Currently API Server on Master Nodes uses localhost instead of ETCD_LB_VIP to connect to the etcd instance.