Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
Go to file
Muhammed Uluyol f66ca094f7 Launch a cluster-local registry.
This registry can be accessed through proxies that run on each node
listening on port 5000. We send the proxy images to the nodes directly
to avoid requests that hit the network during cluster launch. For now,
we continue to pull the registry itself over the network, especially
given its large size (we should be able to dramatically shrink the
image). On GCE we create a PD and use that for storage, otherwise we
use an emptyDir. The registry is not enabled outside of GCE. All
communication is currently plain HTTP. In order to use SSL, we will
need to be able to request a certificate/key from the apiserver signed
by the apiserver's CA cert.
2016-03-29 11:01:37 -07:00
CONTRIBUTING.md final commit 2016-03-29 10:27:47 -07:00
LICENSE final commit 2016-03-29 10:27:47 -07:00
README final commit 2016-03-29 10:27:47 -07:00
init.sls Launch a cluster-local registry. 2016-03-29 11:01:37 -07:00
initd kill child processes of addon-update on stop 2016-03-29 11:01:37 -07:00
kube-addon-update.sh typofix - https://github.com/vlajos/misspell_fixer 2016-03-29 11:01:37 -07:00
kube-addons.service kube2sky using kubeconfig secret: take 2. Point system secrets at https://kubernetes. Override in clients that can't use DNS. 2016-03-29 10:58:03 -07:00
kube-addons.sh Launch a cluster-local registry. 2016-03-29 11:01:37 -07:00
namespace.yaml Move things into a 'kube-system' namespace. 2016-03-29 11:01:23 -07:00

README

# kube-deploy

This is a repository of community maintained Kubernetes cluster deployment automations.