Kiverno Architecture
Kiverno utilizes a single helm chart that deploys multiple controllers, including admission, cleanup, reporting, and background controllers, each serving distinct functions within its own namespace. The system is designed to be stateless, allowing for scalability and high availability, with leader election mechanisms ensuring continuity of tasks in case of failures. This architecture is crucial for efficiently managing request evaluations and maintaining system reliability.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
SE Radio 634: Jim Bugwadia on Kubernetes Policy as Code
Related Questions
Can you say a bit more about why would it be important for a tool that is examining requests and accepting or denying to have a leader.
What is the clip Kiverno Architecture about from the episode SE Radio 634: Jim Bugwadia on Kubernetes Policy as Code?
What is the clip Kaverno Installation Insights about in the episode SE Radio 634: Jim Bugwadia on Kubernetes Policy as Code?