Kong Ingress Controller 1.0: Battle-Tested and Production Hardened
About two and a half years ago, Kong first announced our Kubernetes Ingress Controller. We were stepping up to invest in the Kubernetes community by building a full-featured API gateway that operated in a Kubernetes-native way.
Since then, we – as well as the rest of the broader Kubernetes ecosystem – have hit a number of additional milestones. Our Ingress Controller has run in tens of thousands of Kubernetes clusters, and we’ve continued to expand its functionality and stability. Just a few weeks ago, Kubernetes Ingress went to a GA status. And now, we at Kong are finally excited to announce that the next major milestone for the Kong Ingress Controller is here: it has hit version 1.0!
We’ve continued to make improvements for 1.0, which you can read about in the changelog here. But most importantly, version 1.0 is our signal to you, Kong Nation, that the Kong Ingress Controller is ready for primetime. The 1.0 milestone reflects that the controller has been battle-tested and production-hardened over the years and promises backwards-compatibility for all the future releases.
Now that we’re to 1.0, we know we have a commitment to you to continue development. We have a long roadmap of features, and we’d love to hear your ideas and any contributions you have! We know we’re going to continue to grow and evolve with Kubernetes, and we hope you’ll come along for the journey.
If you want to read more, hop on over to the latest documentation, which includes installation instructions, guidance, and some additional links to help you out. Want more? Go check out our forums, where you can ask further questions and engage with us! See you there!
Ready for a Deeper Dive?