Gardener vs kOps
Gardener
gardener.cloud
kOps
kops.sigs.k8s.ioSide by side
| Figure | Gardener | kOps |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 0 | 1 |
| Spec score · Kubernetes Management Platforms | 7.6 (#16) | 7.8 (#12) |
| Purpose | Gardener is a managed Kubernetes service framework for delivering fully managed clusters at scale through your own Gardener installation. | kOps creates, destroys, upgrades, and maintains production grade, highly available Kubernetes clusters and provisions the required cloud infrastructure. |
| Support | The documentation directs users to community channels, GitHub Issues, and the Gardener community on Slack for assistance and questions. | kOps maintainers hold public office hours for developers and users, and the project points users to Kubernetes Slack channels for help. |
Plans
In their own words
kOps
kOps is a free, open-source tool for creating, upgrading, maintaining, and destroying production-grade, highly available Kubernetes clusters. It also provisions the cloud infrastructure those clusters require, with the control plane managed by the customer. AWS and Google Cloud are officially supported; DigitalOcean, Hetzner, and OpenStack are in beta, while Azure is in alpha.
Configuration uses a YAML manifest-based API with templating and dry-run modes. State synchronization supports dry runs and automatic idempotency, and kOps can generate Terraform. It offers popular CNI networking providers out of the box and supports ARM64 architectures. kOps runs on Linux, macOS, and Windows; kubectl is required to install and use it. SSH access to masters and nodes is allowed from any address by default, although no public key is installed by default. SSH sources can be restricted in cluster configuration or with a command option. The security documentation says Pods can access the underlying instance IAM role and describes its permission scope as broad. The project points users to public office hours and Kubernetes Slack channels for support.