loadbalancer-controller | Kubernetes loadbalancer controller to provision | Load Balancing library

by caicloud Go Version: v0.7.2-oem-czbank-1.0 License: Apache-2.0

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

kandi X-RAY | loadbalancer-controller Summary

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

A LoadBalancer, containing a proxy and multiple providers, provides external traffic load balancing for kubernetes applications. A proxy is an ingress controller watching ingress resources to provide accesses that allow inbound connections to reach the cluster services. A provider is the entrance of the cluster providing high availability for connections to proxy (ingress controller).

Support

Quality

Security

License

Reuse

Support

loadbalancer-controller has a low active ecosystem.

It has 84 star(s) with 46 fork(s). There are 13 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 17 have been closed. On average issues are closed in 98 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of loadbalancer-controller is v0.7.2-oem-czbank-1.0

Quality

loadbalancer-controller has 0 bugs and 8 code smells.

Security

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

loadbalancer-controller code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

loadbalancer-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

loadbalancer-controller releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

It has 3453 lines of code, 165 functions and 48 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

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

NewLoadBalancerController creates a new LoadBalancerController .
UpdateLBWithRetries attempts to update an existing load balancer with the given name . If an exponential backoff fails an error is returned .
EvictPod evict a pod
PodStatusesEqual returns true if a and b are equal .
newOptions returns a new set of options .
setupConfigQPS sets QPS based on environment variables
CalculateReplicas calculates the replicas of a load balancer
mapDel returns a new map with the given dels .
newCommand returns a new cobra command
MergeDeployment returns a copy of the given Deployment .

Get all kandi verified functions for this library.

loadbalancer-controller Key Features

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

loadbalancer-controller Examples and Code Snippets

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

Community Discussions

Trending Discussions on loadbalancer-controller

Securing grafana ingress with tls in kube-prometheus-stack values.yaml and make grafana available via https

EKS Ingress with Single ALB, multiple namespaces, and External DNS

GKE Ingress cannot find service resource

GCP Ingress - Error syncing to GCP: error running backend syncing routine: cloud armor security policies not supported for regional backend service

GKE Internal Ingress for Headless Service

Ingress-Nginx-Controller failed to find the 2nd service deployed on Google Cloud Platform

GCE LoadBalancer not being created despite ingress resource creation

QUESTION

Securing grafana ingress with tls in kube-prometheus-stack values.yaml and make grafana available via https

Asked 2022-Feb-24 at 08:13

I am using kube-prometheus-stack to monitor my system in gcp. Due to new requirements all my ingress need to be secured with tls. As a first step I wanted to make the grafana webpage available via https.

I created a tls secret and updated my values.yaml. After helm upgrade everything seems to work fine but page is still available via http only.

Hope you can support me here.

...

ANSWER

Answered 2022-Feb-24 at 08:12

WORKING NOW WITH FOLLOWING CONFIG

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

QUESTION

EKS Ingress with Single ALB, multiple namespaces, and External DNS

Asked 2021-Nov-16 at 19:58

I'm trying to configure a single ALB across multiple namespaces in aws EKS, each namespace has its own ingress resource.

I'm trying to configure the ingress controller aws-loadbalancer-controller on a k8s v1.20.

The problem i'm facing is that each time I try to deploy a new service it always spin-up a new classic loadbalancer in addition to the shared ALB specified in the ingress config.

https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/

...

ANSWER

Answered 2021-Sep-22 at 19:55

Unfortunately the tool being used for your usecase is wrong. AWS Load Balancer Controller will create a new load balancer for every ingress resource and I think, it makes a network load balancer for every service resource.

For your use-case, the best option is to use nginx ingress controller. You can deploy the nginx ingress controller in any 1 namespace and then create ingress resources throughout your cluster and you can have path/hostname based routing across your cluster.

In case you have many teams/projects/applications and you want to avoid a single point of failure where all your apps depend on 1 ELB, you can deploy more than 1 nginx ingress controller in your k8s cluster.

