kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
1,429 Commits 31 Branches 256 Tags 544 MiB
Go 60.8%
HCL 30.6%
Shell 7.8%
Makefile 0.3%
Roff 0.3%
Go to file
Justin Santa Barbara 718ada42be HACK: apply #38590 directly 
Because we need https://github.com/kubernetes/kubernetes/pull/38590 , we
apply it directly to the vendor/ directory.  So that we don't break CI,
we don't apply the change to _vendor - though this does mean we now
can't run `make copydeps` until 38590 merges upstream.
 		2016-12-11 17:11:10 -05:00
_vendor Revert k8s submodule bump 2016-12-07 11:35:15 -05:00
addons cluster autoscaler addon 2016-11-16 14:19:38 -05:00
channels bumping stable channel to k8s 1.4.6 2016-11-22 23:10:43 -07:00
cloudmock/aws First model -> tf test 2016-12-11 17:11:10 -05:00
cmd First model -> tf test 2016-12-11 17:11:10 -05:00
dns-controller updating headers, OMG we need this in the ci 2016-12-03 13:09:58 -07:00
docs Merge pull request #1053 from DualSpark/release 2016-12-11 13:07:09 -07:00
e2e fixing more headers 2016-10-15 19:20:56 -06:00
examples Apply gofmt 2016-11-13 21:06:55 -05:00
federation Use versioned marshaling where we can 2016-12-08 22:17:26 -05:00
hack Merge pull request #1031 from DualSpark/script-cleanup 2016-12-07 09:21:05 -05:00
images Merge pull request #948 from justinsb/fix_build 2016-11-19 16:10:39 -05:00
pkg Merge pull request #1089 from justinsb/kops_edit_cluster 2016-12-11 10:09:53 -07:00
protokube Disable kubelet from starting until after volume mounts 2016-11-23 11:30:19 -08:00
tests/integration model -> tf test of 1.4.1 schema 2016-12-11 17:11:10 -05:00
upup First model -> tf test 2016-12-11 17:11:10 -05:00
util/pkg First model -> tf test 2016-12-11 17:11:10 -05:00
vendor HACK: apply #38590 directly 2016-12-11 17:11:10 -05:00
.gitignore Don't check in upup/models/bindata.go 2016-09-13 10:08:44 -04:00
.gitmodules Format resource diffs 2016-12-03 10:26:45 -05:00
.travis.yml Commenting out changes instead of delete 2016-12-11 14:07:32 -07:00
CHANGES.md Add notes describing aug 11 changes 2016-08-11 22:40:16 -04:00
CONTRIBUTING.md Readme Changes 2016-10-25 00:56:18 -06:00
HISTORY.md Add notes for stable channel update 2016-10-21 13:39:33 -04:00
LICENSE final commit 2016-03-29 10:27:47 -07:00
Makefile First model -> tf test 2016-12-11 17:11:10 -05:00
README.md more detailed installation instructions 2016-12-07 01:42:35 +02:00
code-of-conduct.md adding k8s code of conduct 2016-11-01 12:27:34 -06:00
doc.go Add canonical import paths 2016-11-03 23:46:27 -04:00

README.md

Kubernetes Operations (kops)

Build Status Go Report Card

The easiest way to get a production Kubernetes cluster up and running.

What is kops?

We like to think of it as kubectl for clusters.

kops lets you deploy production grade (and HA) Kubernetes clusters in the cloud from the command line.

Quickstart

Launching a Kubernetes cluster on AWS.

Example on AWS

Features

  • Automated Kubernetes cluster CRUD for the cloud (AWS)
  • HA (Highly Available) Kubernetes clusters
  • Uses a state-sync model for dry-run and automatic idempotency
  • Custom support for kubectl add-ons
  • Kops can generate Terraform configuration
  • Based on a simple meta-model defined in a directory tree
  • Easy command line syntax
  • Community support

Installation

Recommended

Download the latest release chmod +x kops-linux-amd64 - (Add execution permissions ) ln -s ./kops-linux-amd64 /usr/bin/kops - (optional, makes kops available from any path).

History

View our changelog

From Homebrew (Latest Stable Release)

brew update && brew install kops

From Homebrew (HEAD of master)

brew update && brew install --HEAD kops

From Source

go get -d k8s.io/kops
cd ${GOPATH}/src/k8s.io/kops/
git checkout release
make

See building notes for more information.

Getting involved!

Want to contribute to kops? We would love the extra help from the community. We have a quickstart guide on adding a feature.

Kops also has time set aside every other week to offer help and guidance to the community. Kops maintainers have agreed to set aside time specifically dedicated to working with newcomers, helping with PRs, and discussing new features.

We recommend letting us know beforehand if you plan on attending so we can have time to prepare for the call.

Maintainer Schedule URL
@justinsb 2nd / 4th Friday 9am PDT Zoom
@chrislovecnm 2nd / 4th Friday 9am PDT Zoom
@kris-nova 2nd / 4th Friday 9am PDT Zoom

Reach out to us on kubernetes slack. A great place to get involved or ask questions is #sig-cluster-lifecycle

Other Resources

Bugs

If you think you have found a bug :