Possibility to use OpenStack without lbaas (loadbalancer) #7178
Conversation
k8s-ci-robot
added
do-not-merge/work-in-progress
|
/hold |
k8s-ci-robot
added
the
do-not-merge/hold
|
/hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
zetaab
force-pushed
the
feature/nonlb
branch
4 times, most recently
from
1f29ba8 to
9cf0b45
Compare
zetaab
changed the title
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
|
@drekle can you review this. Like you said this is not "production" ready when there is no loadbalancer in front of kubernetes cluster. However, I would like to make it possible to install it like this - people can use for instance external loadbalancers or metallb in front of k8s api. Actually I am currently trying to get metallb working, so we could install metallb automatically if there is no lbaas. Anyways this is first step to get support to install it like this. After this PR I can install new kops openstack cluster using octavia (neutron-lbaas not tested) or without lbaas. Installing without lbaas is not HIGHLY AVAILABLE from outside cluster |
|
/assign @mikesplain @justinsb |
zetaab
changed the title
|
I'll try to test this soon. On the fence about creating a production k8s cluster in this way, and if Kops should support, but open to input from others here. |
|
I've personally tested this, it seems fine. Running multi-master with no external LB is not as bad as running a single master, which Kops unfortunately supports, so this seems okay to do. /lgtm |
k8s-ci-robot
added
the
lgtm
There was a problem hiding this comment.
This looks good! Thanks so much @zetaab!
/retest
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mikesplain, zetaab 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:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
|
/test pull-kops-e2e-kubernetes-aws |
4 similar comments
|
/test pull-kops-e2e-kubernetes-aws |
|
/test pull-kops-e2e-kubernetes-aws |
|
/test pull-kops-e2e-kubernetes-aws |
|
/test pull-kops-e2e-kubernetes-aws |
|
/retest |
|
Did anyone try further setting up MetalLB (or gobetween like how KubeOne does this)? |
|
@MPV yes I have tried it: 1) it cannot be used for kubernetes master API 2) you need remove usually port-security from neutron ports to get it working. If thats fine then you could use MetalLB, but at least for us removing all security is no-go |
|
@zetaab Ah, yes, I've seen those known issues for using MetalLB as an in-cluster external load balancer too: My main desire here was around no 1: to have a non-OpenStack load balancer for the kubernetes masters (not load balancing services in kube), which is why I was thinking of how KubeOne does load balancing of kube masters/API-servers using gobetween (their motivation here). I'm not yet ready to make this kind of patch to kops myself, but in case anyone else would be interested, we could take a look at how KubeOne deploys gobetween to load balance the masters: Here's how they configure it: And here how they deploy it: And here's how they add the IPs of the different masters into its config: |
Some OpenStack users do have situation that they do not have lbaas resource installed at all in their setup. This PR will add very-experimental support for using OpenStack without lbaas.
Non loadbalancer deployments will generate a certificate with the 3 master floating IP addresses.
Kubeconfig will choose arbitrarily between each master.
Huge thanks to original PR author @drekle #6608
fixes #6584
/sig openstack