k3s/examples/kubectl-container
Tim Hockin 542e13d2d3 Better scary message 2015-07-17 09:28:49 -07:00
..
.gitignore allow kubectl to be built statically 2015-06-03 15:41:09 -07:00
Dockerfile allow kubectl to be built statically 2015-06-03 15:41:09 -07:00
Makefile s/gcloud preview docker/gcloud docker/ 2015-06-18 12:27:08 -07:00
README.md Better scary message 2015-07-17 09:28:49 -07:00
pod.json update examples/kubectl-container to v1 2015-06-10 11:33:15 -07:00

README.md

WARNING WARNING WARNING WARNING WARNING

PLEASE NOTE: This document applies to the HEAD of the source tree

If you are using a released version of Kubernetes, you should refer to the docs that go with that version.

The latest 1.0.x release of this document can be found [here](http://releases.k8s.io/release-1.0/examples/kubectl-container/README.md).

Documentation for other releases can be found at releases.k8s.io.

This directory contains a Dockerfile and Makefile for packaging up kubectl into a container.

It's not currently automated as part of a release process, so for the moment this is an example of what to do if you want to package kubectl into a container/your pod.

In the future, we may release consistently versioned groups of containers when we cut a release, in which case the source of gcr.io/google_containers/kubectl would become that automated process.

pod.json is provided as an example of packaging kubectl as a sidecar container, and to help you verify that kubectl works correctly in this configuration.

A possible reason why you would want to do this is to use kubectl proxy as a drop-in replacement for the old no-auth KUBERNETES_RO service. The other containers in your pod will find the proxy apparently serving on localhost.

Analytics