kube-ingress-aws-controller | Configures AWS Application Load Balancers | Load Balancing library

 by   zalando-incubator Go Version: v0.14.22 License: MIT

kandi X-RAY | kube-ingress-aws-controller Summary

kandi X-RAY | kube-ingress-aws-controller Summary

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

Configures AWS Application Load Balancers according to Kubernetes Ingress resources
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              kube-ingress-aws-controller has a low active ecosystem.
              It has 369 star(s) with 82 fork(s). There are 24 watchers for this library.
              There were 10 major release(s) in the last 12 months.
              There are 53 open issues and 149 have been closed. On average issues are closed in 89 days. There are 6 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of kube-ingress-aws-controller is v0.14.22

            kandi-Quality Quality

              kube-ingress-aws-controller has 0 bugs and 0 code smells.

            kandi-Security Security

              kube-ingress-aws-controller has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              kube-ingress-aws-controller code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              kube-ingress-aws-controller is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              kube-ingress-aws-controller releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.
              It has 12706 lines of code, 391 functions and 57 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kube-ingress-aws-controller
            Get all kandi verified functions for this library.

            kube-ingress-aws-controller Key Features

            No Key Features are available at this moment for kube-ingress-aws-controller.

            kube-ingress-aws-controller Examples and Code Snippets

            No Code Snippets are available at this moment for kube-ingress-aws-controller.

            Community Discussions

            Trending Discussions on kube-ingress-aws-controller

            QUESTION

            Can I use "kube-ingress-aws-controller" without "skipper" ingress?
            Asked 2019-Dec-05 at 10:08

            I'm trying to use the ingress of kubernetes on an AWS cluster built with Kops.
            I'm following this documentation: https://github.com/kubernetes/kops/tree/master/addons/kube-ingress-aws-controller.
            As you can see, I'm using the kube-ingress-aws-controller with the skipper ingress.

            For the kube-ingress-aws-controller I have the following script:

            ...

            ANSWER

            Answered 2019-Dec-05 at 10:08

            Ordinary AWS loadbalancers enable TLS termination, automated certificate rotation, possible WAF, and Security Groups but the HTTP routing capabilities are very limited.

            Skipper's main advantages compared to other HTTP routers are:

            • matching and changing HTTP
            • by default with kube-ingress-aws-controller, just work as you would expect.

            HAproxy and Nginx are well understood and good TCP/HTTP proxies, that were built before Kubernetes. But they have drawbacks like:

            • reliance on static configuration files which comes from a time when routes and their configurations were
            • relatively static the list of annotations to implement even basic features are already quite a big list for users

            Skipper was built to:

            • support dynamically changing route configurations, which happens quite often in Kubernetes
            • gives ability to easily implement automated canary deployments, automated blue-green deployments or shadow traffic

            However there are some features that have better support in aws-alb-ingress-controller, HAproxy and nginx. For instance the sendfile() operation. If you need to stream a large file or large amount of files, then you may want to go for one of these options.

            Aws-alb-ingress-controller directly routes traffic to your Kubernetes services, which is both good and bad, because it can reduce latency, but comes with the risk of depending on kube-proxy routing. kube-proxy routing can take up to 30 seconds, ETCD ttl, for finding pods from dead nodes. Skipper enables: passively observe errors from endpoints and are able to drop these from the loadbalancer members. actively checked member pool, which will enable endpoints if these are healthy again from skipper point of view.

            Additionally the aws-alb-ingress-controller does not support features like ALB sharing, or Server Name Indication which can reduce costs. Features like path rewriting are also not currently supported.

            Traefik has a good community and support for Kubernetes. Skipper originates from Project Mosaic which was started in 2015. Back then Traefik was not yet a mature project and still had time to go before the v1.0.0 release. Traefik also does not currently support our Opentracing provider. It also did not support traffic splitting when we started stackset-controller for automated traffic switching. We have also recently done significant work on running Skipper as API gateway within Kubernetes, which could potentially help many teams that run a many small services on Kubernetes. Skipper predicates and filters are a powerful abstraction which can enhance the system easily.

            So as you can see kube-ingress-aws-controller with the skipper ingress has much more advantages and possibilities comparing to other similar solutions.

            More information you can find here: skipper-ingress-controller.

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

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

            Vulnerabilities

            No vulnerabilities reported

            Install kube-ingress-aws-controller

            You can download it from GitHub.

            Support

            We welcome your contributions, ideas and bug reports via issues and pull requests; here are those Contributor guidelines again.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/zalando-incubator/kube-ingress-aws-controller.git

          • CLI

            gh repo clone zalando-incubator/kube-ingress-aws-controller

          • sshUrl

            git@github.com:zalando-incubator/kube-ingress-aws-controller.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Load Balancing Libraries

            ingress-nginx

            by kubernetes

            bfe

            by bfenetworks

            metallb

            by metallb

            glb-director

            by github

            Try Top Libraries by zalando-incubator

            kopf

            by zalando-incubatorPython

            graphql-jit

            by zalando-incubatorTypeScript

            kubernetes-on-aws

            by zalando-incubatorGo

            kube-metrics-adapter

            by zalando-incubatorGo

            es-operator

            by zalando-incubatorGo