github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-03 09:22:44 +00:00
Code Issues Projects Releases Wiki Activity

Clarify examples/kubectl-container

Browse Source
This commit is contained in:
runseb 2016-03-01 11:00:07 +01:00
parent ff43bee118
commit 66008ff419
1 changed files with 19 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
examples/kubectl-container/README.md
View File

@ -31,24 +31,32 @@ Documentation for other releases can be found at
<!-- END STRIP_FOR_RELEASE --> <!-- END STRIP_FOR_RELEASE -->
<!-- END MUNGE: UNVERSIONED_WARNING --> <!-- END MUNGE: UNVERSIONED_WARNING -->
This directory contains a Dockerfile and Makefile for packaging up kubectl into To access the Kubernetes API [from a Pod](../../docs/user-guide/accessing-the-cluster.md#accessing-the-api-from-a-pod) one of the solution is to run `kubectl proxy` in a so-called sidecar container within the Pod. To do this, you need to package `kubectl` in a container. It is useful when service accounts are being used for accessing the API and the old no-auth KUBERNETES_RO service is not available. Since all containers in a Pod share the same network namespace, containers will be able to reach the API on localhost.
a container.
It's not currently automated as part of a release process, so for the moment This example contains a [Dockerfile](Dockerfile) and [Makefile](Makefile) for packaging up `kubectl` into
this is an example of what to do if you want to package kubectl into a a container and pushing the resulting container image on the Google Container Registry. You can modify the Makefile to push to a different registry if needed.
container/your pod.
Assuming that you have checked out the Kubernetes source code and setup your environment to be able to build it. The typical build step of this kubectl container will be:
$ cd examples/kubectl-container
$ make kubectl
$ make tag
$ make container
$ make push
It is 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 and use it within a pod.
In the future, we may release consistently versioned groups of containers when 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 we cut a release, in which case the source of gcr.io/google_containers/kubectl
would become that automated process. would become that automated process.
```pod.json``` is provided as an example of packaging kubectl as a sidecar [```pod.json```](pod.json) is provided as an example of running `kubectl` as a sidecar
container, and to help you verify that kubectl works correctly in container in a Pod, and to help you verify that `kubectl` works correctly in
this configuration. this configuration. To launch this Pod, you will need a configured Kubernetes endpoint and `kubectl` installed locally, then simply create the Pod:
A possible reason why you would want to do this is to use ```kubectl proxy``` as $ kubectl create -f pod.json
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.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->