Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
Go to file
Manuel de Brito Fontes 1c831f73bb Add .dockerignore file to improve build times 2017-01-04 18:11:11 -03:00
_vendor Update aws-sdk-go to 1.6.8 2016-12-30 10:42:50 -05:00
addons fix bug in ca addon spec 2016-12-15 08:15:42 -05:00
channels Merge pull request #1291 from justinsb/bump_stable_channel 2016-12-28 10:31:18 -07:00
cloudmock/aws Update aws-sdk-go mocks with new functions 2016-12-30 10:47:44 -05:00
cmd Revert "Revert "Load protokube from http/https"" 2017-01-04 09:32:24 -08:00
dns-controller updating headers, OMG we need this in the ci 2016-12-03 13:09:58 -07:00
docs Revert "Revert "Load protokube from http/https"" 2017-01-04 09:32:24 -08:00
examples Fix example code 2016-12-19 00:22:30 -05:00
federation Mark ObjectMeta as a named field 2016-12-14 22:26:57 -05:00
hack Revert "Revert "Load protokube from http/https"" 2017-01-04 09:32:24 -08:00
images protokube / nodeup: Up kubectl to v1.5.1, bump protokube tag to 1.5.0 2016-12-27 12:39:24 -08:00
nodeup/pkg/model Add tests for docker nodeup side 2016-12-20 13:10:39 -05:00
pkg Specify storage-backend=etcd2 explicitly 2017-01-04 11:27:31 -05:00
protokube Always set CredentialsChainVerboseErrors when initializing AWS 2017-01-03 20:03:03 -05:00
tests/integration Lock down bastion->master/nodes 2017-01-03 11:20:01 -05:00
upup Merge pull request #1349 from kubernetes/revert-1347-revert-1318-images_over_http 2017-01-04 10:24:45 -08:00
util/pkg Always set CredentialsChainVerboseErrors when initializing AWS 2017-01-03 20:03:03 -05:00
vendor Update aws-sdk-go to 1.6.8 2016-12-30 10:42:50 -05:00
.dockerignore Add .dockerignore file to improve build times 2017-01-04 18:11:11 -03:00
.gitignore Ignore tags files generated by Exhuberant Ctags 2016-12-28 22:13:47 -08: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 Revert "Revert "Load protokube from http/https"" 2017-01-04 09:32:24 -08:00
README.md Merge pull request #1236 from justinsb/import_fixup 2016-12-29 21:48:24 -07: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
version.go Revert "Revert "Load protokube from http/https"" 2017-01-04 09:32:24 -08:00

README.md

Kubernetes Operations (kops)

Build Status Go Report Card GoDoc Widget

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 lets you deploy grade Kubernetes clusters from the command line, with options that support HA Masters. Kubernetes Operations supports deploying Kubernetes on Amazon Web Services (AWS) and support for more platforms is planned.

Launching a Kubernetes cluster hosted on AWS

Check out our tutorial for launching a Kubernetes cluster hosted on AWS.

Features

  • Automated Kubernetes cluster CRUD for (AWS)
  • Highly Available (HA) Kubernetes Masters Setup
  • 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
  • Command line autocomplete
  • Community support
  • Upgrade from kube-up

Installing

kubectl is required, see here.

OSX From Homebrew (Latest Stable Release)

$ brew update && brew install kops

OSX From Homebrew (HEAD of master)

$ brew update && brew install --HEAD kops

Linux

Download the latest release, then:

$ chmod +x kops-linux-amd64                 # Add execution permissions
$ mv kops-linux-amd64 /usr/local/bin/kops   # Move the kops to /usr/local/bin

From Source

Go 1.7+ and make are required.

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

See building notes for more information.

At this time, Windows is not a supported platform.

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

History

View our changelog

GitHub Issues

Bugs

If you think you have found a bug please follow the instructions below.

  • Please spend a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate.
  • Set -v 10 command line option and save the log output. Please paste this into your issue.
  • Note the version of kops you are running (from kops version), and the command line options you are using
  • Open a new issue
  • Remember users might be searching for your issue in the future, so please give it a meaningful title to helps others.
  • Feel free to reach out to the kops community on kubernetes slack

Features

We also use the issue tracker to track features. If you have an idea for a feature, or think you can help kops become even more awesome follow the steps below.

  • Open a new issue
  • Remember users might be searching for your issue in the future, so please give it a meaningful title to helps others.
  • Clearly define the use case, using concrete examples. EG: I type this and kops does that.
  • Some of our larger features will require some design. If you would like to include a technical design for your feature please include it in the issue.
  • After the new feature is well understood, and the design agreed upon we can start coding the feature. We would love for you to code it. So please open up a WIP (work in progress) pull request, and happy coding.