65dd16a301
This will make use of the kOps taks engine to retry failed servers. The former approach had the side effect of not making kOps fail when the last retry failed: Because there is now a server present - although in an erroneous state - the "instance task" which the task engine retried reconciled the server (port, floating ip) instead of recreating it again. With the approach of letting the task engine retry the failed servers this will be handled correctly. |
||
|---|---|---|
| .github | ||
| addons | ||
| channels | ||
| cloudmock | ||
| cmd | ||
| dns-controller | ||
| dnsprovider | ||
| docs | ||
| examples | ||
| hack | ||
| hooks | ||
| images/mkdocs | ||
| k8s/crds | ||
| nodeup | ||
| permalinks | ||
| pkg | ||
| protokube | ||
| tests | ||
| tools | ||
| upup | ||
| util/pkg | ||
| vendor | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yaml | ||
| .kazelcfg.json | ||
| .shipbot.yaml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| ROADMAP.md | ||
| SECURITY.md | ||
| SECURITY_CONTACTS | ||
| cloudbuild.yaml | ||
| code-of-conduct.md | ||
| doc.go | ||
| go.mod | ||
| go.sum | ||
| kops-version.go | ||
| mkdocs.yml | ||
| netlify.toml | ||
README.md
kOps - Kubernetes Operations
The easiest way to get a production grade Kubernetes cluster up and running.
What is kOps?
We like to think of it as kubectl for clusters.
kops will not only help you create, destroy, upgrade and maintain production-grade, highly
available, Kubernetes cluster, but it will also provision the necessary cloud infrastructure.
AWS (Amazon Web Services) and GCE (Google Cloud Platform) are currently officially supported, with DigitalOcean, Hetzner and OpenStack in beta support, and Azure in alpha.
Can I see it in action?
Installing and launching a Kubernetes cluster hosted on AWS, GCE, DigitalOcean, Hetzner, OpenStack, Azure
See Getting Started
Documentation
Documentation is in the /docs directory, and can be seen at kops.sigs.k8s.io.
Releases and kubernetes Release Compatibility
Getting Involved and Contributing
See Contributing
Office Hours
kOps maintainers set aside one hour every other week for public office hours. This time is used to gather with community members interested in kOps. This session is open to both developers and users.
We do maintain an agenda and stick to it as much as possible. If you want to hold the floor, put your item in this doc. Bullet/note form is fine. Even if your topic gets in late, we do our best to cover it.
For more information about the office hours and how to join, see Office Hours