Kubernetes-based event-driven autoscaling aka KEDA was created in 2019, as a collaboration between Microsoft and Red Hat, to make application autoscaling on Kubernetes as simple as possible. The project was accepted in March 2020 at the CNCF Sandbox maturity level and moved into the Incubator in August 2021. The Cloud Native Computing Foundation (CNCF) recently announced the graduation of KEDA, next to projects such as Kubernetes, Istio and others.
In this episode of TFiR: Newsroom, Zbynek Roubalik, Founder and CTO at Kedify, talks about the origin of the project, KEDA’s graduation within the CNCF, the problem it is trying to solve for the larger cloud-native ecosystem, and more.
Highlights of the video interview:
- Building large applications on Kubernetes could be challenging as complexity grows because of multiple modules and components and managing all these pieces together can be painful.
- It’s important to have a good observability and monitoring stack to monitor your application on your platform and based on that decide what part of the platform needs some scale out or more replicas.
- KEDA started as an open-source collaboration between Microsoft and Red Hat in 2019 to enable developers to deploy serverless, event-driven containers.
- The project was later donated to CNCF. It was accepted in March 2020 at the CNCF Sandbox maturity level and moved into the Incubator in August 2021.
- Roubalik also talks about the progress made by the project. Advanced to the realization phase, KEDA is today mature enough with lots of users. It is used in production by many big organizations, including Reddit, Xbox, and more. “The trend is pretty stable. We still see the growing interest in the project. Because of the goal that we are trying to achieve, I would say that there is no other project that offers the same capabilities on Kubernetes,” explains Roubalik.
- The community has also added new contributors, maintainers, and features.
- Roubalik encourages everyone to reach out and work with the community. “The community is healthy but the more contributors we have, it would be better,” he adds.
- As KEDA moves to the Graduated maturity level, Roubalik discusses its impact on three important constituents of the product — the users, the community around KEDA and the project itself.
- The users may rest assured that the project is well maintained, in a good shape, and mature enough to be used.
- Roubalik hopes that the graduation brings them more contributors, more users, and more people interested in becoming maintainers of the project.
- As part of its release governance, the team usually releases a new KEDA version every three months bringing new features to the project.
- Roubalik also talks about some exciting features that the team is planning to add to KEDA.
This summary was written by Monika Chauhan.