lb-controller | Load Balancer for Rancher services via ingress controllers | Load Balancing library

by rancher Go Version: v0.3.1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | lb-controller Summary

lb-controller is a Go library typically used in Networking, Load Balancing, Nginx applications. lb-controller has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

L7 Load Balancer service managing load balancer provider configured via load balancer controller. Pluggable model allows different controller and provider implementation. v0.1.0 has support for Kubernetes ingress as a controller, and Rancher Load Balancer as a provider. Rancher provider is a default one, although you can develop and deploy your own implementation (nginx, traefic, etc).

Support

Quality

Security

License

Reuse

Support

lb-controller has a low active ecosystem.

It has 92 star(s) with 62 fork(s). There are 14 watchers for this library.

It had no major release in the last 12 months.

lb-controller has no issues reported. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of lb-controller is v0.3.1

Quality

lb-controller has no bugs reported.

Security

lb-controller has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

lb-controller is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

lb-controller releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed lb-controller and discovered the below as its top functions. This is intended to give you an instant insight into lb-controller implemented functionality, and help decide if they suit your requirements.

BuildCustomConfig takes a LoadBalancerConfig and parses it into a custom configuration
newLoadBalancerController creates a new controller .
init initializes the Rancher instance
main is the main entrypoint .
GetSelectorConstraint returns a SelectorConstraint from a string
stickinessPolicyChanged returns true if the stickiness policy changed .
GetDefaultConfig returns a map of default values to the default configuration
GetSelectorConstraints returns a list of constraints for the selector
schedulerLabelsChanged returns true if the two sets of labels have changed .
IsSelectorMatch returns true if the selector matches the selector .

Get all kandi verified functions for this library.

lb-controller Key Features

No Key Features are available at this moment for lb-controller.

lb-controller Examples and Code Snippets

No Code Snippets are available at this moment for lb-controller.

Community Discussions

Trending Discussions on lb-controller

How is CATTLE_ENVIRONMENT_ADMIN_ACCESS_KEY supposed to be set in a Rancher container?

What is the glue between k8 ingress and google load bancers

QUESTION

How is CATTLE_ENVIRONMENT_ADMIN_ACCESS_KEY supposed to be set in a Rancher container?

Asked 2019-Jul-22 at 21:49

I'm working on a project requiring replacing rancher-compose with the rancher CLI. At the same time, my Rancher installation was upgraded from 1.6.21 (IIRC) to 1.6.27. The stacks deploy correctly when using rancher-compose. When I deploy the stacks using the rancher CLI, all of the load balancer containers have errors similar to this in their logs:

...

ANSWER

Answered 2019-Jul-22 at 21:49

It turned out that the problem is the rancher CLI is sensitive to command line parameter order in a way that rancher-compose is not: With rancher-compose, this command line worked correctly:

Source https://stackoverflow.com/questions/56482344

QUESTION

What is the glue between k8 ingress and google load bancers

Asked 2017-Feb-04 at 05:32

I am using kubernetes on google cloud container, and I still don't understand how the load-balancers are "magically" getting configured when I create / update any of my ingresses.

My understanding was that I needed to deploy a glbc / gce L7 container, and that container would watch the ingresses and do the job. I've never deployed such container. So maybe it is part of this cluster addon glbc, so it works even before I do anything?

Yet, on my cluster, I can see a "l7-default-backend-v1.0" Replication Controller in kube-system, with its pod and NodePort service, and it corresponds to what I see in the LB configs/routes. But I can't find anything like a "l7-lb-controller" that should do the provisionning, such container does not exist on the cluster.

So where is the magic ? What is the glue between the ingresses and the LB provisionning ?

...

ANSWER

Answered 2017-Feb-04 at 05:32

Google Container Engine runs the glbc "glue" on your behalf unless you explicitly request it to be disabled as a cluster add-on (see https://cloud.google.com/container-engine/reference/rest/v1/projects.zones.clusters#HttpLoadBalancing).

Just like you don't see a pod in the system namespace for the scheduler or controller manager (like you do if you deploy Kubernetes yourself), you don't see the glbc controller pod either.

Source https://stackoverflow.com/questions/42026375

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install lb-controller

You can build LB controller using Rancher dapper tool. Just install Dapper, and run the command below from lb-controller directory:. it would build the binaries and create an lb-controller image.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: