Tim Bannister
23e8eaf782
* Use note shortcode in kops glossary entry This brings the entry closer to Kubernetes' style guide for documentation. * Reword kops glossary entry - Write “Terraform” with a capital T (it's a proper noun) - Adjust grammar
1.0 KiB
Executable File
1.0 KiB
Executable File
title, id, date, full_link, short_description, aka, tags
| title | id | date | full_link | short_description | aka | tags | ||
|---|---|---|---|---|---|---|---|---|
| Kops | kops | 2018-04-12 | /docs/getting-started-guides/kops/ | A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. |
|
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters.
{{< note >}} kops has general availability support only for AWS. Support for using kops with GCE and VMware vSphere are in alpha. {{< /note >}}
kops provisions your cluster with:
- Fully automated installation
- DNS-based cluster identification
- Self-healing: everything runs in Auto-Scaling Groups
- Limited OS support (Debian preferred, Ubuntu 16.04 supported, early support for CentOS & RHEL)
- High availability (HA) support
- The ability to directly provision, or to generate Terraform manifests
You can also build your own cluster using {{< glossary_tooltip term_id="kubeadm" >}} as a building block. kops builds on the kubeadm work.