2 changes: 2 additions & 0 deletions 2 docs/README.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -36,4 +36,6 @@ certainly want the docs that go with that version.</h1>
		folder.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

25 changes: 14 additions & 11 deletions 25 docs/accessing-the-cluster.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -42,7 +42,7 @@ kubernetes CLI, `kubectl`.
		To access a cluster, you need to know the location of the cluster and have credentials
		to access it. Typically, this is automatically set-up when you work through
		though a [Getting started guide](../docs/getting-started-guides/README.md),
		though a [Getting started guide](getting-started-guides/README.md),
		or someone else setup the cluster and provided you with credentials and a location.
		Check the location and credentials that kubectl knows about with this command:
Expand All		@@ -51,7 +51,7 @@ kubectl config view
		```
		Many of the [examples](../examples/) provide an introduction to using
		kubectl and complete documentation is found in the [kubectl manual](../docs/user-guide/kubectl/kubectl.md).
		kubectl and complete documentation is found in the [kubectl manual](user-guide/kubectl/kubectl.md).
		### Directly accessing the REST API
		Kubectl handles locating and authenticating to the apiserver.
Expand All		@@ -76,7 +76,7 @@ Run it like this:
		```
		kubectl proxy --port=8080 &
		```
		See [kubectl proxy](../docs/user-guide/kubectl/kubectl_proxy.md) for more details.
		See [kubectl proxy](user-guide/kubectl/kubectl_proxy.md) for more details.
		Then you can explore the API with curl, wget, or a browser, like so:
		```
Expand Down Expand Up		@@ -110,16 +110,16 @@ certificate.
		On some clusters, the apiserver does not require authentication; it may serve
		on localhost, or be protected by a firewall. There is not a standard
		for this. [Configuring Access to the API](../docs/accessing_the_api.md)
		for this. [Configuring Access to the API](accessing_the_api.md)
		describes how a cluster admin can configure this. Such approaches may conflict
		with future high-availability support.
		### Programmatic access to the API
		There are [client libraries](../docs/client-libraries.md) for accessing the API
		There are [client libraries](client-libraries.md) for accessing the API
		from several languages. The Kubernetes project-supported
		[Go](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/pkg/client)
		client library can use the same [kubeconfig file](../docs/kubeconfig-file.md)
		client library can use the same [kubeconfig file](kubeconfig-file.md)
		as the kubectl CLI does to locate and authenticate to the apiserver.
		See documentation for other libraries for how they authenticate.
Expand Down Expand Up		@@ -153,7 +153,7 @@ In each case, the credentials of the pod are used to communicate securely with t
		## Accessing services running on the cluster
		The previous section was about connecting the Kubernetes API server. This section is about
		connecting to other services running on Kubernetes cluster. In kubernetes, the
		[nodes](../docs/node.md), [pods](../docs/pods.md) and [services](services.md) all have
		[nodes](node.md), [pods](pods.md) and [services](services.md) all have
		their own IPs. In many cases, the node IPs, pod IPs, and some service IPs on a cluster will not be
		routable, so they will not be reachable from a machine outside the cluster,
		such as your desktop machine.
Expand All		@@ -162,8 +162,8 @@ such as your desktop machine.
		You have several options for connecting to nodes, pods and services from outside the cluster:
		- Access services through public IPs.
		- Use a service with type `NodePort` or `LoadBalancer` to make the service reachable outside
		the cluster. See the [services](../docs/services.md) and
		[kubectl expose](../docs/user-guide/kubectl/kubectl_expose.md) documentation.
		the cluster. See the [services](services.md) and
		[kubectl expose](user-guide/kubectl/kubectl_expose.md) documentation.
		- Depending on your cluster environment, this may just expose the service to your corporate network,
		or it may expose it to the internet. Think about whether the service being exposed is secure.
		Does it do its own authentication?