You just need to define a ingress-class variable in your nginx ingress controller deployment and add that ingress-class annotation on your applications. This way, applications having ingress-class:nginxA annotation will be clustered with the nginx ingress controller that has ingress-class=nginxA in its deployment.

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

QUESTION

GKE Ingress cannot find service resource

Asked 2021-Oct-08 at 11:44

I have a GKE Ingress, set up according to this tutorial. It worked great for a few weeks, till I wanted to add a new rule to the YAML configuration.

The following error is shown and no ingress is created anymore:

...

ANSWER

Answered 2021-Oct-08 at 11:44

I still do not understand why this was broken, or why the following fixed it.

I simplified my Ingress to not have any annotations and applied that:

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

QUESTION

GCP Ingress - Error syncing to GCP: error running backend syncing routine: cloud armor security policies not supported for regional backend service

Asked 2021-Aug-28 at 19:26

I've got this issue in Google cloud once tried to create an ingress resource.

Usually when ingress is created, other GCP resources are automatically created too (resources such as target-https-proxies-list , urlmap , forwarding-rules , etc. ). Nothing was created this time and the Ingress error is here:

...

ANSWER

Answered 2021-Aug-12 at 15:52

To elaborate a bit more on Dawids answer:

The reason for this is that cloud armor policies are only usable by external HTTP loadBalancers as explained on Google's documentation.

So if you are configuring an internal ingress on GKE this creates an Internal HTTP LoadBalancer, which is not compatible with Cloud armor security policies

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

QUESTION

GKE Internal Ingress for Headless Service

Asked 2021-Jun-11 at 11:12

I'm trying to create an internal ingress for inter-cluster communication with gke. The service that I'm trying to expose is headless and points to a kafka-broker on the cluster.

However when I try to load up the ingress, it says it cannot find the service?

...

ANSWER

Answered 2021-Jun-11 at 11:12

Setting up ingress for internal load balancing requires you to configure a proxy-only subnet on the same VPC used by your GKE cluster. This subnet will be used for the load balancers proxies. You'll also need to create a fw rule to allow traffic as well.

Have a look at the prereqs for ingress and then look here for info on how to setup the proxy-only subnet for your VPC.

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

QUESTION

Ingress-Nginx-Controller failed to find the 2nd service deployed on Google Cloud Platform

Asked 2020-Mar-18 at 12:50

I deployed following 2 services (built in Java) on GCP:

mply6 (service 1, listening on port 8080 external of GCP), corresponding to the URL: http://example.com/path1
gami6 (service 2, listening on port 8081 external of GCP), corresponding to the URL: http://example.com/path2

The yaml to deploy and expose the service 1:

...

ANSWER

Answered 2020-Mar-17 at 14:57

I cannot add any remarks on the deployment you have above. However this deployment is very similar to the http-balancer documentation

I tried the deployment mentioned in the documentation and I was able to achieve what you are trying to do. Having a load-balancer routing requests based on the path.

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

QUESTION

GCE LoadBalancer not being created despite ingress resource creation

Asked 2020-Jan-25 at 13:00

I am installing the official jenkins helm chart on GKE.

I am enabling Ingress therefore the corresponding template should be applied and the resource created.

According to the official GKE documentation:

When you create the Ingress, the GKE ingress controller creates and configures an HTTP(S) load balancer according to the information in the Ingress and the associated Services. Also, the load balancer is given a stable IP address that you can associate with a domain name.

However, this does not happen in my case; the ingress does not get an external IP associated with it:

...

ANSWER

Answered 2020-Jan-25 at 12:48

Run describe on the Ingress. If you see create/add events, you have an Ingress controller running in the cluster, otherwise, you probably have the HttpLoadBalancing(GKE Ingress Controller) add-on disabled on your GKE cluster

Edit1:

You have version incompatibility between kubernetes server and kubectl. You can check both client and server version by running below command. Check this issue for details.

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

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

Vulnerabilities

No vulnerabilities reported

Install loadbalancer-controller

You can download it from GitHub.

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: