kubernetes-ingress-controller

Popular open-source Kubernetes network component "Kong Ingress controller" was hit by an attack in late December. Due to a stolen authentication token, an attacker was able to upload a version of the software to Dockerhub that contained a crypto-miner (obfuscated as a fileless executable). Due to the end-of-year vacations and the relatively fast detection, it looks like only a few have fallen victim to the supply chain attack. GitHub issue: https://github.com/Kong/kubernetes-ingress-controller/issues... See more details about the behavior of the malware here https://www.armosec.io/blog/kong-ingress-controller-cryptoja...

My team at Kong would agree - as maintainers of a very feature-rich implementation of Ingress we've felt the pain of pushing Ingress to the limits of its expressive power (hence our current strong focus on Gateway API). The Ingress API is fine as long as you're in the "basic proxying with simple path-based routing" territory, but once you want to do something more serious (route by query string, configure weighted load balancing, work with TLS, deal with methods, etc - let alone other protocols than HTTP) you're kinda stuck with vendor-specific extensions that mostly rely on annotations. Kong has an implementation of Gateway API for HTTP(S), TCP, UDP, TLS, gRPC that aims to offer a fairly smooth transition from Ingress to Gateway API by supporting both in our Kong Ingress Controller and working on conversion tooling (we're the only provid

There are a few options to deploy Kong as your API Gateway: Kong can work as an Ingress Controller for your Kubernetes cluster and run plugins for your traffic at the Ingress layer. Refere to the repo for more details: https://github.com/kong/kubernetes-ingress-controller You can simply deploy it as an application using the Helm chart: https://github.com/helm/charts/tree/master/stable/kong

I think there's a Kong ingress controller, that gets you a very powerful nginx setup. https://github.com/Kong/kubernetes-ingress-controller Knative uses parts of Istio for servign and TLS/SSL setup: https://github.com/knative/docs/blob/master/serving/using-an... It's a bit funny that knative serving is so complicated I have still no idea what they use under the many layers of abstraction (probably something hacked together in go), and I don't understand why don't they use a generic configurable ingress component.