Expand All		@@ -179,7 +179,7 @@ You have several options for connecting to nodes, pods and services from outside
		- Only works for HTTP/HTTPS.
		- Described [here](#discovering-builtin-services).
		- Access from a node or pod in the cluster.
		- Run a pod, and then connect to a shell in it using [kubectl exec](../docs/user-guide/kubectl/kubectl_exec.md).
		- Run a pod, and then connect to a shell in it using [kubectl exec](user-guide/kubectl/kubectl_exec.md).
		Connect to other nodes, pods, and services from that shell.
		- Some clusters may allow you to ssh to a node in the cluster. From there you may be able to
		access cluster services. This is a non-standard method, and will work on some clusters but
Expand Down Expand Up		@@ -256,7 +256,7 @@ There are several different proxies you may encounter when using kubernetes:
		- proxy to target may use HTTP or HTTPS as chosen by proxy using available information
		- can be used to reach a Node, Pod, or Service
		- does load balancing when used to reach a Service
		1. The [kube proxy](../docs/services.md#ips-and-vips):
		1. The [kube proxy](services.md#ips-and-vips):
		- runs on each node
		- proxies UDP and TCP
		- does not understand HTTP
Expand All		@@ -277,4 +277,7 @@ There are several different proxies you may encounter when using kubernetes:
		Kubernetes users will typically not need to worry about anything other than the first two types. The cluster admin
		will typically ensure that the latter types are setup correctly.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

4 changes: 3 additions & 1 deletion 4 docs/accessing_the_api.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -20,7 +20,7 @@ cluster administrators who want to customize their cluster
		or understand the details.
		Most questions about accessing the cluster are covered
		in [Accessing the cluster](../docs/accessing-the-cluster.md).
		in [Accessing the cluster](accessing-the-cluster.md).
		## Ports and IPs Served On
Expand Down Expand Up		@@ -89,4 +89,6 @@ variety of uses cases:
		installations that want to do their own auth proxy.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/admission_controllers.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -141,4 +141,6 @@ For Kubernetes 1.0, we strongly recommend running the following set of admission
		```
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/annotations.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -39,4 +39,6 @@ Possible information that could be recorded in annotations:
		Yes, this information could be stored in an external database or directory, but that would make it much harder to produce shared client libraries and tools for deployment, management, introspection, etc.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

4 changes: 2 additions & 2 deletions 4 docs/api-conventions.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -624,6 +624,6 @@ Possible values for the ```reason``` and ```details``` fields:
		TODO: Document events (refer to another doc for details)
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/api.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -86,4 +86,6 @@ Some important differences between v1beta1/2 and v1beta3:
		* Host volumes have been changed from `hostDir` to `hostPath` to better reflect that they can be files or directories.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/application-troubleshooting.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -166,4 +166,6 @@ check:
		* Is your application serving on the port that you configured? Kubernetes doesn't do port remapping, so if your application serves on 8080, the ```containerPort``` field needs to be 8080.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/authentication.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -54,4 +54,6 @@ that interface between kubernetes and a bedrock authentication provider (e.g.
		github.com, google.com, enterprise directory, kerberos, etc.)
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/authorization.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -117,4 +117,6 @@ same or similar arguments. Developers should then consider the interaction betw
		caching and revocation of permissions.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/availability.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -144,4 +144,6 @@ service instances behind a load balancer (AWS Elastic Load Balancer, GCE Forward
		failures of a single cluster are not visible to end users.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/cli-roadmap.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -92,4 +92,6 @@ Server-side support:
		1. Operate on uids
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 2 additions & 1 deletion 3 docs/client-libraries.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -29,5 +29,6 @@ certainly want the docs that go with that version.</h1>
		* [Perl](https://metacpan.org/pod/Net::Kubernetes)
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 2 additions & 1 deletion 3 docs/cluster-admin-guide.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -87,5 +87,6 @@ project.](salt.md).
		* **Admission Controllers** [admission_controllers](admission_controllers.md)
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/cluster-large.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -71,4 +71,6 @@ To avoid running into cluster addon resource issues, when creating a cluster wit
		For directions on how to detect if addon containers are hitting resource limits, see the [Troubleshooting section of Compute Resources](compute_resources.md#troubleshooting).
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 2 additions & 1 deletion 3 docs/cluster-troubleshooting.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -40,5 +40,6 @@ of the relevant log files. (note that on systemd based systems, you may need to
		* /var/log/kube-proxy.log - Kube Proxy, responsible for service load balancing
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/cluster_management.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -73,4 +73,6 @@ If you want more control over the upgrading process, you may use the following w
		node discovery; currently this is only Google Compute Engine, not including CoreOS on Google Compute Engine using kube-register). See [Node](node.md).
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 2 additions & 1 deletion 3 docs/compute_resources.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -222,5 +222,6 @@ cores. We plan to revise the definition of the cpu resource to allow for more c
		across providers and platforms.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/container-environment.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -118,4 +118,6 @@ Hook handlers are the way that hooks are surfaced to containers.  Containers ca
		[1]: http://man7.org/linux/man-pages/man2/gethostname.2.html
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/containers.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -103,4 +103,6 @@ The relationship between Docker's capabilities and [Linux capabilities](http://m
		| BLOCK_SUSPEND | CAP_BLOCK_SUSPEND |
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/debugging-services.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -503,4 +503,6 @@ Contact us on
		[GitHub](https://github.com/GoogleCloudPlatform/kubernetes).
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/README.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -31,4 +31,6 @@ Finally, Kubernetes aspires to be an extensible, pluggable, building-block OSS p
		For more about the Kubernetes architecture, see [architecture](architecture.md).
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/access.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -262,4 +262,6 @@ Improvements:
		- Policies to drop logging for high rate trusted API calls, or by users performing audit or other sensitive functions.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/admission_control.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -93,4 +93,6 @@ will ensure the following:
		If at any step, there is an error, the request is canceled.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/admission_control_limit_range.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -146,4 +146,6 @@ It is expected we will want to define limits for particular pods or containers b
		To make a **LimitRangeItem** more restrictive, we will intend to add these additional restrictions at a future point in time.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/admission_control_resource_quota.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -167,4 +167,6 @@ services 3 5
		```
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/architecture.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -58,4 +58,6 @@ All other cluster-level functions are currently performed by the Controller Mana
		The [`replicationcontroller`](../replication-controller.md) is a mechanism that is layered on top of the simple [`pod`](../pods.md) API. We eventually plan to port it to a generic plug-in mechanism, once one is implemented.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/clustering.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -74,4 +74,6 @@ This flow has the admin manually approving the kubelet signing requests. This i
		
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 3 additions & 0 deletions 3 docs/design/clustering/README.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -39,4 +39,7 @@ If you are using boot2docker and get warnings about clock skew (or if things are
		If you have the fswatch utility installed, you can have it monitor the file system and automatically rebuild when files have changed. Just do a `make watch`.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 3 additions & 0 deletions 3 docs/design/command_execution_port_forwarding.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -157,4 +157,7 @@ access.
		Additional work is required to ensure that multiple command execution or port forwarding connections from different clients are not able to see each other's data. This can most likely be achieved via SELinux labeling and unique process contexts.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/event_compression.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -92,4 +92,6 @@ This demonstrates what would have been 20 separate entries (indicating schedulin
		* PR [#4444](https://github.com/GoogleCloudPlatform/kubernetes/pull/4444): Switch events history to use LRU cache instead of map
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 3 additions & 0 deletions 3 docs/design/expansion.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -399,4 +399,7 @@ spec:
		restartPolicy: Never
		```
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/identifiers.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -106,4 +106,6 @@ objectives.
		1. This may correspond to Docker's container ID.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

3 changes: 3 additions & 0 deletions 3 docs/design/namespaces.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -348,4 +348,7 @@ to remove that Namespace from the storage.
		At this point, all content associated with that Namespace, and the Namespace itself are gone.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/networking.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -190,4 +190,6 @@ External IP assignment would also simplify DNS support (see below).
		IPv6 would be a nice option, also, but we can't depend on it yet. Docker support is in progress: [Docker issue #2974](https://github.com/dotcloud/docker/issues/2974), [Docker issue #6923](https://github.com/dotcloud/docker/issues/6923), [Docker issue #6975](https://github.com/dotcloud/docker/issues/6975). Additionally, direct ipv6 assignment to instances doesn't appear to be supported by major cloud providers (e.g., AWS EC2, GCE) yet. We'd happily take pull requests from people running Kubernetes on bare metal, though. :-)
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/persistent-storage.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -228,4 +228,6 @@ The ```PersistentVolumeClaimBinder``` will reconcile this by removing the claim
		Admins can script the recycling of released volumes. Future dynamic provisioners will understand how a volume should be recycled.
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/principles.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -69,4 +69,6 @@ TODO
		* [Eric Raymond's 17 UNIX rules](https://en.wikipedia.org/wiki/Unix_philosophy#Eric_Raymond.E2.80.99s_17_Unix_Rules)
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/resources.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -227,4 +227,6 @@ This is the amount of time a container spends accessing disk, including actuator
		* Compressible? yes
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

2 changes: 2 additions & 0 deletions 2 docs/design/secrets.md

Show comments

View file Edit file Delete file

Original file line number	Diff line number	Diff line change
Expand Up		@@ -590,4 +590,6 @@ source. Both containers will have the following files present on their filesyst
		/etc/secret-volume/password
		<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
		[]()
		<!-- END MUNGE: GENERATED_ANALYTICS -->

Loading