Keiko - Enable Kubernetes at scale
Read this in other languages: įŽäŊä¸æ.
News
Keiko Project has moved from the CLA to the DCO.
Please signoff your contributions by doing ONE of the following:
- Use
git commit -s ...with each commit to add the signoff or - Manually add a
Signed-off-by: Your Name <[email protected]>to each commit message.
The email address must match your primary GitHub email. You do NOT need cryptographic (e.g. gpg) signing.
- Use
git commit -s --amend ...to add a signoff to the latest commit, if you forgot.
To automatically signoff on every commit, copy the community/dco-signoff-hook/prepare-commit-msg file to the .git/hooks directory in your repo or if you already have such a hook, merge the contents into your existing hook.
What is Keiko?
Keiko is a set of independent open source declarative tools for orchestration and management of multi-tenant, reliable, secure and efficient Kubernetes clusters in production.
Why Keiko?
Keiko solves the following common problems faced when running and managing Kubernetes clusters at scale and at all stages of their lifecycle.
- How do I bootstrap and manage worker nodes for my cluster?
- How do I mitigate spurious pod/node failures as well as maintain SLAs and compliance?
- How do I manage critical cluster services required across all apps on clusters?
- How do I optimize cost of my cluster?
- How do I do forensic dumps?
Keiko Components
- Instance-manager
- Upgrade-manager
- Addon-manager
- Governor
- Lifecycle-Manager
- Minion-manager
- Kube-forensics
- Active-monitor
Demos
- Instance-manager demo
Who uses Keiko?
As the Keiko Community grows, we'd like to keep track of our users. Please send a PR with your organization name.
Currently officially using Keiko: