diff --git a/docs/README.md b/docs/README.md index 3059f73df1d..8b720b6f5a5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -36,4 +36,6 @@ certainly want the docs that go with that version. folder. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/README.md?pixel)]() + diff --git a/docs/accessing-the-cluster.md b/docs/accessing-the-cluster.md index de94687c5ef..3ac0df38c04 100644 --- a/docs/accessing-the-cluster.md +++ b/docs/accessing-the-cluster.md @@ -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: @@ -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. @@ -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: ``` @@ -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. @@ -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. @@ -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? @@ -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 @@ -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 @@ -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. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/accessing-the-cluster.md?pixel)]() + diff --git a/docs/accessing_the_api.md b/docs/accessing_the_api.md index 758d828f9bf..b6701e710cd 100644 --- a/docs/accessing_the_api.md +++ b/docs/accessing_the_api.md @@ -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 @@ -89,4 +89,6 @@ variety of uses cases: installations that want to do their own auth proxy. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/accessing_the_api.md?pixel)]() + diff --git a/docs/admission_controllers.md b/docs/admission_controllers.md index 243f2550411..9fe437c4a37 100644 --- a/docs/admission_controllers.md +++ b/docs/admission_controllers.md @@ -141,4 +141,6 @@ For Kubernetes 1.0, we strongly recommend running the following set of admission ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/admission_controllers.md?pixel)]() + diff --git a/docs/annotations.md b/docs/annotations.md index 3d29dd28329..27a9685e531 100644 --- a/docs/annotations.md +++ b/docs/annotations.md @@ -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. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/annotations.md?pixel)]() + diff --git a/docs/api-conventions.md b/docs/api-conventions.md index 83a09f5a961..626c0354ba1 100644 --- a/docs/api-conventions.md +++ b/docs/api-conventions.md @@ -624,6 +624,6 @@ Possible values for the ```reason``` and ```details``` fields: TODO: Document events (refer to another doc for details) - - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/api-conventions.md?pixel)]() + diff --git a/docs/api.md b/docs/api.md index 0fb8bbdfffa..2079bb64dcb 100644 --- a/docs/api.md +++ b/docs/api.md @@ -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. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/api.md?pixel)]() + diff --git a/docs/application-troubleshooting.md b/docs/application-troubleshooting.md index c3443f01c41..b062b779e9b 100644 --- a/docs/application-troubleshooting.md +++ b/docs/application-troubleshooting.md @@ -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. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/application-troubleshooting.md?pixel)]() + diff --git a/docs/authentication.md b/docs/authentication.md index cfce591c9f1..405894562c7 100644 --- a/docs/authentication.md +++ b/docs/authentication.md @@ -54,4 +54,6 @@ that interface between kubernetes and a bedrock authentication provider (e.g. github.com, google.com, enterprise directory, kerberos, etc.) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/authentication.md?pixel)]() + diff --git a/docs/authorization.md b/docs/authorization.md index 3bfff677016..f5602d98a8c 100644 --- a/docs/authorization.md +++ b/docs/authorization.md @@ -117,4 +117,6 @@ same or similar arguments. Developers should then consider the interaction betw caching and revocation of permissions. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/authorization.md?pixel)]() + diff --git a/docs/availability.md b/docs/availability.md index ec63e678622..b2c451f2cd9 100644 --- a/docs/availability.md +++ b/docs/availability.md @@ -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. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/availability.md?pixel)]() + diff --git a/docs/cli-roadmap.md b/docs/cli-roadmap.md index d7d4e7c28bf..1dc683903f8 100644 --- a/docs/cli-roadmap.md +++ b/docs/cli-roadmap.md @@ -92,4 +92,6 @@ Server-side support: 1. Operate on uids + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/cli-roadmap.md?pixel)]() + diff --git a/docs/client-libraries.md b/docs/client-libraries.md index 934b522e0e4..c2edc545f2a 100644 --- a/docs/client-libraries.md +++ b/docs/client-libraries.md @@ -29,5 +29,6 @@ certainly want the docs that go with that version. * [Perl](https://metacpan.org/pod/Net::Kubernetes) - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/client-libraries.md?pixel)]() + diff --git a/docs/cluster-admin-guide.md b/docs/cluster-admin-guide.md index 1a68ee8a019..a565d799adf 100644 --- a/docs/cluster-admin-guide.md +++ b/docs/cluster-admin-guide.md @@ -87,5 +87,6 @@ project.](salt.md). * **Admission Controllers** [admission_controllers](admission_controllers.md) - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/cluster-admin-guide.md?pixel)]() + diff --git a/docs/cluster-large.md b/docs/cluster-large.md index 3173e0292b2..ddb26eba777 100644 --- a/docs/cluster-large.md +++ b/docs/cluster-large.md @@ -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). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/cluster-large.md?pixel)]() + diff --git a/docs/cluster-troubleshooting.md b/docs/cluster-troubleshooting.md index 8801e90f258..17df092ebfb 100644 --- a/docs/cluster-troubleshooting.md +++ b/docs/cluster-troubleshooting.md @@ -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 - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/cluster-troubleshooting.md?pixel)]() + diff --git a/docs/cluster_management.md b/docs/cluster_management.md index 8b95c5b83c6..e06bada965a 100644 --- a/docs/cluster_management.md +++ b/docs/cluster_management.md @@ -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). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/cluster_management.md?pixel)]() + diff --git a/docs/compute_resources.md b/docs/compute_resources.md index 2e8a59d685c..70f1a209fa2 100644 --- a/docs/compute_resources.md +++ b/docs/compute_resources.md @@ -222,5 +222,6 @@ cores. We plan to revise the definition of the cpu resource to allow for more c across providers and platforms. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/compute_resources.md?pixel)]() + diff --git a/docs/container-environment.md b/docs/container-environment.md index 510cc319c45..1641e7ea13f 100644 --- a/docs/container-environment.md +++ b/docs/container-environment.md @@ -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 + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/container-environment.md?pixel)]() + diff --git a/docs/containers.md b/docs/containers.md index 895d857b217..ec930a8476e 100644 --- a/docs/containers.md +++ b/docs/containers.md @@ -103,4 +103,6 @@ The relationship between Docker's capabilities and [Linux capabilities](http://m | BLOCK_SUSPEND | CAP_BLOCK_SUSPEND | + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/containers.md?pixel)]() + diff --git a/docs/debugging-services.md b/docs/debugging-services.md index f67bd11ec96..d8a1fe3e0fc 100644 --- a/docs/debugging-services.md +++ b/docs/debugging-services.md @@ -503,4 +503,6 @@ Contact us on [GitHub](https://github.com/GoogleCloudPlatform/kubernetes). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/debugging-services.md?pixel)]() + diff --git a/docs/design/README.md b/docs/design/README.md index 66265b993e5..5a5b049737a 100644 --- a/docs/design/README.md +++ b/docs/design/README.md @@ -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). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/README.md?pixel)]() + diff --git a/docs/design/access.md b/docs/design/access.md index 98bf2bdf223..912f93aa62a 100644 --- a/docs/design/access.md +++ b/docs/design/access.md @@ -262,4 +262,6 @@ Improvements: - Policies to drop logging for high rate trusted API calls, or by users performing audit or other sensitive functions. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/access.md?pixel)]() + diff --git a/docs/design/admission_control.md b/docs/design/admission_control.md index 4094156b561..5870a60127e 100644 --- a/docs/design/admission_control.md +++ b/docs/design/admission_control.md @@ -93,4 +93,6 @@ will ensure the following: If at any step, there is an error, the request is canceled. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/admission_control.md?pixel)]() + diff --git a/docs/design/admission_control_limit_range.md b/docs/design/admission_control_limit_range.md index c1914478548..e5363cea037 100644 --- a/docs/design/admission_control_limit_range.md +++ b/docs/design/admission_control_limit_range.md @@ -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. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/admission_control_limit_range.md?pixel)]() + diff --git a/docs/design/admission_control_resource_quota.md b/docs/design/admission_control_resource_quota.md index cd9282df1ca..754e5a006d8 100644 --- a/docs/design/admission_control_resource_quota.md +++ b/docs/design/admission_control_resource_quota.md @@ -167,4 +167,6 @@ services 3 5 ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/admission_control_resource_quota.md?pixel)]() + diff --git a/docs/design/architecture.md b/docs/design/architecture.md index 6c82896ede4..71d606a1798 100644 --- a/docs/design/architecture.md +++ b/docs/design/architecture.md @@ -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. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/architecture.md?pixel)]() + diff --git a/docs/design/clustering.md b/docs/design/clustering.md index 95ff3cccec9..3e9972ce42b 100644 --- a/docs/design/clustering.md +++ b/docs/design/clustering.md @@ -74,4 +74,6 @@ This flow has the admin manually approving the kubelet signing requests. This i ![Dynamic Sequence Diagram](clustering/dynamic.png) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/clustering.md?pixel)]() + diff --git a/docs/design/clustering/README.md b/docs/design/clustering/README.md index dfd55e96a35..07dcc7b392a 100644 --- a/docs/design/clustering/README.md +++ b/docs/design/clustering/README.md @@ -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`. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/clustering/README.md?pixel)]() + diff --git a/docs/design/command_execution_port_forwarding.md b/docs/design/command_execution_port_forwarding.md index 056814e7f3a..7d110c3fc4c 100644 --- a/docs/design/command_execution_port_forwarding.md +++ b/docs/design/command_execution_port_forwarding.md @@ -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. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/command_execution_port_forwarding.md?pixel)]() + diff --git a/docs/design/event_compression.md b/docs/design/event_compression.md index 4178393c903..40dc9e52772 100644 --- a/docs/design/event_compression.md +++ b/docs/design/event_compression.md @@ -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 + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/event_compression.md?pixel)]() + diff --git a/docs/design/expansion.md b/docs/design/expansion.md index 01a774cb2d6..4f4511ce236 100644 --- a/docs/design/expansion.md +++ b/docs/design/expansion.md @@ -399,4 +399,7 @@ spec: restartPolicy: Never ``` + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/expansion.md?pixel)]() + diff --git a/docs/design/identifiers.md b/docs/design/identifiers.md index e192b1ed0b8..49068cc8c76 100644 --- a/docs/design/identifiers.md +++ b/docs/design/identifiers.md @@ -106,4 +106,6 @@ objectives. 1. This may correspond to Docker's container ID. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/identifiers.md?pixel)]() + diff --git a/docs/design/namespaces.md b/docs/design/namespaces.md index 547d040b0a1..cd8b5280999 100644 --- a/docs/design/namespaces.md +++ b/docs/design/namespaces.md @@ -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. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/namespaces.md?pixel)]() + diff --git a/docs/design/networking.md b/docs/design/networking.md index 5a4a5835e47..35248a71386 100644 --- a/docs/design/networking.md +++ b/docs/design/networking.md @@ -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. :-) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/networking.md?pixel)]() + diff --git a/docs/design/persistent-storage.md b/docs/design/persistent-storage.md index 9cc92b425eb..585cd281941 100644 --- a/docs/design/persistent-storage.md +++ b/docs/design/persistent-storage.md @@ -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. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/persistent-storage.md?pixel)]() + diff --git a/docs/design/principles.md b/docs/design/principles.md index e1bd97da09c..5071e89d138 100644 --- a/docs/design/principles.md +++ b/docs/design/principles.md @@ -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) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/principles.md?pixel)]() + diff --git a/docs/design/resources.md b/docs/design/resources.md index 9539bed2689..229e9b766d8 100644 --- a/docs/design/resources.md +++ b/docs/design/resources.md @@ -227,4 +227,6 @@ This is the amount of time a container spends accessing disk, including actuator * Compressible? yes + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/resources.md?pixel)]() + diff --git a/docs/design/secrets.md b/docs/design/secrets.md index c1643a9d182..2fdee5376af 100644 --- a/docs/design/secrets.md +++ b/docs/design/secrets.md @@ -590,4 +590,6 @@ source. Both containers will have the following files present on their filesyst /etc/secret-volume/password + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/secrets.md?pixel)]() + diff --git a/docs/design/security.md b/docs/design/security.md index 90dc3237188..bbb735eb8c6 100644 --- a/docs/design/security.md +++ b/docs/design/security.md @@ -131,4 +131,6 @@ The controller manager for Replication Controllers and other future controllers The Kubernetes pod scheduler is responsible for reading data from the pod to fit it onto a node in the cluster. At a minimum, it needs access to view the ID of a pod (to craft the binding), its current state, any resource information necessary to identify placement, and other data relevant to concerns like anti-affinity, zone or region preference, or custom logic. It does not need the ability to modify pods or see other resources, only to create bindings. It should not need the ability to delete bindings unless the scheduler takes control of relocating components on failed hosts (which could be implemented by a separate component that can delete bindings but not create them). The scheduler may need read access to user or project-container information to determine preferential location (underspecified at this time). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/security.md?pixel)]() + diff --git a/docs/design/security_context.md b/docs/design/security_context.md index cbf525a8d39..ad83a6bd193 100644 --- a/docs/design/security_context.md +++ b/docs/design/security_context.md @@ -170,5 +170,6 @@ will be denied by default. In the future the admission plugin will base this de configurable policies that reside within the [service account](https://github.com/GoogleCloudPlatform/kubernetes/pull/2297). - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/security_context.md?pixel)]() + diff --git a/docs/design/service_accounts.md b/docs/design/service_accounts.md index 896bd68e798..612378531dd 100644 --- a/docs/design/service_accounts.md +++ b/docs/design/service_accounts.md @@ -177,5 +177,6 @@ Finally, it may provide an interface to automate creation of new serviceAccounts to GET serviceAccounts to see what has been created. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/service_accounts.md?pixel)]() + diff --git a/docs/design/simple-rolling-update.md b/docs/design/simple-rolling-update.md index 45005353999..0f2fe9e628e 100644 --- a/docs/design/simple-rolling-update.md +++ b/docs/design/simple-rolling-update.md @@ -105,4 +105,6 @@ then ```foo-next``` is synthesized using the pattern ```- [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/simple-rolling-update.md?pixel)]() + diff --git a/docs/devel/README.md b/docs/devel/README.md index 26eb7cede93..6ce867693fe 100644 --- a/docs/devel/README.md +++ b/docs/devel/README.md @@ -47,4 +47,7 @@ Docs in this directory relate to developing Kubernetes. * **Getting Recent Builds** ([getting-builds.md](getting-builds.md)): How to get recent builds including the latest builds to pass CI. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/README.md?pixel)]() + diff --git a/docs/devel/api_changes.md b/docs/devel/api_changes.md index 3ad1847d525..3a0c1991af3 100644 --- a/docs/devel/api_changes.md +++ b/docs/devel/api_changes.md @@ -356,4 +356,6 @@ the change gets in. If you are unsure, ask. Also make sure that the change gets TODO(smarterclayton): write this. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/api_changes.md?pixel)]() + diff --git a/docs/devel/cherry-picks.md b/docs/devel/cherry-picks.md index 03f2ebb58ff..04811f0b40c 100644 --- a/docs/devel/cherry-picks.md +++ b/docs/devel/cherry-picks.md @@ -46,4 +46,6 @@ against a release is a GitHub query: For example, [this query is all of the v0.21.x cherry-picks](https://github.com/GoogleCloudPlatform/kubernetes/pulls?utf8=%E2%9C%93&q=is%3Apr+%22automated+cherry+pick%22+base%3Arelease-0.21) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/cherry-picks.md?pixel)]() + diff --git a/docs/devel/coding-conventions.md b/docs/devel/coding-conventions.md index e61398ee513..54d9aaa634a 100644 --- a/docs/devel/coding-conventions.md +++ b/docs/devel/coding-conventions.md @@ -20,5 +20,6 @@ Coding style advice for contributors - https://gist.github.com/lavalamp/4bd23295a9f32706a48f - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/coding-conventions.md?pixel)]() + diff --git a/docs/devel/collab.md b/docs/devel/collab.md index dc12537df83..d212012f175 100644 --- a/docs/devel/collab.md +++ b/docs/devel/collab.md @@ -54,4 +54,6 @@ PRs that are incorrectly judged to be merge-able, may be reverted and subject to Any maintainer or core contributor who wants to review a PR but does not have time immediately may put a hold on a PR simply by saying so on the PR discussion and offering an ETA measured in single-digit days at most. Any PR that has a hold shall not be merged until the person who requested the hold acks the review, withdraws their hold, or is overruled by a preponderance of maintainers. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/collab.md?pixel)]() + diff --git a/docs/devel/developer-guides/vagrant.md b/docs/devel/developer-guides/vagrant.md index 1316e26b0ec..1b71664828e 100644 --- a/docs/devel/developer-guides/vagrant.md +++ b/docs/devel/developer-guides/vagrant.md @@ -351,4 +351,6 @@ export KUBERNETES_MINION_MEMORY=2048 ```vagrant suspend``` seems to mess up the network. It's not supported at this time. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/developer-guides/vagrant.md?pixel)]() + diff --git a/docs/devel/development.md b/docs/devel/development.md index 157f49d6bed..ba9b989740e 100644 --- a/docs/devel/development.md +++ b/docs/devel/development.md @@ -281,8 +281,8 @@ go run hack/e2e.go -v -ctl='delete pod foobar' ## Conformance testing End-to-end testing, as described above, is for [development -distributions](../../docs/devel/writing-a-getting-started-guide.md). A conformance test is used on -a [versioned distro](../../docs/devel/writing-a-getting-started-guide.md). +distributions](writing-a-getting-started-guide.md). A conformance test is used on +a [versioned distro](writing-a-getting-started-guide.md). The conformance test runs a subset of the e2e-tests against a manually-created cluster. It does not require support for up/push/down and other operations. To run a conformance test, you need to know the @@ -300,4 +300,6 @@ hack/run-gendocs.sh ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/development.md?pixel)]() + diff --git a/docs/devel/faster_reviews.md b/docs/devel/faster_reviews.md index 99e60fb1eda..eb3b25e9f1b 100644 --- a/docs/devel/faster_reviews.md +++ b/docs/devel/faster_reviews.md @@ -190,5 +190,6 @@ a bit of thought into how your work can be made easier to review. If you do these things your PRs will flow much more easily. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/faster_reviews.md?pixel)]() + diff --git a/docs/devel/flaky-tests.md b/docs/devel/flaky-tests.md index ee93bf198f8..d26fc406c28 100644 --- a/docs/devel/flaky-tests.md +++ b/docs/devel/flaky-tests.md @@ -76,4 +76,6 @@ If you do a final check for flakes with ```docker ps -a```, ignore tasks that ex Happy flake hunting! + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/flaky-tests.md?pixel)]() + diff --git a/docs/devel/getting-builds.md b/docs/devel/getting-builds.md index 5a1a4dde554..770d486c70f 100644 --- a/docs/devel/getting-builds.md +++ b/docs/devel/getting-builds.md @@ -35,4 +35,6 @@ gsutil ls gs://kubernetes-release/release # list all official re ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/getting-builds.md?pixel)]() + diff --git a/docs/devel/instrumentation.md b/docs/devel/instrumentation.md index 762d1980a62..22cd38e160d 100644 --- a/docs/devel/instrumentation.md +++ b/docs/devel/instrumentation.md @@ -47,4 +47,6 @@ https://github.com/prometheus/client_golang/blob/master/prometheus/histogram.go https://github.com/prometheus/client_golang/blob/master/prometheus/summary.go + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/instrumentation.md?pixel)]() + diff --git a/docs/devel/issues.md b/docs/devel/issues.md index 62444185ac6..d4d1d132ee7 100644 --- a/docs/devel/issues.md +++ b/docs/devel/issues.md @@ -33,4 +33,6 @@ Definitions * untriaged - anything without a priority/X label will be considered untriaged + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/issues.md?pixel)]() + diff --git a/docs/devel/logging.md b/docs/devel/logging.md index 1ca18718027..bf2bd5c8be3 100644 --- a/docs/devel/logging.md +++ b/docs/devel/logging.md @@ -40,4 +40,6 @@ The following conventions for the glog levels to use. [glog](http://godoc.org/g As per the comments, the practical default level is V(2). Developers and QE environments may wish to run at V(3) or V(4). If you wish to change the log level, you can pass in `-v=X` where X is the desired maximum level to log. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/logging.md?pixel)]() + diff --git a/docs/devel/making-release-notes.md b/docs/devel/making-release-notes.md index 0dfbeebe1be..877c1364cdc 100644 --- a/docs/devel/making-release-notes.md +++ b/docs/devel/making-release-notes.md @@ -47,5 +47,6 @@ With the final markdown all set, cut and paste it to the top of ```CHANGELOG.md` * Press Save. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/making-release-notes.md?pixel)]() + diff --git a/docs/devel/profiling.md b/docs/devel/profiling.md index 51635424200..41737414736 100644 --- a/docs/devel/profiling.md +++ b/docs/devel/profiling.md @@ -48,4 +48,6 @@ to get 30 sec. CPU profile. To enable contention profiling you need to add line ```rt.SetBlockProfileRate(1)``` in addition to ```m.mux.HandleFunc(...)``` added before (```rt``` stands for ```runtime``` in ```master.go```). This enables 'debug/pprof/block' subpage, which can be used as an input to ```go tool pprof```. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/profiling.md?pixel)]() + diff --git a/docs/devel/pull-requests.md b/docs/devel/pull-requests.md index e82d2d005df..1c6bbe5fbae 100644 --- a/docs/devel/pull-requests.md +++ b/docs/devel/pull-requests.md @@ -42,4 +42,7 @@ Once those requirements are met, they will be labeled [ok-to-merge](https://gith These restrictions will be relaxed after v1.0 is released. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/pull-requests.md?pixel)]() + diff --git a/docs/devel/releasing.md b/docs/devel/releasing.md index 29e685cf207..5cdbde2f8ad 100644 --- a/docs/devel/releasing.md +++ b/docs/devel/releasing.md @@ -314,4 +314,6 @@ by plain mortals (in a perfect world PR/issue's title would be enough but often it is just too cryptic/geeky/domain-specific that it isn't). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/releasing.md?pixel)]() + diff --git a/docs/devel/scheduler.md b/docs/devel/scheduler.md index 3e1ae0e195c..d9fccefc5fc 100644 --- a/docs/devel/scheduler.md +++ b/docs/devel/scheduler.md @@ -61,4 +61,6 @@ If you want to get a global picture of how the scheduler works, you can start in [plugin/cmd/kube-scheduler/app/server.go](../../plugin/cmd/kube-scheduler/app/server.go) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/scheduler.md?pixel)]() + diff --git a/docs/devel/scheduler_algorithm.md b/docs/devel/scheduler_algorithm.md index 96789422c59..119b0c865f8 100644 --- a/docs/devel/scheduler_algorithm.md +++ b/docs/devel/scheduler_algorithm.md @@ -14,7 +14,7 @@ certainly want the docs that go with that version. # Scheduler Algorithm in Kubernetes -For each unscheduled Pod, the Kubernetes scheduler tries to find a node across the cluster according to a set of rules. A general introduction to the Kubernetes scheduler can be found at [docs/devel/scheduler.md](../../docs/devel/scheduler.md). In this document, the algorithm of how to select a node for the Pod is explained. There are two steps before a destination node of a Pod is chosen. The first step is filtering all the nodes and the second is ranking the remaining nodes to find a best fit for the Pod. +For each unscheduled Pod, the Kubernetes scheduler tries to find a node across the cluster according to a set of rules. A general introduction to the Kubernetes scheduler can be found at [scheduler.md](scheduler.md). In this document, the algorithm of how to select a node for the Pod is explained. There are two steps before a destination node of a Pod is chosen. The first step is filtering all the nodes and the second is ranking the remaining nodes to find a best fit for the Pod. ## Filtering the nodes The purpose of filtering the nodes is to filter out the nodes that do not meet certain requirements of the Pod. For example, if the free resource on a node (measured by the capacity minus the sum of the resource limits of all the Pods that already run on the node) is less than the Pod's required resource, the node should not be considered in the ranking phase so it is filtered out. Currently, there are several "predicates" implementing different filtering policies, including: @@ -44,7 +44,9 @@ Currently, Kubernetes scheduler provides some practical priority functions, incl - `CalculateSpreadPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on the same node. - `CalculateAntiAffinityPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on nodes with the same value for a particular label. -The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](../../plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](../../plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [docs/devel/scheduler.md](../../docs/devel/scheduler.md) for how to customize). +The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](../../plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](../../plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [scheduler.md](scheduler.md) for how to customize). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/scheduler_algorithm.md?pixel)]() + diff --git a/docs/devel/writing-a-getting-started-guide.md b/docs/devel/writing-a-getting-started-guide.md index 7b94d9a3feb..dec4d9c93ed 100644 --- a/docs/devel/writing-a-getting-started-guide.md +++ b/docs/devel/writing-a-getting-started-guide.md @@ -43,7 +43,7 @@ These guidelines say *what* to do. See the Rationale section for *why*. search for uses of flags by guides. - We may ask that you host binary assets or large amounts of code in our `contrib` directory or on your own repo. - - Setup a cluster and run the [conformance test](../../docs/devel/development.md#conformance-testing) against it, and report the + - Setup a cluster and run the [conformance test](development.md#conformance-testing) against it, and report the results in your PR. - Add or update a row in [The Matrix](../../docs/getting-started-guides/README.md). - State the binary version of kubernetes that you tested clearly in your Guide doc and in The Matrix. @@ -113,4 +113,6 @@ These guidelines say *what* to do. See the Rationale section for *why*. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/writing-a-getting-started-guide.md?pixel)]() + diff --git a/docs/developer-guide.md b/docs/developer-guide.md index dbd1021d5eb..c0b4da0507a 100644 --- a/docs/developer-guide.md +++ b/docs/developer-guide.md @@ -46,7 +46,9 @@ Guide](cluster-admin-guide.md). ## Contributing to the Kubernetes Project -See this [README](../docs/devel/README.md). +See this [README](devel/README.md). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/developer-guide.md?pixel)]() + diff --git a/docs/dns.md b/docs/dns.md index c1a0db1172f..ca065987ec4 100644 --- a/docs/dns.md +++ b/docs/dns.md @@ -52,4 +52,6 @@ time. See [the docs for the DNS cluster addon](../cluster/addons/dns/README.md). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/dns.md?pixel)]() + diff --git a/docs/downward_api.md b/docs/downward_api.md index 3fef2e32b11..53fdddf7e30 100644 --- a/docs/downward_api.md +++ b/docs/downward_api.md @@ -88,4 +88,6 @@ Some more thorough examples: * [downward API](../examples/downward-api/) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/downward_api.md?pixel)]() + diff --git a/docs/getting-started-guides/README.md b/docs/getting-started-guides/README.md index 3b5c9bd08b6..1e34ba37af3 100644 --- a/docs/getting-started-guides/README.md +++ b/docs/getting-started-guides/README.md @@ -23,37 +23,37 @@ If you are considering contributing a new guide, please read the IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level | Notes -------------------- | ------------ | ------ | ---------- | ------------------------------------------------------------------------------ | ----------- | ---------------------------- | ----- GKE | | | GCE | [docs](https://cloud.google.com/container-engine) | [✓][1](#references) | Commercial | Uses latest via https://get.k8s.io -Vagrant | Saltstack | Fedora | OVS | [docs](../../docs/getting-started-guides/vagrant.md) | | Project | Uses latest via https://get.k8s.io/ -GCE | Saltstack | Debian | GCE | [docs](../../docs/getting-started-guides/gce.md) | | Project | Uses latest via https://get.k8s.io -Azure | CoreOS | CoreOS | Weave | [docs](../../docs/getting-started-guides/coreos/azure/README.md) | | Community ([@errordeveloper](https://github.com/errordeveloper), [@squillace](https://github.com/squillace), [@chanezon](https://github.com/chanezon), [@crossorigin](https://github.com/crossorigin)) | Uses K8s version 0.17.0 +Vagrant | Saltstack | Fedora | OVS | [docs](vagrant.md) | | Project | Uses latest via https://get.k8s.io/ +GCE | Saltstack | Debian | GCE | [docs](gce.md) | | Project | Uses latest via https://get.k8s.io +Azure | CoreOS | CoreOS | Weave | [docs](coreos/azure/README.md) | | Community ([@errordeveloper](https://github.com/errordeveloper), [@squillace](https://github.com/squillace), [@chanezon](https://github.com/chanezon), [@crossorigin](https://github.com/crossorigin)) | Uses K8s version 0.17.0 Docker Single Node | custom | N/A | local | [docs](docker.md) | | Project (@brendandburns) | Tested @ 0.14.1 | Docker Multi Node | Flannel | N/A | local | [docs](docker-multinode.md) | | Project (@brendandburns) | Tested @ 0.14.1 | -Bare-metal | Ansible | Fedora | flannel | [docs](../../docs/getting-started-guides/fedora/fedora_ansible_config.md) | | Project | Uses K8s v0.13.2 -Bare-metal | custom | Fedora | _none_ | [docs](../../docs/getting-started-guides/fedora/fedora_manual_config.md) | | Project | Uses K8s v0.13.2 -Bare-metal | custom | Fedora | flannel | [docs](../../docs/getting-started-guides/fedora/flannel_multi_node_cluster.md) | | Community ([@aveshagarwal](https://github.com/aveshagarwal))| Tested with 0.15.0 -libvirt | custom | Fedora | flannel | [docs](../../docs/getting-started-guides/fedora/flannel_multi_node_cluster.md) | | Community ([@aveshagarwal](https://github.com/aveshagarwal))| Tested with 0.15.0 -KVM | custom | Fedora | flannel | [docs](../../docs/getting-started-guides/fedora/flannel_multi_node_cluster.md) | | Community ([@aveshagarwal](https://github.com/aveshagarwal))| Tested with 0.15.0 -Mesos/GCE | | | | [docs](../../docs/getting-started-guides/mesos.md) | | [Community](https://github.com/mesosphere/kubernetes-mesos) ([@jdef](https://github.com/jdef)) | Uses K8s v0.11.2 -AWS | CoreOS | CoreOS | flannel | [docs](../../docs/getting-started-guides/coreos.md) | | Community | Uses K8s version 0.19.3 -GCE | CoreOS | CoreOS | flannel | [docs](../../docs/getting-started-guides/coreos.md) | | Community [@pires](https://github.com/pires) | Uses K8s version 0.19.3 -Vagrant | CoreOS | CoreOS | flannel | [docs](../../docs/getting-started-guides/coreos.md) | | Community ( [@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles) ) | Uses K8s version 0.19.3 -Bare-metal (Offline) | CoreOS | CoreOS | flannel | [docs](../../docs/getting-started-guides/coreos/bare_metal_offline.md) | | Community([@jeffbean](https://github.com/jeffbean)) | Uses K8s version 0.15.0 -CloudStack | Ansible | CoreOS | flannel | [docs](../../docs/getting-started-guides/cloudstack.md) | | Community (@runseb) | Uses K8s version 0.9.1 -Vmware | | Debian | OVS | [docs](../../docs/getting-started-guides/vsphere.md) | | Community (@pietern) | Uses K8s version 0.9.1 -Bare-metal | custom | CentOS | _none_ | [docs](../../docs/getting-started-guides/centos/centos_manual_config.md) | | Community(@coolsvap) | Uses K8s v0.9.1 -AWS | Juju | Ubuntu | flannel | [docs](../../docs/getting-started-guides/juju.md) | | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) ) | [Tested](http://reports.vapour.ws/charm-tests-by-charm/kubernetes) K8s v0.8.1 -OpenStack/HPCloud | Juju | Ubuntu | flannel | [docs](../../docs/getting-started-guides/juju.md) | | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) ) | [Tested](http://reports.vapour.ws/charm-tests-by-charm/kubernetes) K8s v0.8.1 -Joyent | Juju | Ubuntu | flannel | [docs](../../docs/getting-started-guides/juju.md) | | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) ) | [Tested](http://reports.vapour.ws/charm-tests-by-charm/kubernetes) K8s v0.8.1 -AWS | Saltstack | Ubuntu | OVS | [docs](../../docs/getting-started-guides/aws.md) | | Community (@justinsb) | Uses K8s version 0.5.0 -Vmware | CoreOS | CoreOS | flannel | [docs](../../docs/getting-started-guides/coreos.md) | | Community (@kelseyhightower) | Uses K8s version 0.15.0 -Azure | Saltstack | Ubuntu | OpenVPN | [docs](../../docs/getting-started-guides/azure.md) | | Community | -Bare-metal | custom | Ubuntu | flannel | [docs](../../docs/getting-started-guides/ubuntu.md) | | Community (@resouer @WIZARD-CXY) | use k8s version 0.19.3 -Local | | | _none_ | [docs](../../docs/getting-started-guides/locally.md) | | Community (@preillyme) | -libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | [docs](../../docs/getting-started-guides/libvirt-coreos.md) | | Community (@lhuard1A) | -oVirt | | | | [docs](../../docs/getting-started-guides/ovirt.md) | | Community (@simon3z) | -Rackspace | CoreOS | CoreOS | flannel | [docs](../../docs/getting-started-guides/rackspace.md) | | Community (@doublerr) | use k8s version 0.18.0 +Bare-metal | Ansible | Fedora | flannel | [docs](fedora/fedora_ansible_config.md) | | Project | Uses K8s v0.13.2 +Bare-metal | custom | Fedora | _none_ | [docs](fedora/fedora_manual_config.md) | | Project | Uses K8s v0.13.2 +Bare-metal | custom | Fedora | flannel | [docs](fedora/flannel_multi_node_cluster.md) | | Community ([@aveshagarwal](https://github.com/aveshagarwal))| Tested with 0.15.0 +libvirt | custom | Fedora | flannel | [docs](fedora/flannel_multi_node_cluster.md) | | Community ([@aveshagarwal](https://github.com/aveshagarwal))| Tested with 0.15.0 +KVM | custom | Fedora | flannel | [docs](fedora/flannel_multi_node_cluster.md) | | Community ([@aveshagarwal](https://github.com/aveshagarwal))| Tested with 0.15.0 +Mesos/GCE | | | | [docs](mesos.md) | | [Community](https://github.com/mesosphere/kubernetes-mesos) ([@jdef](https://github.com/jdef)) | Uses K8s v0.11.2 +AWS | CoreOS | CoreOS | flannel | [docs](coreos.md) | | Community | Uses K8s version 0.19.3 +GCE | CoreOS | CoreOS | flannel | [docs](coreos.md) | | Community [@pires](https://github.com/pires) | Uses K8s version 0.19.3 +Vagrant | CoreOS | CoreOS | flannel | [docs](coreos.md) | | Community ( [@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles) ) | Uses K8s version 0.19.3 +Bare-metal (Offline) | CoreOS | CoreOS | flannel | [docs](coreos/bare_metal_offline.md) | | Community([@jeffbean](https://github.com/jeffbean)) | Uses K8s version 0.15.0 +CloudStack | Ansible | CoreOS | flannel | [docs](cloudstack.md) | | Community (@runseb) | Uses K8s version 0.9.1 +Vmware | | Debian | OVS | [docs](vsphere.md) | | Community (@pietern) | Uses K8s version 0.9.1 +Bare-metal | custom | CentOS | _none_ | [docs](centos/centos_manual_config.md) | | Community(@coolsvap) | Uses K8s v0.9.1 +AWS | Juju | Ubuntu | flannel | [docs](juju.md) | | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) ) | [Tested](http://reports.vapour.ws/charm-tests-by-charm/kubernetes) K8s v0.8.1 +OpenStack/HPCloud | Juju | Ubuntu | flannel | [docs](juju.md) | | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) ) | [Tested](http://reports.vapour.ws/charm-tests-by-charm/kubernetes) K8s v0.8.1 +Joyent | Juju | Ubuntu | flannel | [docs](juju.md) | | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) ) | [Tested](http://reports.vapour.ws/charm-tests-by-charm/kubernetes) K8s v0.8.1 +AWS | Saltstack | Ubuntu | OVS | [docs](aws.md) | | Community (@justinsb) | Uses K8s version 0.5.0 +Vmware | CoreOS | CoreOS | flannel | [docs](coreos.md) | | Community (@kelseyhightower) | Uses K8s version 0.15.0 +Azure | Saltstack | Ubuntu | OpenVPN | [docs](azure.md) | | Community | +Bare-metal | custom | Ubuntu | flannel | [docs](ubuntu.md) | | Community (@resouer @WIZARD-CXY) | use k8s version 0.19.3 +Local | | | _none_ | [docs](locally.md) | | Community (@preillyme) | +libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | [docs](libvirt-coreos.md) | | Community (@lhuard1A) | +oVirt | | | | [docs](ovirt.md) | | Community (@simon3z) | +Rackspace | CoreOS | CoreOS | flannel | [docs](rackspace.md) | | Community (@doublerr) | use k8s version 0.18.0 -Don't see anything above that meets your needs? See our [Getting Started from Scratch](../../docs/getting-started-guides/scratch.md) guide. +Don't see anything above that meets your needs? See our [Getting Started from Scratch](scratch.md) guide. *Note*: The above table is ordered by version test/used in notes followed by support level. @@ -77,4 +77,7 @@ Definition of columns: #### References: - [1] [GCE conformance test result](https://gist.github.com/erictune/4cabc010906afbcc5061) + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/README.md?pixel)]() + diff --git a/docs/getting-started-guides/aws-coreos.md b/docs/getting-started-guides/aws-coreos.md index 02804ee60e1..70e146cd7fc 100644 --- a/docs/getting-started-guides/aws-coreos.md +++ b/docs/getting-started-guides/aws-coreos.md @@ -228,4 +228,6 @@ kubectl delete pods hello ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/aws-coreos.md?pixel)]() + diff --git a/docs/getting-started-guides/aws.md b/docs/getting-started-guides/aws.md index b69b2312e05..af04aa5b94a 100644 --- a/docs/getting-started-guides/aws.md +++ b/docs/getting-started-guides/aws.md @@ -110,4 +110,6 @@ Please see the [Kubernetes docs](https://github.com/GoogleCloudPlatform/kubernet and using a Kubernetes cluster. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/aws.md?pixel)]() + diff --git a/docs/getting-started-guides/aws/kubectl.md b/docs/getting-started-guides/aws/kubectl.md index 0d71f7c427c..b3424dd3de1 100644 --- a/docs/getting-started-guides/aws/kubectl.md +++ b/docs/getting-started-guides/aws/kubectl.md @@ -35,4 +35,6 @@ ssh -f -nNT -L 8080:127.0.0.1:8080 core@ ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/aws/kubectl.md?pixel)]() + diff --git a/docs/getting-started-guides/azure.md b/docs/getting-started-guides/azure.md index af04ef7d9be..c975d6828e5 100644 --- a/docs/getting-started-guides/azure.md +++ b/docs/getting-started-guides/azure.md @@ -73,4 +73,6 @@ cluster/kube-down.sh ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/azure.md?pixel)]() + diff --git a/docs/getting-started-guides/binary_release.md b/docs/getting-started-guides/binary_release.md index 06a43083091..e09d89c0c3d 100644 --- a/docs/getting-started-guides/binary_release.md +++ b/docs/getting-started-guides/binary_release.md @@ -37,4 +37,6 @@ make release For more details on the release process see the [`build/` directory](../../build/) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/binary_release.md?pixel)]() + diff --git a/docs/getting-started-guides/centos/centos_manual_config.md b/docs/getting-started-guides/centos/centos_manual_config.md index b10c36283e1..19a5526d223 100644 --- a/docs/getting-started-guides/centos/centos_manual_config.md +++ b/docs/getting-started-guides/centos/centos_manual_config.md @@ -180,4 +180,6 @@ centos-minion Ready You should have a functional cluster, check out [101](../../../examples/walkthrough/README.md)! + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/centos/centos_manual_config.md?pixel)]() + diff --git a/docs/getting-started-guides/cloudstack.md b/docs/getting-started-guides/cloudstack.md index 16b8ac01795..8bb4dfba72c 100644 --- a/docs/getting-started-guides/cloudstack.md +++ b/docs/getting-started-guides/cloudstack.md @@ -98,11 +98,6 @@ SSH to it using the key that was created and using the _core_ user and you can l e9af8293... role=node - - - - - - - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/cloudstack.md?pixel)]() + diff --git a/docs/getting-started-guides/coreos.md b/docs/getting-started-guides/coreos.md index aac5136c366..9f523ceea1d 100644 --- a/docs/getting-started-guides/coreos.md +++ b/docs/getting-started-guides/coreos.md @@ -25,4 +25,6 @@ There are multiple guides on running Kubernetes with [CoreOS](http://coreos.com) * [Resizable multi-node cluster on Azure with Weave](coreos/azure/README.md) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/coreos.md?pixel)]() + diff --git a/docs/getting-started-guides/coreos/azure/README.md b/docs/getting-started-guides/coreos/azure/README.md index e51301f6dd5..453cbd170f3 100644 --- a/docs/getting-started-guides/coreos/azure/README.md +++ b/docs/getting-started-guides/coreos/azure/README.md @@ -217,4 +217,6 @@ If you don't wish care about the Azure bill, you can tear down the cluster. It's By the way, with the scripts shown, you can deploy multiple clusters, if you like :) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/coreos/azure/README.md?pixel)]() + diff --git a/docs/getting-started-guides/coreos/bare_metal_offline.md b/docs/getting-started-guides/coreos/bare_metal_offline.md index 74d5da6de11..801ae680cf2 100644 --- a/docs/getting-started-guides/coreos/bare_metal_offline.md +++ b/docs/getting-started-guides/coreos/bare_metal_offline.md @@ -671,4 +671,6 @@ Kill all pods: for i in `kubectl get pods | awk '{print $1}'`; do kubectl stop pod $i; done + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/coreos/bare_metal_offline.md?pixel)]() + diff --git a/docs/getting-started-guides/coreos/coreos_multinode_cluster.md b/docs/getting-started-guides/coreos/coreos_multinode_cluster.md index 3602d6c92e5..5db8d6f6864 100644 --- a/docs/getting-started-guides/coreos/coreos_multinode_cluster.md +++ b/docs/getting-started-guides/coreos/coreos_multinode_cluster.md @@ -150,4 +150,6 @@ hdiutil makehybrid -iso -joliet -joliet-volume-name "config-2" -joliet -o node.i Boot one or more the [vmware image](https://coreos.com/docs/running-coreos/platforms/vmware) using `node.iso` as a config drive. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/coreos/coreos_multinode_cluster.md?pixel)]() + diff --git a/docs/getting-started-guides/docker-multinode.md b/docs/getting-started-guides/docker-multinode.md index 5105e9e0915..63369f79e42 100644 --- a/docs/getting-started-guides/docker-multinode.md +++ b/docs/getting-started-guides/docker-multinode.md @@ -66,4 +66,6 @@ Once your cluster has been created you can [test it out](docker-multinode/testin For more complete applications, please look in the [examples directory](../../examples/) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/docker-multinode.md?pixel)]() + diff --git a/docs/getting-started-guides/docker-multinode/master.md b/docs/getting-started-guides/docker-multinode/master.md index bdf3bebd08c..9241aaa5f46 100644 --- a/docs/getting-started-guides/docker-multinode/master.md +++ b/docs/getting-started-guides/docker-multinode/master.md @@ -157,4 +157,6 @@ If all else fails, ask questions on IRC at #google-containers. Move on to [adding one or more workers](worker.md) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/docker-multinode/master.md?pixel)]() + diff --git a/docs/getting-started-guides/docker-multinode/testing.md b/docs/getting-started-guides/docker-multinode/testing.md index d795621ad0b..8e62100901d 100644 --- a/docs/getting-started-guides/docker-multinode/testing.md +++ b/docs/getting-started-guides/docker-multinode/testing.md @@ -71,4 +71,7 @@ kubectl get pods You should see pods landing on the newly added machine. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/docker-multinode/testing.md?pixel)]() + diff --git a/docs/getting-started-guides/docker-multinode/worker.md b/docs/getting-started-guides/docker-multinode/worker.md index 119b5e9a5dc..c4957bfa1d7 100644 --- a/docs/getting-started-guides/docker-multinode/worker.md +++ b/docs/getting-started-guides/docker-multinode/worker.md @@ -122,4 +122,6 @@ sudo docker run -d --net=host --privileged gcr.io/google_containers/hyperkube:v0 Move on to [testing your cluster](testing.md) or [add another node](#adding-a-kubernetes-worker-node-via-docker) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/docker-multinode/worker.md?pixel)]() + diff --git a/docs/getting-started-guides/docker.md b/docs/getting-started-guides/docker.md index 87aff81544a..837a0e48884 100644 --- a/docs/getting-started-guides/docker.md +++ b/docs/getting-started-guides/docker.md @@ -113,4 +113,6 @@ the cluster, you need to first kill the kubelet container, and then any other co You may use ```docker ps -a | awk '{print $1}' | xargs docker kill```, note this removes _all_ containers running under Docker, so use with caution. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/docker.md?pixel)]() + diff --git a/docs/getting-started-guides/fedora/fedora_ansible_config.md b/docs/getting-started-guides/fedora/fedora_ansible_config.md index bd55b353618..8c8bc97f0c8 100644 --- a/docs/getting-started-guides/fedora/fedora_ansible_config.md +++ b/docs/getting-started-guides/fedora/fedora_ansible_config.md @@ -257,4 +257,6 @@ curl http://localhost That's it ! + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/fedora/fedora_ansible_config.md?pixel)]() + diff --git a/docs/getting-started-guides/fedora/fedora_manual_config.md b/docs/getting-started-guides/fedora/fedora_manual_config.md index 5c63138ea23..f278ed7c6d5 100644 --- a/docs/getting-started-guides/fedora/fedora_manual_config.md +++ b/docs/getting-started-guides/fedora/fedora_manual_config.md @@ -207,4 +207,6 @@ $ kubectl delete -f node.json You should have a functional cluster, check out [101](../../../examples/walkthrough/README.md)! + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/fedora/fedora_manual_config.md?pixel)]() + diff --git a/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md index 955a6a691a8..660d356e85b 100644 --- a/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md +++ b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md @@ -191,4 +191,6 @@ PING 18.16.90.4 (18.16.90.4) 56(84) bytes of data. * Now kubernetes multi-node cluster is set up with overlay networking set up by flannel. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md?pixel)]() + diff --git a/docs/getting-started-guides/gce.md b/docs/getting-started-guides/gce.md index 229667badc6..f75f9b90e62 100644 --- a/docs/getting-started-guides/gce.md +++ b/docs/getting-started-guides/gce.md @@ -226,4 +226,6 @@ field values: * Allowed Protocols and Port: `tcp:1-65535;udp:1-65535;icmp` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/gce.md?pixel)]() + diff --git a/docs/getting-started-guides/juju.md b/docs/getting-started-guides/juju.md index f9e335c4be8..256aa174614 100644 --- a/docs/getting-started-guides/juju.md +++ b/docs/getting-started-guides/juju.md @@ -247,4 +247,6 @@ MAAS (bare metal) | TBD GCE | TBD + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/juju.md?pixel)]() + diff --git a/docs/getting-started-guides/libvirt-coreos.md b/docs/getting-started-guides/libvirt-coreos.md index 9f0a13fd803..f474fba141f 100644 --- a/docs/getting-started-guides/libvirt-coreos.md +++ b/docs/getting-started-guides/libvirt-coreos.md @@ -282,4 +282,6 @@ usermod -a -G libvirtd $USER Ensure libvirtd has been restarted since ebtables was installed. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/libvirt-coreos.md?pixel)]() + diff --git a/docs/getting-started-guides/locally.md b/docs/getting-started-guides/locally.md index 674d3fb34be..f038fffca26 100644 --- a/docs/getting-started-guides/locally.md +++ b/docs/getting-started-guides/locally.md @@ -145,4 +145,6 @@ One or more of the kubernetes daemons might've crashed. Tail the logs of each in The local-up-cluster.sh script doesn't start a DNS service. Similar situation can be found [here](https://github.com/GoogleCloudPlatform/kubernetes/issues/6667). You can start a manually. Related documents can be found [here](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/cluster/addons/dns#how-do-i-configure-it) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/locally.md?pixel)]() + diff --git a/docs/getting-started-guides/logging-elasticsearch.md b/docs/getting-started-guides/logging-elasticsearch.md index 759e8a4920f..1d33d651a21 100644 --- a/docs/getting-started-guides/logging-elasticsearch.md +++ b/docs/getting-started-guides/logging-elasticsearch.md @@ -243,4 +243,6 @@ Starting to serve on localhost:8001 Now you can visit the URL [http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging](http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging) to contact Elasticsearch and [http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kibana-logging](http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kibana-logging) to access the Kibana viewer. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/logging-elasticsearch.md?pixel)]() + diff --git a/docs/getting-started-guides/logging.md b/docs/getting-started-guides/logging.md index 61b6e4b11a2..e185f0073f8 100644 --- a/docs/getting-started-guides/logging.md +++ b/docs/getting-started-guides/logging.md @@ -205,4 +205,7 @@ This page has touched briefly on the underlying mechanisms that support gatherin Some of the material in this section also appears in the blog article [Cluster Level Logging with Kubernetes](http://blog.kubernetes.io/2015/06/cluster-level-logging-with-kubernetes.html). + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/logging.md?pixel)]() + diff --git a/docs/getting-started-guides/mesos.md b/docs/getting-started-guides/mesos.md index 5a66a260c8d..55b12f8e2e8 100644 --- a/docs/getting-started-guides/mesos.md +++ b/docs/getting-started-guides/mesos.md @@ -224,4 +224,7 @@ Future work will add instructions to this guide to enable support for Kubernetes [9]: ../../examples/ [10]: http://open.mesosphere.com/getting-started/cloud/google/mesosphere/#vpn-setup + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/mesos.md?pixel)]() + diff --git a/docs/getting-started-guides/ovirt.md b/docs/getting-started-guides/ovirt.md index a568740f0f3..d569cc4c50f 100644 --- a/docs/getting-started-guides/ovirt.md +++ b/docs/getting-started-guides/ovirt.md @@ -68,4 +68,6 @@ This short screencast demonstrates how the oVirt Cloud Provider can be used to d [![Screencast](http://img.youtube.com/vi/JyyST4ZKne8/0.jpg)](http://www.youtube.com/watch?v=JyyST4ZKne8) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/ovirt.md?pixel)]() + diff --git a/docs/getting-started-guides/rackspace.md b/docs/getting-started-guides/rackspace.md index 95ed7af1abc..b2d3093dd39 100644 --- a/docs/getting-started-guides/rackspace.md +++ b/docs/getting-started-guides/rackspace.md @@ -79,4 +79,6 @@ There is a specific `cluster/rackspace` directory with the scripts for the follo - eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/rackspace.md?pixel)]() + diff --git a/docs/getting-started-guides/rkt/README.md b/docs/getting-started-guides/rkt/README.md index 0b4c1de7931..af16112a56c 100644 --- a/docs/getting-started-guides/rkt/README.md +++ b/docs/getting-started-guides/rkt/README.md @@ -103,4 +103,6 @@ See [a simple nginx example](../../../examples/simple-nginx.md) to try out your For more complete applications, please look in the [examples directory](../../../examples/). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/rkt/README.md?pixel)]() + diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md index eefa17d879c..2c1fcb88bdc 100644 --- a/docs/getting-started-guides/scratch.md +++ b/docs/getting-started-guides/scratch.md @@ -767,5 +767,6 @@ If you run into trouble, please see the section on [troubleshooting](gce.md#trou [google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on IRC at #google-containers on freenode. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/scratch.md?pixel)]() + diff --git a/docs/getting-started-guides/ubuntu.md b/docs/getting-started-guides/ubuntu.md index d57d440819d..de23165cbc4 100644 --- a/docs/getting-started-guides/ubuntu.md +++ b/docs/getting-started-guides/ubuntu.md @@ -206,4 +206,6 @@ Please try: 4. You can also customize your own settings in `/etc/default/{component_name}` after configured success. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/ubuntu.md?pixel)]() + diff --git a/docs/getting-started-guides/vagrant.md b/docs/getting-started-guides/vagrant.md index 84a78c08139..bdfb6faf4d1 100644 --- a/docs/getting-started-guides/vagrant.md +++ b/docs/getting-started-guides/vagrant.md @@ -353,4 +353,6 @@ export KUBERNETES_VAGRANT_USE_NFS=true ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/vagrant.md?pixel)]() + diff --git a/docs/getting-started-guides/vsphere.md b/docs/getting-started-guides/vsphere.md index 88251bab79b..13b97f8544b 100644 --- a/docs/getting-started-guides/vsphere.md +++ b/docs/getting-started-guides/vsphere.md @@ -102,4 +102,6 @@ going on (find yourself authorized with your SSH key, or use the password `kube` otherwise). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/vsphere.md?pixel)]() + diff --git a/docs/glossary.md b/docs/glossary.md index 1d3639dcb5f..895a078294e 100644 --- a/docs/glossary.md +++ b/docs/glossary.md @@ -69,4 +69,6 @@ Volumes build upon [Docker Volumes](https://docs.docker.com/userguide/dockervolu directory and/or device. See [volumes](volumes.md). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/glossary.md?pixel)]() + diff --git a/docs/high-availability.md b/docs/high-availability.md index 1e18868b311..05b87d62c94 100644 --- a/docs/high-availability.md +++ b/docs/high-availability.md @@ -230,4 +230,7 @@ We indeed have an initial proof of concept tester for this, which is available [ It implements the major concepts (with a few minor reductions for simplicity), of the podmaster HA implementation alongside a quick smoke test using k8petstore. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/high-availability.md?pixel)]() + diff --git a/docs/identifiers.md b/docs/identifiers.md index 6765e63eb07..a462f27f36c 100644 --- a/docs/identifiers.md +++ b/docs/identifiers.md @@ -24,4 +24,6 @@ Names are generally client-provided. Only one object of a given kind can have a UID are generated by Kubernetes. Every object created over the whole lifetime of a Kubernetes cluster has a distinct UID (i.e., they are spatially and temporally unique). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/identifiers.md?pixel)]() + diff --git a/docs/images.md b/docs/images.md index 36c7f29d645..bcfbcc39128 100644 --- a/docs/images.md +++ b/docs/images.md @@ -163,7 +163,7 @@ where node creation is automated. Kubernetes supports specifying registry keys on a pod. First, create a `.dockercfg`, such as running `docker login `. -Then put the resulting `.dockercfg` file into a [secret resource](../docs/secrets.md). For example: +Then put the resulting `.dockercfg` file into a [secret resource](secrets.md). For example: ``` $ docker login Username: janedoe @@ -215,7 +215,7 @@ spec: ``` This needs to be done for each pod that is using a private registry. However, setting of this field can be automated by setting the imagePullSecrets -in a [serviceAccount](../docs/service_accounts.md) resource. +in a [serviceAccount](service_accounts.md) resource. Currently, all pods will potentially have read access to any images which were pulled using imagePullSecrets. That is, imagePullSecrets does *NOT* protect your @@ -250,4 +250,6 @@ common use cases and suggested solutions. - NOT supported yet. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/images.md?pixel)]() + diff --git a/docs/kube-apiserver.md b/docs/kube-apiserver.md index 60294ffec39..69c34d3164e 100644 --- a/docs/kube-apiserver.md +++ b/docs/kube-apiserver.md @@ -84,4 +84,7 @@ cluster's shared state through which all other components interact. ###### Auto generated by spf13/cobra at 2015-07-06 18:03:28.852677626 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kube-apiserver.md?pixel)]() + diff --git a/docs/kube-controller-manager.md b/docs/kube-controller-manager.md index b5b10f1fedb..d920643885a 100644 --- a/docs/kube-controller-manager.md +++ b/docs/kube-controller-manager.md @@ -62,4 +62,7 @@ controller, and serviceaccounts controller. ###### Auto generated by spf13/cobra at 2015-07-06 18:03:31.507732064 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kube-controller-manager.md?pixel)]() + diff --git a/docs/kube-proxy.md b/docs/kube-proxy.md index bc3ba3ee35b..488adf02e9b 100644 --- a/docs/kube-proxy.md +++ b/docs/kube-proxy.md @@ -44,4 +44,7 @@ with the apiserver API to configure the proxy. ###### Auto generated by spf13/cobra at 2015-07-06 18:03:37.657112759 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kube-proxy.md?pixel)]() + diff --git a/docs/kube-scheduler.md b/docs/kube-scheduler.md index ccddb3585b8..b46a3bfb198 100644 --- a/docs/kube-scheduler.md +++ b/docs/kube-scheduler.md @@ -43,4 +43,7 @@ through the API as necessary. ###### Auto generated by spf13/cobra at 2015-07-06 18:03:39.24859096 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kube-scheduler.md?pixel)]() + diff --git a/docs/kubeconfig-file.md b/docs/kubeconfig-file.md index e9238a9c44b..1388d39abbf 100644 --- a/docs/kubeconfig-file.md +++ b/docs/kubeconfig-file.md @@ -163,4 +163,6 @@ $kubectl config use-context federal-context ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kubeconfig-file.md?pixel)]() + diff --git a/docs/kubelet.md b/docs/kubelet.md index ec0b4c2ea8b..5f09185b5b3 100644 --- a/docs/kubelet.md +++ b/docs/kubelet.md @@ -100,4 +100,7 @@ HTTP server: The kubelet can also listen for HTTP and respond to a simple API ###### Auto generated by spf13/cobra at 2015-07-06 18:03:36.451093085 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kubelet.md?pixel)]() + diff --git a/docs/labels.md b/docs/labels.md index a5a3d861f56..7459055322e 100644 --- a/docs/labels.md +++ b/docs/labels.md @@ -120,4 +120,6 @@ Pods (and other objects) may belong to multiple sets simultaneously, which enabl Concerning API: we may extend such filtering to DELETE operations in the future. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/labels.md?pixel)]() + diff --git a/docs/logging.md b/docs/logging.md index 9e5d8538cef..a6111ff066f 100644 --- a/docs/logging.md +++ b/docs/logging.md @@ -82,4 +82,7 @@ describes how to ingest cluster level logs into Elasticsearch and view them usin Cluster level logging only collects the standard output and standard error output of the applications running in containers. The guide [Collecting log files within containers with Fluentd](../contrib/logging/fluentd-sidecar-gcp/README.md) explains how the log files of applications can also be ingested into Google Cloud logging. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/logging.md?pixel)]() + diff --git a/docs/monitoring.md b/docs/monitoring.md index 6ff0affe8df..9884b7f9d92 100644 --- a/docs/monitoring.md +++ b/docs/monitoring.md @@ -70,4 +70,7 @@ Now that you’ve learned a bit about Heapster, feel free to try it out on your *Authors: Vishnu Kannan and Victor Marmol, Google Software Engineers.* *This article was originally posted in [Kubernetes blog](http://blog.kubernetes.io/2015/05/resource-usage-monitoring-kubernetes.html).* + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/monitoring.md?pixel)]() + diff --git a/docs/namespaces.md b/docs/namespaces.md index f040610abe8..74573828ff8 100644 --- a/docs/namespaces.md +++ b/docs/namespaces.md @@ -21,4 +21,6 @@ Use of multiple namespaces is optional. For small teams, they may not be needed Namespaces are still under development. For now, the best documentation is the [Namespaces Design Document](design/namespaces.md). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/namespaces.md?pixel)]() + diff --git a/docs/networking.md b/docs/networking.md index d3007322aba..c8cb1f96cc5 100644 --- a/docs/networking.md +++ b/docs/networking.md @@ -207,4 +207,6 @@ plans are described in more detail in the [networking design document](design/networking.md). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/networking.md?pixel)]() + diff --git a/docs/node.md b/docs/node.md index 4fd9d6299c0..48fc66dc599 100644 --- a/docs/node.md +++ b/docs/node.md @@ -214,4 +214,7 @@ Set the `cpu` and `memory` values to the amount of resources you want to reserve Place the file in the manifest directory (`--config=DIR` flag of kubelet). Do this on each kubelet where you want to reserve resources. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/node.md?pixel)]() + diff --git a/docs/overview.md b/docs/overview.md index a814c9e0cb9..2cad8218549 100644 --- a/docs/overview.md +++ b/docs/overview.md @@ -42,5 +42,6 @@ Other details: * Monitoring using [CAdvisor](https://github.com/google/cadvisor) and [Heapster](https://github.com/GoogleCloudPlatform/heapster) - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/overview.md?pixel)]() + diff --git a/docs/ovs-networking.md b/docs/ovs-networking.md index 1204a46054e..f9de8099f91 100644 --- a/docs/ovs-networking.md +++ b/docs/ovs-networking.md @@ -28,4 +28,6 @@ Also, an OVS bridge is created(obr0) and added as a port to the kbr0 bridge. All Routing rules enable any 10.244.0.0/16 target to become reachable via the OVS bridge connected with the tunnels. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/ovs-networking.md?pixel)]() + diff --git a/docs/persistent-volumes.md b/docs/persistent-volumes.md index 17716a24b3e..7bfc560785f 100644 --- a/docs/persistent-volumes.md +++ b/docs/persistent-volumes.md @@ -210,4 +210,7 @@ spec: ``` + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/persistent-volumes.md?pixel)]() + diff --git a/docs/pod-states.md b/docs/pod-states.md index cdcbb2001e7..a16e72e633d 100644 --- a/docs/pod-states.md +++ b/docs/pod-states.md @@ -119,4 +119,6 @@ If a node dies or is disconnected from the rest of the cluster, some entity with * If running under a controller, pod will be recreated elsewhere + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/pod-states.md?pixel)]() + diff --git a/docs/pods.md b/docs/pods.md index 314f2bed6cc..fcf165b7f55 100644 --- a/docs/pods.md +++ b/docs/pods.md @@ -92,5 +92,6 @@ Pod is exposed as a primitive in order to facilitate: The current best practice for pets is to create a replication controller with `replicas` equal to `1` and a corresponding service. If you find this cumbersome, please comment on [issue #260](https://github.com/GoogleCloudPlatform/kubernetes/issues/260). - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/pods.md?pixel)]() + diff --git a/docs/proposals/autoscaling.md b/docs/proposals/autoscaling.md index bd8244abb6e..e56a22566ad 100644 --- a/docs/proposals/autoscaling.md +++ b/docs/proposals/autoscaling.md @@ -267,5 +267,6 @@ temporarily disable negative decrement thresholds until the deployment process i an auto-scaler to be able to grow capacity during a deployment than to shrink the number of instances precisely. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/autoscaling.md?pixel)]() + diff --git a/docs/proposals/federation.md b/docs/proposals/federation.md index a8e9813ba32..e61163db096 100644 --- a/docs/proposals/federation.md +++ b/docs/proposals/federation.md @@ -445,4 +445,6 @@ their primary zookeeper replica? And now how do I do a shared, highly available redis database? + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/federation.md?pixel)]() + diff --git a/docs/proposals/high-availability.md b/docs/proposals/high-availability.md index 4525f709077..ee03b28e82d 100644 --- a/docs/proposals/high-availability.md +++ b/docs/proposals/high-availability.md @@ -60,4 +60,6 @@ There is a short window after a new master acquires the lease, during which data * Is there a desire to keep track of all nodes for a specific component type? + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/high-availability.md?pixel)]() + diff --git a/docs/replication-controller.md b/docs/replication-controller.md index e811878b9cf..a754059b725 100644 --- a/docs/replication-controller.md +++ b/docs/replication-controller.md @@ -98,4 +98,6 @@ In addition to running multiple releases of an application while a rolling updat For instance, a service might target all pods with `tier in (frontend), environment in (prod)`. Now say you have 10 replicated pods that make up this tier. But you want to be able to 'canary' a new version of this component. You could set up a replication controller with `replicas` set to 9 for the bulk of the replicas, with labels `tier=frontend, environment=prod, track=stable`, and another replication controller with `replicas` set to 1 for the canary, with labels `tier=frontend, environment=prod, track=canary`. Now the service is covering both the canary and non-canary pods. But you can mess with the replication controllers separately to test things out, monitor the results, etc. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/replication-controller.md?pixel)]() + diff --git a/docs/resource_quota_admin.md b/docs/resource_quota_admin.md index bde7671b2d9..b45b0eed7bb 100644 --- a/docs/resource_quota_admin.md +++ b/docs/resource_quota_admin.md @@ -115,4 +115,6 @@ writing a 'controller' which watches the quota usage and adjusts the quota hard limits of each namespace. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/resource_quota_admin.md?pixel)]() + diff --git a/docs/roadmap.md b/docs/roadmap.md index 6d1fb9dab07..7fadd6e2086 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -105,4 +105,6 @@ In terms of performance, the objectives include: - startup time at the 99%tile ([#3552](https://github.com/GoogleCloudPlatform/kubernetes/issues/3952)) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/roadmap.md?pixel)]() + diff --git a/docs/salt.md b/docs/salt.md index 5e16bb27f70..ac10e314bfc 100644 --- a/docs/salt.md +++ b/docs/salt.md @@ -112,4 +112,6 @@ We should define a grains.conf key that captures more specifically what network The [cluster/saltbase](../cluster/saltbase/) tree has more details on the current SaltStack configuration. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/salt.md?pixel)]() + diff --git a/docs/secrets.md b/docs/secrets.md index 141089c3c0a..cce4040ebf2 100644 --- a/docs/secrets.md +++ b/docs/secrets.md @@ -499,4 +499,6 @@ Pod level](#use-case-two-containers). single node. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/secrets.md?pixel)]() + diff --git a/docs/security_context.md b/docs/security_context.md index c5d0d45fe05..d85b4460431 100644 --- a/docs/security_context.md +++ b/docs/security_context.md @@ -17,4 +17,6 @@ certainly want the docs that go with that version. A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. See [security context design](design/security_context.md) for more details. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/security_context.md?pixel)]() + diff --git a/docs/service_accounts.md b/docs/service_accounts.md index 06618cf2a0c..29d92cc3f36 100644 --- a/docs/service_accounts.md +++ b/docs/service_accounts.md @@ -104,4 +104,6 @@ TODO explain: - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/service_accounts.md?pixel)]() + diff --git a/docs/service_accounts_admin.md b/docs/service_accounts_admin.md index eb299f9dce3..8f4d3a107bb 100644 --- a/docs/service_accounts_admin.md +++ b/docs/service_accounts_admin.md @@ -95,4 +95,7 @@ $ kubectl describe secret mysecretname kubectl delete secret mysecretname ``` + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/service_accounts_admin.md?pixel)]() + diff --git a/docs/services-firewalls.md b/docs/services-firewalls.md index 7bc9c74d7d1..6e56356328a 100644 --- a/docs/services-firewalls.md +++ b/docs/services-firewalls.md @@ -48,4 +48,7 @@ Consequently, please be careful when opening firewalls in Google Compute Engine ### Other cloud providers Coming soon. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/services-firewalls.md?pixel)]() + diff --git a/docs/services.md b/docs/services.md index 0c760aa396e..b2e9bf8c16f 100644 --- a/docs/services.md +++ b/docs/services.md @@ -507,5 +507,6 @@ of which `Pods` they are actually accessing. ![Services detailed diagram](services_detail.png) - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/services.md?pixel)]() + diff --git a/docs/sharing-clusters.md b/docs/sharing-clusters.md index 6e0bb5279e1..a9b809b0553 100644 --- a/docs/sharing-clusters.md +++ b/docs/sharing-clusters.md @@ -119,5 +119,6 @@ export $KUBECONFIG=path/to/other/.kube/config Detailed examples and explanation of `kubeconfig` loading/merging rules can be found in [kubeconfig-file.md](kubeconfig-file.md). - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/sharing-clusters.md?pixel)]() + diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 142af647a0c..333b1579eb9 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -18,4 +18,6 @@ Sometimes things go wrong. This guide is aimed at making them right. It has tw * [Troubleshooting your cluster](cluster-troubleshooting.md) - Useful for cluster administrators and people whose Kubernetes cluster is unhappy. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/troubleshooting.md?pixel)]() + diff --git a/docs/ui.md b/docs/ui.md index 94e327aea18..fddd25b0577 100644 --- a/docs/ui.md +++ b/docs/ui.md @@ -52,4 +52,7 @@ Other views (Pods, Nodes, Replication Controllers, Services, and Events) simply ## More Information For more information, see the [Kubernetes UI development document](../www/README.md) in the www directory. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/ui.md?pixel)]() + diff --git a/docs/user-guide.md b/docs/user-guide.md index 717f9b0f072..9f593a49f98 100644 --- a/docs/user-guide.md +++ b/docs/user-guide.md @@ -52,7 +52,7 @@ kubernetes API, or to contribute directly to the kubernetes project. (e.g. ssh keys, passwords) separately from the Pods that use them, protecting the sensitive data from proliferation by tools that process pods. -* **Accessing the API and other cluster services via a Proxy** [docs/accessing-the-cluster.md](../docs/accessing-the-cluster.md) +* **Accessing the API and other cluster services via a Proxy** [accessing-the-cluster.md](accessing-the-cluster.md) * **API Overview** ([api.md](api.md)): Pointers to API documentation on various topics and explanation of Kubernetes's approaches to API changes and API versioning. @@ -117,5 +117,6 @@ for i in *.md; do grep -r $i . | grep -v "^\./$i" > /dev/null; rv=$?; if [[ $rv * Frequently asked questions are answered on this project's [wiki](https://github.com/GoogleCloudPlatform/kubernetes/wiki). - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide.md?pixel)]() + diff --git a/docs/user-guide/configuring-containers.md b/docs/user-guide/configuring-containers.md index bf3c0a97558..44cdea15498 100644 --- a/docs/user-guide/configuring-containers.md +++ b/docs/user-guide/configuring-containers.md @@ -159,4 +159,6 @@ Terminated pods aren’t currently automatically deleted, so that you can observ On the other hand, containers and their logs are eventually deleted automatically in order to free up disk space on the nodes. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/configuring-containers.md?pixel)]() + diff --git a/docs/user-guide/connecting-applications.md b/docs/user-guide/connecting-applications.md index 9aad8bd62ba..c684464f91f 100644 --- a/docs/user-guide/connecting-applications.md +++ b/docs/user-guide/connecting-applications.md @@ -230,5 +230,6 @@ $ kubectl get service nginxsvc -o json | grep \"ip\" Now you have a load balancer that automatically does what you would’ve in the previous step. Note that you cannot directly curl your nodes on port 80, you need to go to the ip of the load balancer. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/connecting-applications.md?pixel)]() + diff --git a/docs/user-guide/connecting-to-applications-port-forward.md b/docs/user-guide/connecting-to-applications-port-forward.md index 17c92a82823..90d49cb443f 100644 --- a/docs/user-guide/connecting-to-applications-port-forward.md +++ b/docs/user-guide/connecting-to-applications-port-forward.md @@ -13,7 +13,7 @@ certainly want the docs that go with that version. #Connecting to applications: kubectl port-forward -kubectl port-forward forwards connections to a local port to a port on a pod. Its man page is available [here](../../docs/user-guide/kubectl/kubectl_port-forward.md). Compared to [kubectl proxy](../../docs/accessing-the-cluster.md#using-kubectl-proxy), `kubectl port-forward` is more generic as it can forward TCP traffic while `kubectl proxy` can only forward HTTP traffic. This guide demonstrates how to use `kubectl port-forward` to connect to a Redis database, which may be useful for database debugging. +kubectl port-forward forwards connections to a local port to a port on a pod. Its man page is available [here](kubectl/kubectl_port-forward.md). Compared to [kubectl proxy](../../docs/accessing-the-cluster.md#using-kubectl-proxy), `kubectl port-forward` is more generic as it can forward TCP traffic while `kubectl proxy` can only forward HTTP traffic. This guide demonstrates how to use `kubectl port-forward` to connect to a Redis database, which may be useful for database debugging. ## Creating a Redis master @@ -51,4 +51,7 @@ PONG ``` Now one can debug the database from the local workstation. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/connecting-to-applications-port-forward.md?pixel)]() + diff --git a/docs/user-guide/connecting-to-applications-proxy.md b/docs/user-guide/connecting-to-applications-proxy.md index b6e814ddbb9..57478cf187a 100644 --- a/docs/user-guide/connecting-to-applications-proxy.md +++ b/docs/user-guide/connecting-to-applications-proxy.md @@ -34,7 +34,6 @@ Starting to serve on localhost:8001 Now you can access the kube-ui service on your local workstation at [http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui](http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui) -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/connecting-to-applications-1.md?pixel)]() - - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/connecting-to-applications-proxy.md?pixel)]() + diff --git a/docs/user-guide/deploying-applications.md b/docs/user-guide/deploying-applications.md index 079f387354e..03ccd2ea980 100644 --- a/docs/user-guide/deploying-applications.md +++ b/docs/user-guide/deploying-applications.md @@ -97,7 +97,7 @@ CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS APP my-nginx nginx nginx app=nginx 2 nginx ``` -More importantly, the pod template’s labels are used to create a [`selector`](../../docs/labels.md#label-selectors) that will match pods carrying those labels. You can see this field by requesting it using the [Go template output format of `kubectl get`](../../docs/user-guide/kubectl/kubectl_get.md): +More importantly, the pod template’s labels are used to create a [`selector`](../../docs/labels.md#label-selectors) that will match pods carrying those labels. You can see this field by requesting it using the [Go template output format of `kubectl get`](kubectl/kubectl_get.md): ```bash $ kubectl get rc my-nginx -o template --template="{{.spec.selector}}" map[app:nginx] @@ -106,4 +106,6 @@ map[app:nginx] You could also specify the `selector` explicitly, such as if you wanted to specify labels in the pod template that you didn’t want to select on, but you should ensure that the selector will match the labels of the pods created from the pod template, and that it won’t match pods created by other replication controllers. The most straightforward way to ensure the latter is to create a unique label value for the replication controller, and to specify it in both the pod template’s labels and in the selector. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/deploying-applications.md?pixel)]() + diff --git a/docs/user-guide/getting-into-containers.md b/docs/user-guide/getting-into-containers.md index 8a746be3926..ea20d139008 100644 --- a/docs/user-guide/getting-into-containers.md +++ b/docs/user-guide/getting-into-containers.md @@ -67,4 +67,7 @@ root@storage:/data# ``` This gets you a terminal. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/getting-into-containers.md?pixel)]() + diff --git a/docs/user-guide/introspection-and-debugging.md b/docs/user-guide/introspection-and-debugging.md index e68ce4ba91b..29ff401520c 100644 --- a/docs/user-guide/introspection-and-debugging.md +++ b/docs/user-guide/introspection-and-debugging.md @@ -310,5 +310,6 @@ status: ``` - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/introspection-and-debugging.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl.md b/docs/user-guide/kubectl/kubectl.md index 72a4600d2d2..b8afe0c0ba7 100644 --- a/docs/user-guide/kubectl/kubectl.md +++ b/docs/user-guide/kubectl/kubectl.md @@ -80,6 +80,9 @@ kubectl * [kubectl stop](kubectl_stop.md) - Gracefully shut down a resource by name or filename. * [kubectl version](kubectl_version.md) - Print the client and server version information. -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.04001576 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.96000791 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_api-versions.md b/docs/user-guide/kubectl/kubectl_api-versions.md index 203176ad21b..b1637e216cd 100644 --- a/docs/user-guide/kubectl/kubectl_api-versions.md +++ b/docs/user-guide/kubectl/kubectl_api-versions.md @@ -63,6 +63,9 @@ kubectl api-versions ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.03979762 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.959722426 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_api-versions.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_cluster-info.md b/docs/user-guide/kubectl/kubectl_cluster-info.md index 52f62187b78..9340f624a70 100644 --- a/docs/user-guide/kubectl/kubectl_cluster-info.md +++ b/docs/user-guide/kubectl/kubectl_cluster-info.md @@ -63,6 +63,9 @@ kubectl cluster-info ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.039702166 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.959601452 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_cluster-info.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config.md b/docs/user-guide/kubectl/kubectl_config.md index 6d70297c719..f5667e21a60 100644 --- a/docs/user-guide/kubectl/kubectl_config.md +++ b/docs/user-guide/kubectl/kubectl_config.md @@ -76,6 +76,9 @@ kubectl config SUBCOMMAND * [kubectl config use-context](kubectl_config_use-context.md) - Sets the current-context in a kubeconfig file * [kubectl config view](kubectl_config_view.md) - displays Merged kubeconfig settings or a specified kubeconfig file. -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.039608227 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.959458886 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config_set-cluster.md b/docs/user-guide/kubectl/kubectl_config_set-cluster.md index 9ed9d226f4a..29ae0372d6f 100644 --- a/docs/user-guide/kubectl/kubectl_config_set-cluster.md +++ b/docs/user-guide/kubectl/kubectl_config_set-cluster.md @@ -78,6 +78,9 @@ $ kubectl config set-cluster e2e --insecure-skip-tls-verify=true ### SEE ALSO * [kubectl config](kubectl_config.md) - config modifies kubeconfig files -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.038569042 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.95861887 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config_set-cluster.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config_set-context.md b/docs/user-guide/kubectl/kubectl_config_set-context.md index ec2233daaec..a52a51c5210 100644 --- a/docs/user-guide/kubectl/kubectl_config_set-context.md +++ b/docs/user-guide/kubectl/kubectl_config_set-context.md @@ -71,6 +71,9 @@ $ kubectl config set-context gce --user=cluster-admin ### SEE ALSO * [kubectl config](kubectl_config.md) - config modifies kubeconfig files -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.039201244 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.958911281 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config_set-context.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config_set-credentials.md b/docs/user-guide/kubectl/kubectl_config_set-credentials.md index d432c5e0bbe..9f4926f5d4a 100644 --- a/docs/user-guide/kubectl/kubectl_config_set-credentials.md +++ b/docs/user-guide/kubectl/kubectl_config_set-credentials.md @@ -91,6 +91,9 @@ $ kubectl config set-credentials cluster-admin --client-certificate=~/.kube/admi ### SEE ALSO * [kubectl config](kubectl_config.md) - config modifies kubeconfig files -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.038679654 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.958785654 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config_set-credentials.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config_set.md b/docs/user-guide/kubectl/kubectl_config_set.md index 931d010100d..e4a49cffd2d 100644 --- a/docs/user-guide/kubectl/kubectl_config_set.md +++ b/docs/user-guide/kubectl/kubectl_config_set.md @@ -65,6 +65,9 @@ kubectl config set PROPERTY_NAME PROPERTY_VALUE ### SEE ALSO * [kubectl config](kubectl_config.md) - config modifies kubeconfig files -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.039309985 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.959031072 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config_set.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config_unset.md b/docs/user-guide/kubectl/kubectl_config_unset.md index 63cdb5b4a69..68d32364508 100644 --- a/docs/user-guide/kubectl/kubectl_config_unset.md +++ b/docs/user-guide/kubectl/kubectl_config_unset.md @@ -64,6 +64,9 @@ kubectl config unset PROPERTY_NAME ### SEE ALSO * [kubectl config](kubectl_config.md) - config modifies kubeconfig files -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.03940649 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.959148086 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config_unset.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config_use-context.md b/docs/user-guide/kubectl/kubectl_config_use-context.md index a1ec7856067..0223a5f7f6b 100644 --- a/docs/user-guide/kubectl/kubectl_config_use-context.md +++ b/docs/user-guide/kubectl/kubectl_config_use-context.md @@ -63,6 +63,9 @@ kubectl config use-context CONTEXT_NAME ### SEE ALSO * [kubectl config](kubectl_config.md) - config modifies kubeconfig files -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.03950086 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.959263442 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config_use-context.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_config_view.md b/docs/user-guide/kubectl/kubectl_config_view.md index 3214f26e1c9..1c0c6476a95 100644 --- a/docs/user-guide/kubectl/kubectl_config_view.md +++ b/docs/user-guide/kubectl/kubectl_config_view.md @@ -83,6 +83,9 @@ $ kubectl config view -o template --template='{{range .users}}{{ if eq .name "e2 ### SEE ALSO * [kubectl config](kubectl_config.md) - config modifies kubeconfig files -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.03846839 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.958490153 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_config_view.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_create.md b/docs/user-guide/kubectl/kubectl_create.md index fafee073c0b..ca65d669091 100644 --- a/docs/user-guide/kubectl/kubectl_create.md +++ b/docs/user-guide/kubectl/kubectl_create.md @@ -76,6 +76,9 @@ $ cat pod.json | kubectl create -f - ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.036742691 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.955765309 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_create.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_delete.md b/docs/user-guide/kubectl/kubectl_delete.md index 03b31e00359..925c8400caf 100644 --- a/docs/user-guide/kubectl/kubectl_delete.md +++ b/docs/user-guide/kubectl/kubectl_delete.md @@ -98,6 +98,9 @@ $ kubectl delete pods --all ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037057308 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.95616314 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_delete.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_describe.md b/docs/user-guide/kubectl/kubectl_describe.md index 58ad8c0e66d..241e4774736 100644 --- a/docs/user-guide/kubectl/kubectl_describe.md +++ b/docs/user-guide/kubectl/kubectl_describe.md @@ -89,6 +89,9 @@ $ kubectl describe pods frontend ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.036639846 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.955631296 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_describe.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_exec.md b/docs/user-guide/kubectl/kubectl_exec.md index a69ba535f73..ebbabfb9e1e 100644 --- a/docs/user-guide/kubectl/kubectl_exec.md +++ b/docs/user-guide/kubectl/kubectl_exec.md @@ -81,6 +81,9 @@ $ kubectl exec 123456-7890 -c ruby-container -i -t -- bash -il ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037624471 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.956874128 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_exec.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_expose.md b/docs/user-guide/kubectl/kubectl_expose.md index 64943e3f869..439cd775378 100644 --- a/docs/user-guide/kubectl/kubectl_expose.md +++ b/docs/user-guide/kubectl/kubectl_expose.md @@ -97,6 +97,9 @@ $ kubectl expose rc streamer --port=4100 --protocol=udp --name=video-stream ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.038219725 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.957615868 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_expose.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_get.md b/docs/user-guide/kubectl/kubectl_get.md index eb525b1382a..17e7e994450 100644 --- a/docs/user-guide/kubectl/kubectl_get.md +++ b/docs/user-guide/kubectl/kubectl_get.md @@ -105,6 +105,9 @@ $ kubectl get rc/web service/frontend pods/web-pod-13je7 ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.036494619 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.955450097 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_get.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_label.md b/docs/user-guide/kubectl/kubectl_label.md index 9d83b16b969..bb888be86a8 100644 --- a/docs/user-guide/kubectl/kubectl_label.md +++ b/docs/user-guide/kubectl/kubectl_label.md @@ -95,6 +95,9 @@ $ kubectl label pods foo bar- ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.038346279 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.958329854 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_label.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_logs.md b/docs/user-guide/kubectl/kubectl_logs.md index 7fbe0f5afab..cdf4bab4956 100644 --- a/docs/user-guide/kubectl/kubectl_logs.md +++ b/docs/user-guide/kubectl/kubectl_logs.md @@ -80,6 +80,9 @@ $ kubectl logs -f 123456-7890 ruby-container ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.03725996 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.956443079 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_logs.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_namespace.md b/docs/user-guide/kubectl/kubectl_namespace.md index 137dff8cffa..201ed615fc2 100644 --- a/docs/user-guide/kubectl/kubectl_namespace.md +++ b/docs/user-guide/kubectl/kubectl_namespace.md @@ -66,6 +66,9 @@ kubectl namespace [namespace] ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037159721 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.956297427 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_namespace.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_patch.md b/docs/user-guide/kubectl/kubectl_patch.md index 37c650943fe..2a762d43d55 100644 --- a/docs/user-guide/kubectl/kubectl_patch.md +++ b/docs/user-guide/kubectl/kubectl_patch.md @@ -74,6 +74,9 @@ kubectl patch node k8s-node-1 -p '{"spec":{"unschedulable":true}}' ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 18:16:24.525726093 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.956026887 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_patch.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_port-forward.md b/docs/user-guide/kubectl/kubectl_port-forward.md index 0a588b82f30..786c9a086a6 100644 --- a/docs/user-guide/kubectl/kubectl_port-forward.md +++ b/docs/user-guide/kubectl/kubectl_port-forward.md @@ -81,6 +81,9 @@ $ kubectl port-forward -p mypod 0:5000 ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037733037 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.957000233 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_port-forward.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_proxy.md b/docs/user-guide/kubectl/kubectl_proxy.md index a4f37f6764e..639d37ad608 100644 --- a/docs/user-guide/kubectl/kubectl_proxy.md +++ b/docs/user-guide/kubectl/kubectl_proxy.md @@ -98,6 +98,9 @@ $ kubectl proxy --api-prefix=/k8s-api ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037848292 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.957150329 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_proxy.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_replace.md b/docs/user-guide/kubectl/kubectl_replace.md index ccd38945bee..b0bc3cb9e34 100644 --- a/docs/user-guide/kubectl/kubectl_replace.md +++ b/docs/user-guide/kubectl/kubectl_replace.md @@ -83,6 +83,9 @@ kubectl replace --force -f pod.json ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.036845595 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.955895303 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_replace.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_rolling-update.md b/docs/user-guide/kubectl/kubectl_rolling-update.md index a69f3b10db8..c2d01588de2 100644 --- a/docs/user-guide/kubectl/kubectl_rolling-update.md +++ b/docs/user-guide/kubectl/kubectl_rolling-update.md @@ -97,6 +97,9 @@ $ kubectl rolling-update frontend --image=image:v2 ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037393307 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.956605022 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_rolling-update.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_run.md b/docs/user-guide/kubectl/kubectl_run.md index 0dbb44ba90b..dc7da381293 100644 --- a/docs/user-guide/kubectl/kubectl_run.md +++ b/docs/user-guide/kubectl/kubectl_run.md @@ -92,6 +92,9 @@ $ kubectl run nginx --image=nginx --overrides='{ "apiVersion": "v1", "spec": { . ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037967503 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.957298888 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_run.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_scale.md b/docs/user-guide/kubectl/kubectl_scale.md index 9cb5487b5ea..512d1bc5b19 100644 --- a/docs/user-guide/kubectl/kubectl_scale.md +++ b/docs/user-guide/kubectl/kubectl_scale.md @@ -81,6 +81,9 @@ $ kubectl scale --current-replicas=2 --replicas=3 replicationcontrollers foo ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.037506001 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.956739933 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_scale.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_stop.md b/docs/user-guide/kubectl/kubectl_stop.md index b10c327631f..dccacdc90d9 100644 --- a/docs/user-guide/kubectl/kubectl_stop.md +++ b/docs/user-guide/kubectl/kubectl_stop.md @@ -88,6 +88,9 @@ $ kubectl stop -f path/to/resources ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.038086735 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.957441942 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_stop.md?pixel)]() + diff --git a/docs/user-guide/kubectl/kubectl_version.md b/docs/user-guide/kubectl/kubectl_version.md index af94d5d9509..76d7a0b91e3 100644 --- a/docs/user-guide/kubectl/kubectl_version.md +++ b/docs/user-guide/kubectl/kubectl_version.md @@ -64,6 +64,9 @@ kubectl version ### SEE ALSO * [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager -###### Auto generated by spf13/cobra at 2015-07-13 17:48:54.039889101 +0000 UTC +###### Auto generated by spf13/cobra at 2015-07-14 00:11:42.959846454 +0000 UTC + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_version.md?pixel)]() + diff --git a/docs/user-guide/managing-deployments.md b/docs/user-guide/managing-deployments.md index 655a4342b14..79e6d03a93f 100644 --- a/docs/user-guide/managing-deployments.md +++ b/docs/user-guide/managing-deployments.md @@ -232,7 +232,7 @@ my-nginx-o0ef1 1/1 Running 0 1h At some point, you’ll eventually need to update your deployed application, typically by specifying a new image or image tag, as in the canary deployment scenario above. `kubectl` supports several update operations, each of which is applicable to different scenarios. -To update a service without an outage, `kubectl` supports what is called [“rolling update”](../../docs/user-guide/kubectl/kubectl_rolling-update.md), which updates one pod at a time, rather than taking down the entire service at the same time. +To update a service without an outage, `kubectl` supports what is called [“rolling update”](kubectl/kubectl_rolling-update.md), which updates one pod at a time, rather than taking down the entire service at the same time. Let’s say you were running version 1.7.9 of nginx: ```yaml @@ -389,4 +389,6 @@ replicationcontrollers/my-nginx-v4 ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/managing-deployments.md?pixel)]() + diff --git a/docs/user-guide/prereqs.md b/docs/user-guide/prereqs.md index 36a978bb610..2e4d2023108 100644 --- a/docs/user-guide/prereqs.md +++ b/docs/user-guide/prereqs.md @@ -14,9 +14,11 @@ certainly want the docs that go with that version. # Kubernetes User Guide: Managing Applications: Prerequisites -To deploy and manage applications on Kubernetes, you’ll use the Kubernetes command-line tool, [kubectl](../../docs/user-guide/kubectl/kubectl.md). It can be found in the release tar bundle, or can be built from source from github. Ensure that it is executable and in your path. +To deploy and manage applications on Kubernetes, you’ll use the Kubernetes command-line tool, [kubectl](kubectl/kubectl.md). It can be found in the release tar bundle, or can be built from source from github. Ensure that it is executable and in your path. In order for kubectl to find and access the Kubernetes cluster, it needs a [kubeconfig file](../../docs/kubeconfig-file.md), which is created automatically when creating a cluster using kube-up.sh (see the [getting started guides](../../docs/getting-started-guides/) for more about creating clusters). If you need access to a cluster you didn’t create, see the [Sharing Cluster Access document](../../docs/sharing-clusters.md). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/prereqs.md?pixel)]() + diff --git a/docs/user-guide/production-pods.md b/docs/user-guide/production-pods.md index b85b4a1fc78..75cf68d6b6b 100644 --- a/docs/user-guide/production-pods.md +++ b/docs/user-guide/production-pods.md @@ -161,4 +161,6 @@ spec: ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/production-pods.md?pixel)]() + diff --git a/docs/user-guide/quick-start.md b/docs/user-guide/quick-start.md index e5b53cfff72..9cb19be4d8a 100644 --- a/docs/user-guide/quick-start.md +++ b/docs/user-guide/quick-start.md @@ -20,7 +20,7 @@ This guide will help you get oriented to Kubernetes and running your first conta Once your application is packaged into a container and pushed to an image registry, you’re ready to deploy it to Kubernetes. -For example, [nginx](http://wiki.nginx.org/Main) is a popular HTTP server, with a [pre-built container on Docker hub](https://registry.hub.docker.com/_/nginx/). The [`kubectl run`](../../docs/user-guide/kubectl/kubectl_run.md) command below will create two nginx replicas, listening on port 80. +For example, [nginx](http://wiki.nginx.org/Main) is a popular HTTP server, with a [pre-built container on Docker hub](https://registry.hub.docker.com/_/nginx/). The [`kubectl run`](kubectl/kubectl_run.md) command below will create two nginx replicas, listening on port 80. ```bash $ kubectl run my-nginx --image=nginx --replicas=2 --port=80 @@ -67,4 +67,6 @@ services/my-nginx ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/quick-start.md?pixel)]() + diff --git a/docs/versioning.md b/docs/versioning.md index e7234f72e3a..551606d7e77 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -59,4 +59,6 @@ It may seem a bit strange to complete the v2 API before v2.0 is released, but *a There is a separate question of how to track the capabilities of a kubelet to facilitate rolling upgrades. That is not addressed here. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/versioning.md?pixel)]() + diff --git a/docs/volumes.md b/docs/volumes.md index 4013a5783b0..9fbd940f350 100644 --- a/docs/volumes.md +++ b/docs/volumes.md @@ -375,4 +375,6 @@ specification, and to select the type of media to use, for clusters that have several media types. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/volumes.md?pixel)]() + diff --git a/docs/working_with_resources.md b/docs/working_with_resources.md index 227adaa53ba..81aeb26407e 100644 --- a/docs/working_with_resources.md +++ b/docs/working_with_resources.md @@ -71,5 +71,6 @@ Once there: - You should see a list of all possible resource fields, starting with `v1.pods {...}` - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/working_with_resources.md?pixel)]() + diff --git a/examples/README.md b/examples/README.md index 0d67871ef57..d326d876607 100644 --- a/examples/README.md +++ b/examples/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Kubernetes Examples: releases.k8s.io/HEAD @@ -17,4 +31,6 @@ This directory contains a number of different examples of how to run applications with Kubernetes. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/README.md?pixel)]() + diff --git a/examples/aws_ebs/README.md b/examples/aws_ebs/README.md index 35cb0f9778f..f93a83bb64c 100644 --- a/examples/aws_ebs/README.md +++ b/examples/aws_ebs/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + This is a simple web server pod which serves HTML from an AWS EBS volume. @@ -17,4 +31,7 @@ You should now be able to query your web server: $ Hello World ```` + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/aws_ebs/README.md?pixel)]() + diff --git a/examples/blog-logging/diagrams/README.md b/examples/blog-logging/diagrams/README.md index 5b6987b862d..d929313a3b4 100644 --- a/examples/blog-logging/diagrams/README.md +++ b/examples/blog-logging/diagrams/README.md @@ -1,4 +1,20 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Diagrams for Cloud Logging Blog Article + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/blog-logging/diagrams/README.md?pixel)]() + diff --git a/examples/cassandra/README.md b/examples/cassandra/README.md index 8f32bf3dd64..2e75b9ed5ea 100644 --- a/examples/cassandra/README.md +++ b/examples/cassandra/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Cloud Native Deployments of Cassandra using Kubernetes The following document describes the development of a _cloud native_ [Cassandra](http://cassandra.apache.org/) deployment on Kubernetes. When we say _cloud native_ we mean an application which understands that it is running within a cluster manager, and uses this cluster management infrastructure to help implement the application. In particular, in this instance, a custom Cassandra ```SeedProvider``` is used to enable Cassandra to dynamically discover new Cassandra nodes as they join the cluster. @@ -265,6 +279,9 @@ kubectl scale rc cassandra --replicas=4 ### Seed Provider Source -See [here](./java/src/io/k8s/cassandra/KubernetesSeedProvider.java). +See [here](java/src/io/k8s/cassandra/KubernetesSeedProvider.java). + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/cassandra/README.md?pixel)]() + diff --git a/examples/celery-rabbitmq/README.md b/examples/celery-rabbitmq/README.md index 6997a215f7a..41a1f19d517 100644 --- a/examples/celery-rabbitmq/README.md +++ b/examples/celery-rabbitmq/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Example: Distributed task queues with Celery, RabbitMQ and Flower ## Introduction @@ -257,5 +271,6 @@ Point your internet browser to the appropriate flower-service address, port 5555 If you click on the tab called "Tasks", you should see an ever-growing list of tasks called "celery_conf.add" which the run\_tasks.py script is dispatching. - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/celery-rabbitmq/README.md?pixel)]() + diff --git a/examples/cluster-dns/README.md b/examples/cluster-dns/README.md index d0c6fb57070..4fb37cead8a 100644 --- a/examples/cluster-dns/README.md +++ b/examples/cluster-dns/README.md @@ -1,10 +1,24 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Kubernetes DNS example This is a toy example demonstrating how to use kubernetes DNS. ### Step Zero: Prerequisites -This example assumes that you have forked the repository and [turned up a Kubernetes cluster](../../docs/getting-started-guides). Make sure DNS is enabled in your setup, see [DNS doc](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/cluster/addons/dns). +This example assumes that you have forked the repository and [turned up a Kubernetes cluster](../../docs/getting-started-guides/). Make sure DNS is enabled in your setup, see [DNS doc](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/cluster/addons/dns). ```shell $ cd kubernetes @@ -121,7 +135,7 @@ $ kubectl logs dns-frontend 2015-05-07T20:13:54.147738295Z Hello World! ``` -Please refer to the [source code](./images/frontend/client.py) about the log. First line prints out the ip address associated with the service in dev namespace; remaining lines print out our request and server response. +Please refer to the [source code](images/frontend/client.py) about the log. First line prints out the ip address associated with the service in dev namespace; remaining lines print out our request and server response. If we switch to prod namespace with the same pod config, we'll see the same result, i.e. dns will resolve across namespace. @@ -176,4 +190,6 @@ kubectl logs dns-frontend ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/cluster-dns/README.md?pixel)]() + diff --git a/examples/downward-api/README.md b/examples/downward-api/README.md index e189d60be6c..e886bf41b4f 100644 --- a/examples/downward-api/README.md +++ b/examples/downward-api/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Downward API example Following this example, you will create a pod with a containers that consumes the pod's name and @@ -7,7 +21,7 @@ namespace using the [downward API](https://github.com/GoogleCloudPlatform/kubern This example assumes you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` command line tool somewhere in your path. Please see the [getting -started](../../docs/getting-started-guides) for installation instructions for your platform. +started](../../docs/getting-started-guides/) for installation instructions for your platform. ## Step One: Create the pod @@ -33,4 +47,6 @@ $ kubectl logs dapi-test-pod | grep POD_ ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/downward-api/README.md?pixel)]() + diff --git a/examples/elasticsearch/README.md b/examples/elasticsearch/README.md index b7292ca92e8..7b7972b8a6e 100644 --- a/examples/elasticsearch/README.md +++ b/examples/elasticsearch/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Elasticsearch for Kubernetes This directory contains the source for a Docker image that creates an instance @@ -304,4 +318,7 @@ $ curl 104.197.12.157:9200/_nodes?pretty=true | grep name ``` + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/elasticsearch/README.md?pixel)]() + diff --git a/examples/environment-guide/README.md b/examples/environment-guide/README.md index bd796f161c6..49825040d51 100644 --- a/examples/environment-guide/README.md +++ b/examples/environment-guide/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + Environment Guide Example ========================= This example demonstrates running pods, replication controllers, and @@ -7,7 +21,7 @@ environment information about itself, and a backend pod that it has accessed through the service. The goal is to illuminate the environment metadata available to running containers inside the Kubernetes cluster. The documentation for the kubernetes environment -is [here](/docs/container-environment.md). +is [here](../../docs/container-environment.md). ![Diagram](diagram.png) @@ -16,13 +30,13 @@ Prerequisites This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the `kubectl` command line tool somewhere in your path. Please see the [getting -started](/docs/getting-started-guides) for installation instructions +started](../../docs/getting-started-guides/) for installation instructions for your platform. Optional: Build your own containers ----------------------------------- The code for the containers is under -[containers/](containers) +[containers/](containers/) Get everything running ---------------------- @@ -67,8 +81,8 @@ Backend Namespace: default ``` First the frontend pod's information is printed. The pod name and -[namespace](/docs/design/namespaces.md) are retreived from the -[Downward API](/docs/downward_api.md). Next, `USER_VAR` is the name of +[namespace](../../docs/design/namespaces.md) are retreived from the +[Downward API](../../docs/downward_api.md). Next, `USER_VAR` is the name of an environment variable set in the [pod definition](show-rc.yaml). Then, the dynamic kubernetes environment variables are scanned and printed. These are used to find the backend @@ -89,4 +103,6 @@ Cleanup kubectl delete rc,service -l type=backend-type + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/environment-guide/README.md?pixel)]() + diff --git a/examples/environment-guide/containers/README.md b/examples/environment-guide/containers/README.md index 01085e971dd..195c9e43b57 100644 --- a/examples/environment-guide/containers/README.md +++ b/examples/environment-guide/containers/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + Building -------- For each container, the build steps are the same. The examples below @@ -20,4 +34,6 @@ Edit both `show-rc.yaml` and `backend-rc.yaml` and replace the specified `image:` with the one that you built. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/environment-guide/containers/README.md?pixel)]() + diff --git a/examples/explorer/README.md b/examples/explorer/README.md index b55d892b97b..712e2b2db39 100644 --- a/examples/explorer/README.md +++ b/examples/explorer/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ### explorer Explorer is a little container for examining the runtime environment kubernetes produces for your pods. @@ -127,4 +141,6 @@ Error: <*>lookup elasticsearch-logging: no such host ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/explorer/README.md?pixel)]() + diff --git a/examples/glusterfs/README.md b/examples/glusterfs/README.md index a6af9d1cbe6..cd8df4c34bf 100644 --- a/examples/glusterfs/README.md +++ b/examples/glusterfs/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Glusterfs [Glusterfs](http://www.gluster.org) is an open source scale-out filesystem. These examples provide information about how to allow containers use Glusterfs volumes. @@ -83,4 +97,6 @@ $ mount | grep kube_vol You may also run `docker ps` on the host to see the actual container. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/glusterfs/README.md?pixel)]() + diff --git a/examples/guestbook-go/_src/README.md b/examples/guestbook-go/_src/README.md index 236bd82609d..020ecf26dcd 100644 --- a/examples/guestbook-go/_src/README.md +++ b/examples/guestbook-go/_src/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Building and releasing Guestbook Image This process employs building two docker images, one compiles the source and the other hosts the compiled binaries. @@ -34,4 +48,6 @@ Accepts an optional tag (defaults to "latest") ./script/clean.sh + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/guestbook-go/_src/README.md?pixel)]() + diff --git a/examples/guestbook/README.md b/examples/guestbook/README.md index dbd8ba29b98..93ca40b7569 100644 --- a/examples/guestbook/README.md +++ b/examples/guestbook/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Guestbook Example @@ -33,7 +47,7 @@ The web front end interacts with the redis master via javascript redis API calls ### Step Zero: Prerequisites -This example requires a running Kubernetes cluster. See the [Getting Started guides](../../docs/getting-started-guides) for how to get started. As noted above, if you have a Google Container Engine cluster set up, go [here](https://cloud.google.com/container-engine/docs/tutorials/guestbook) instead. +This example requires a running Kubernetes cluster. See the [Getting Started guides](../../docs/getting-started-guides/) for how to get started. As noted above, if you have a Google Container Engine cluster set up, go [here](https://cloud.google.com/container-engine/docs/tutorials/guestbook) instead. ### Step One: Start up the redis master @@ -539,5 +553,7 @@ If you are having trouble bringing up your guestbook app, double check that your Then, see the [troubleshooting documentation](../../docs/troubleshooting.md) for a further list of common issues and how you can diagnose them. -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/guestbook/README.md?pixel)]() + +[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/guestbook/README.md?pixel)]() + diff --git a/examples/hazelcast/README.md b/examples/hazelcast/README.md index da984b0a402..47e17b2cfc4 100644 --- a/examples/hazelcast/README.md +++ b/examples/hazelcast/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Cloud Native Deployments of Hazelcast using Kubernetes The following document describes the development of a _cloud native_ [Hazelcast](http://hazelcast.org/) deployment on Kubernetes. When we say _cloud native_ we mean an application which understands that it is running within a cluster manager, and uses this cluster management infrastructure to help implement the application. In particular, in this instance, a custom Hazelcast ```bootstrapper``` is used to enable Hazelcast to dynamically discover Hazelcast nodes that have already joined the cluster. @@ -206,4 +220,7 @@ kubectl scale rc hazelcast --replicas=4 See [here](https://github.com/pires/hazelcast-kubernetes-bootstrapper/blob/master/src/main/java/com/github/pires/hazelcast/HazelcastDiscoveryController.java) + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/hazelcast/README.md?pixel)]() + diff --git a/examples/iscsi/README.md b/examples/iscsi/README.md index cf049a8e4fb..5ea813288e4 100644 --- a/examples/iscsi/README.md +++ b/examples/iscsi/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Step 1. Setting up iSCSI target and iSCSI initiator **Setup A.** On Fedora 21 nodes @@ -67,4 +81,6 @@ Run *docker inspect* and I found the Containers mounted the host directory into ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/iscsi/README.md?pixel)]() + diff --git a/examples/k8petstore/README.md b/examples/k8petstore/README.md index f11ddeafb45..c0972bb47ca 100644 --- a/examples/k8petstore/README.md +++ b/examples/k8petstore/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Welcome to k8PetStore This is a follow up to the [Guestbook Example](../guestbook/README.md)'s [Go implementation](../guestbook-go/). @@ -109,4 +123,6 @@ For questions on running this app, you can ask on the google containers group (f For questions about bigpetstore, and how the data is generated, ask on the apache bigtop mailing list. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/k8petstore/README.md?pixel)]() + diff --git a/examples/k8petstore/bps-data-generator/README.md b/examples/k8petstore/bps-data-generator/README.md index 21b1319e639..2b407beda08 100644 --- a/examples/k8petstore/bps-data-generator/README.md +++ b/examples/k8petstore/bps-data-generator/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # How to generate the bps-data-generator container # This container is maintained as part of the apache bigtop project. @@ -15,4 +29,6 @@ then, cd to bigtop-bigpetstore/bigpetstore-transaction-queue, and run the docker `Docker build -t -i jayunit100/bps-transaction-queue`. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/k8petstore/bps-data-generator/README.md?pixel)]() + diff --git a/examples/kubectl-container/README.md b/examples/kubectl-container/README.md index 1d37732af6a..15737b397c3 100644 --- a/examples/kubectl-container/README.md +++ b/examples/kubectl-container/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + This directory contains a Dockerfile and Makefile for packaging up kubectl into a container. @@ -18,4 +32,6 @@ 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](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/kubectl-container/README.md?pixel)]() + diff --git a/examples/kubernetes-namespaces/README.md b/examples/kubernetes-namespaces/README.md index 45aeb27a77e..d0ba4172ebc 100644 --- a/examples/kubernetes-namespaces/README.md +++ b/examples/kubernetes-namespaces/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Kubernetes Namespaces Kubernetes _[namespaces](../../docs/namespaces.md)_ help different projects, teams, or customers to share a Kubernetes cluster. @@ -15,7 +29,7 @@ This example demonstrates how to use Kubernetes namespaces to subdivide your clu This example assumes the following: -1. You have an [existing Kubernetes cluster](../../docs/getting-started-guides). +1. You have an [existing Kubernetes cluster](../../docs/getting-started-guides/). 2. You have a basic understanding of Kubernetes _[pods](../../docs/pods.md)_, _[services](../../docs/services.md)_, and _[replication controllers](../../docs/replication-controller.md)_. ### Step One: Understand the default namespace @@ -242,4 +256,6 @@ As the policy support in Kubernetes evolves, we will extend this scenario to sho authorization rules for each namespace. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/kubernetes-namespaces/README.md?pixel)]() + diff --git a/examples/limitrange/README.md b/examples/limitrange/README.md index 869d00effe5..75110d6561d 100644 --- a/examples/limitrange/README.md +++ b/examples/limitrange/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + Limit Range ======================================== By default, pods run with unbounded CPU and memory limits. This means that any pod in the @@ -29,7 +43,7 @@ For a detailed description of the Kubernetes resource model, see [Resources](htt Step 0: Prerequisites ----------------------------------------- -This example requires a running Kubernetes cluster. See the [Getting Started guides](../../docs/getting-started-guides) for how to get started. +This example requires a running Kubernetes cluster. See the [Getting Started guides](../../docs/getting-started-guides/) for how to get started. Change to the `/examples/limitrange` directory if you're not already there. @@ -163,4 +177,6 @@ the Kubernetes system is able to apply default resource limits if desired in ord amount of resource a pod consumes on a node. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/limitrange/README.md?pixel)]() + diff --git a/examples/liveness/README.md b/examples/liveness/README.md index 96d529e4f5b..da379fdd866 100644 --- a/examples/liveness/README.md +++ b/examples/liveness/README.md @@ -1,7 +1,21 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Overview This example shows two types of pod health checks: HTTP checks and container execution checks. -The [exec-liveness.yaml](./exec-liveness.yaml) demonstrates the container execution check. +The [exec-liveness.yaml](exec-liveness.yaml) demonstrates the container execution check. ``` livenessProbe: exec: @@ -67,4 +81,8 @@ Sat, 27 Jun 2015 13:44:44 +0200 Sat, 27 Jun 2015 13:44:44 +0200 1 {kube Sat, 27 Jun 2015 13:44:44 +0200 Sat, 27 Jun 2015 13:44:44 +0200 1 {kubelet kubernetes-minion-6fbi} spec.containers{liveness} created Created with docker id ed6bb004ee10 Sat, 27 Jun 2015 13:44:44 +0200 Sat, 27 Jun 2015 13:44:44 +0200 1 {kubelet kubernetes-minion-6fbi} spec.containers{liveness} started Started with docker id ed6bb004ee10 ``` + + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/liveness/README.md?pixel)]() + diff --git a/examples/logging-demo/README.md b/examples/logging-demo/README.md index 7c6abffe925..ce0cbd64910 100644 --- a/examples/logging-demo/README.md +++ b/examples/logging-demo/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Elasticsearch/Kibana Logging Demonstration This directory contains two [pod](../../docs/pods.md) specifications which can be used as synthetic logging sources. The pod specification in [synthetic_0_25lps.yaml](synthetic_0_25lps.yaml) @@ -7,10 +21,12 @@ describes a pod that just emits 10 log lines per second. To observe the ingested log lines when using Google Cloud Logging please see the getting started instructions -at [Cluster Level Logging to Google Cloud Logging](/docs/getting-started-guides/logging.md). +at [Cluster Level Logging to Google Cloud Logging](../../docs/getting-started-guides/logging.md). To observe the ingested log lines when using Elasticsearch and Kibana please see the getting started instructions -at [Cluster Level Logging with Elasticsearch and Kibana](/docs/getting-started-guides/logging-elasticsearch.md). +at [Cluster Level Logging with Elasticsearch and Kibana](../../docs/getting-started-guides/logging-elasticsearch.md). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/logging-demo/README.md?pixel)]() + diff --git a/examples/meteor/README.md b/examples/meteor/README.md index a0d1d650cb8..644d5b674a5 100644 --- a/examples/meteor/README.md +++ b/examples/meteor/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + Meteor on Kuberenetes ===================== @@ -11,7 +25,7 @@ Meteor uses MongoDB, and we will use the `GCEPersistentDisk` type of volume for persistent storage. Therefore, this example is only applicable to [Google Compute Engine](https://cloud.google.com/compute/). Take a look at the -[volumes documentation](/docs/volumes.md) for other options. +[volumes documentation](../../docs/volumes.md) for other options. First, if you have not already done so: @@ -104,7 +118,7 @@ and make sure the `image:` points to the container you just pushed to the Docker Hub or GCR. We will need to provide MongoDB a persistent Kuberetes volume to -store its data. See the [volumes documentation](/docs/volumes.md) for +store its data. See the [volumes documentation](../../docs/volumes.md) for options. We're going to use Google Compute Engine persistent disks. Create the MongoDB disk by running: ``` @@ -155,7 +169,7 @@ Here we can see the MongoDB host and port information being passed into the Meteor app. The `MONGO_SERVICE...` environment variables are set by Kubernetes, and point to the service named `mongo` specified in [`mongo-service.json`](mongo-service.json). See the [environment -documentation](/docs/container-environment.md) for more details. +documentation](../../docs/container-environment.md) for more details. As you may know, Meteor uses long lasting connections, and requires _sticky sessions_. With Kubernetes you can scale out your app easily @@ -163,7 +177,7 @@ with session affinity. The [`meteor-service.json`](meteor-service.json) file contains `"sessionAffinity": "ClientIP"`, which provides this for us. See the [service -documentation](/docs/services.md#virtual-ips-and-service-proxies) for +documentation](../../docs/services.md#virtual-ips-and-service-proxies) for more information. As mentioned above, the mongo container uses a volume which is mapped @@ -192,4 +206,6 @@ container section: ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/meteor/README.md?pixel)]() + diff --git a/examples/meteor/dockerbase/README.md b/examples/meteor/dockerbase/README.md index a3a9e09084b..4d7e4f9364b 100644 --- a/examples/meteor/dockerbase/README.md +++ b/examples/meteor/dockerbase/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + Building the meteor-kubernetes base image ----------------------------------------- @@ -9,4 +23,6 @@ To build and push the base meteor-kubernetes image: docker push chees/meteor-kubernetes + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/meteor/dockerbase/README.md?pixel)]() + diff --git a/examples/mysql-wordpress-pd/README.md b/examples/mysql-wordpress-pd/README.md index 7e6d95aed08..ffeff2186cd 100644 --- a/examples/mysql-wordpress-pd/README.md +++ b/examples/mysql-wordpress-pd/README.md @@ -1,6 +1,20 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Persistent Installation of MySQL and WordPress on Kubernetes -This example describes how to run a persistent installation of [Wordpress](https://wordpress.org/) using the [volumes](/docs/volumes.md) feature of Kubernetes, and [Google Compute Engine](https://cloud.google.com/compute/docs/disks) [persistent disks](/docs/volumes.md#gcepersistentdisk). +This example describes how to run a persistent installation of [Wordpress](https://wordpress.org/) using the [volumes](../../docs/volumes.md) feature of Kubernetes, and [Google Compute Engine](https://cloud.google.com/compute/docs/disks) [persistent disks](../../docs/volumes.md#gcepersistentdisk). We'll use the [mysql](https://registry.hub.docker.com/_/mysql/) and [wordpress](https://registry.hub.docker.com/_/wordpress/) official [Docker](https://www.docker.com/) images for this installation. (The wordpress image includes an Apache server). @@ -10,7 +24,7 @@ This example demonstrates several useful things, including: how to set up and us ## Get started on Google Compute Engine (GCE) -Because we're using the `GCEPersistentDisk` type of volume for persistent storage, this example is only applicable to [Google Compute Engine](https://cloud.google.com/compute/). Take a look at the [volumes documentation](/docs/volumes.md) for other options. +Because we're using the `GCEPersistentDisk` type of volume for persistent storage, this example is only applicable to [Google Compute Engine](https://cloud.google.com/compute/). Take a look at the [volumes documentation](../../docs/volumes.md) for other options. First, if you have not already done so: @@ -36,7 +50,7 @@ Please see the [GCE getting started guide](../../docs/getting-started-guides/gce For this WordPress installation, we're going to configure our Kubernetes [pods](../../docs/pods.md) to use [persistent disks](https://cloud.google.com/compute/docs/disks). This means that we can preserve installation state across pod shutdown and re-startup. -You will need to create the disks in the same [GCE zone](https://cloud.google.com/compute/docs/zones) as the Kubernetes cluster. The default setup script will create the cluster in the `us-central1-b` zone, as seen in the [config-default.sh](/cluster/gce/config-default.sh) file. Replace `$ZONE` below with the appropriate zone. +You will need to create the disks in the same [GCE zone](https://cloud.google.com/compute/docs/zones) as the Kubernetes cluster. The default setup script will create the cluster in the `us-central1-b` zone, as seen in the [config-default.sh](../../cluster/gce/config-default.sh) file. Replace `$ZONE` below with the appropriate zone. We will create two disks: one for the mysql pod, and one for the wordpress pod. In this example, we create 20GB disks, which will be sufficient for this demo. Feel free to change the size to align with your needs, as wordpress requirements can vary. Also, keep in mind that [disk performance scales with size](https://cloud.google.com/compute/docs/disks/#comparison_of_disk_types). @@ -300,4 +314,6 @@ $ cluster/kube-down.sh ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/mysql-wordpress-pd/README.md?pixel)]() + diff --git a/examples/nfs/README.md b/examples/nfs/README.md index d1144442967..4a705a2fdb6 100644 --- a/examples/nfs/README.md +++ b/examples/nfs/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Example of NFS volume See [nfs-web-pod.yaml](nfs-web-pod.yaml) for a quick example, how to use NFS volume @@ -50,4 +64,6 @@ Now the pod serves `index.html` from the NFS server: Hello World! + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/nfs/README.md?pixel)]() + diff --git a/examples/nfs/exporter/README.md b/examples/nfs/exporter/README.md index f8564d9b724..f3a42c86f32 100644 --- a/examples/nfs/exporter/README.md +++ b/examples/nfs/exporter/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # NFS-exporter container Inspired by https://github.com/cpuguy83/docker-nfs-server. Rewritten for @@ -10,4 +24,6 @@ Usage:: docker run -d --name nfs --privileged jsafrane/nfsexporter /path/to/share /path/to/share2 ... + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/nfs/exporter/README.md?pixel)]() + diff --git a/examples/nfs/nfs-data/README.md b/examples/nfs/nfs-data/README.md index f7606ace72d..2596612ef9a 100644 --- a/examples/nfs/nfs-data/README.md +++ b/examples/nfs/nfs-data/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # NFS-exporter container with a file This container exports /mnt/data with index.html in it via NFSv4. Based on @@ -6,4 +20,7 @@ This container exports /mnt/data with index.html in it via NFSv4. Based on Available in dockerhub as [jsafrane/nfs-data](https://registry.hub.docker.com/u/jsafrane/nfs-data/). + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/nfs/nfs-data/README.md?pixel)]() + diff --git a/examples/node-selection/README.md b/examples/node-selection/README.md index 03871e96e38..48ea49e5cc8 100644 --- a/examples/node-selection/README.md +++ b/examples/node-selection/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Node selection example This example shows how to assign a pod to a specific node or to one of a set of nodes using node labels and the nodeSelector field in a pod specification. Generally this is unnecessary, as the scheduler will take care of things for you, but you may want to do so in certain circumstances like to ensure that your pod ends up on a machine with an SSD attached to it. @@ -14,7 +28,7 @@ Then, to add a label to the node you've chosen, run `kubectl label nodes [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/node-selection/README.md?pixel)]() + diff --git a/examples/openshift-origin/README.md b/examples/openshift-origin/README.md index bc4990ca220..8c9ca8c58d0 100644 --- a/examples/openshift-origin/README.md +++ b/examples/openshift-origin/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## OpenShift Origin example This example shows how to run OpenShift Origin as a pod on an existing Kubernetes cluster. @@ -155,4 +169,6 @@ $ osc --help ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/openshift-origin/README.md?pixel)]() + diff --git a/examples/persistent-volumes/README.md b/examples/persistent-volumes/README.md index 4afa91574b2..a554fcc1bd1 100644 --- a/examples/persistent-volumes/README.md +++ b/examples/persistent-volumes/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # How To Use Persistent Volumes The purpose of this guide is to help you become familiar with Kubernetes Persistent Volumes. By the end of the guide, we'll have @@ -99,4 +113,6 @@ Hopefully this simple guide is enough to get you started with PersistentVolumes. Enjoy! + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/persistent-volumes/README.md?pixel)]() + diff --git a/examples/phabricator/README.md b/examples/phabricator/README.md index 7d8732b904c..2b7cd45bbef 100644 --- a/examples/phabricator/README.md +++ b/examples/phabricator/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Phabricator example This example shows how to build a simple multi-tier web application using Kubernetes and Docker. @@ -6,7 +20,7 @@ The example combines a web frontend and an external service that provides MySQL ### Step Zero: Prerequisites -This example assumes that you have a basic understanding of kubernetes [services](../../docs/services.md) and that you have forked the repository and [turned up a Kubernetes cluster](../../docs/getting-started-guides): +This example assumes that you have a basic understanding of kubernetes [services](../../docs/services.md) and that you have forked the repository and [turned up a Kubernetes cluster](../../docs/getting-started-guides/): ```shell $ cd kubernetes @@ -223,4 +237,6 @@ $ cluster/kube-down.sh ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/phabricator/README.md?pixel)]() + diff --git a/examples/rbd/README.md b/examples/rbd/README.md index a71f971f18b..7e0492513ae 100644 --- a/examples/rbd/README.md +++ b/examples/rbd/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # How to Use it? Install Ceph on the Kubernetes host. For example, on Fedora 21 @@ -45,4 +59,7 @@ On the Kubernetes host, I got these in mount output If you ssh to that machine, you can run `docker ps` to see the actual pod and `docker inspect` to see the volumes used by the container. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/rbd/README.md?pixel)]() + diff --git a/examples/redis/README.md b/examples/redis/README.md index ad98566a13c..195d49e9871 100644 --- a/examples/redis/README.md +++ b/examples/redis/README.md @@ -1,9 +1,23 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Reliable, Scalable Redis on Kubernetes The following document describes the deployment of a reliable, multi-node Redis on Kubernetes. It deploys a master with replicated slaves, as well as replicated redis sentinels which are use for health checking and failover. ### Prerequisites -This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` command line tool somewhere in your path. Please see the [getting started](../../docs/getting-started-guides) for installation instructions for your platform. +This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` command line tool somewhere in your path. Please see the [getting started](../../docs/getting-started-guides/) for installation instructions for your platform. ### A note for the impatient This is a somewhat long tutorial. If you want to jump straight to the "do it now" commands, please see the [tl; dr](#tl-dr) at the end. @@ -112,6 +126,6 @@ kubectl delete pods redis-master ``` - - + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/redis/README.md?pixel)]() + diff --git a/examples/resourcequota/README.md b/examples/resourcequota/README.md index 27a8da1bdcb..c611085332b 100644 --- a/examples/resourcequota/README.md +++ b/examples/resourcequota/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + Resource Quota ======================================== This example demonstrates how resource quota and limits can be applied to a Kubernetes namespace. @@ -151,4 +165,7 @@ by the namespace quota. Any action that consumes those resources can be tweaked, or can pick up namespace level defaults to meet your end goal. + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/resourcequota/README.md?pixel)]() + diff --git a/examples/rethinkdb/README.md b/examples/rethinkdb/README.md index 5035cfa8021..e873f2687ef 100644 --- a/examples/rethinkdb/README.md +++ b/examples/rethinkdb/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + RethinkDB Cluster on Kubernetes ============================== @@ -125,4 +139,6 @@ the generated pods which is using `nodeSelector` to force k8s to schedule contai * see [antmanler/rethinkdb-k8s](https://github.com/antmanler/rethinkdb-k8s) for detail + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/rethinkdb/README.md?pixel)]() + diff --git a/examples/secrets/README.md b/examples/secrets/README.md index 4851c99551b..27046286377 100644 --- a/examples/secrets/README.md +++ b/examples/secrets/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Secrets example Following this example, you will create a secret and a pod that consumes that secret in a volume. @@ -7,7 +21,7 @@ You can learn more about secrets [Here](https://github.com/GoogleCloudPlatform/k This example assumes you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` command line tool somewhere in your path. Please see the [getting -started](../../docs/getting-started-guides) for installation instructions for your platform. +started](../../docs/getting-started-guides/) for installation instructions for your platform. ## Step One: Create the secret @@ -59,4 +73,6 @@ $ kubectl logs secret-test-pod ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/secrets/README.md?pixel)]() + diff --git a/examples/simple-nginx.md b/examples/simple-nginx.md index 10f25661605..fbdca24afc2 100644 --- a/examples/simple-nginx.md +++ b/examples/simple-nginx.md @@ -22,7 +22,7 @@ to Kubernetes and running your first containers on the cluster. From this point onwards, it is assumed that `kubectl` is on your path from one of the getting started guides. -The [`kubectl run`](../../docs/user-guide/kubectl/kubectl_run.md) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](../docs/pods.md) listening on port 80. It will also create a [replication controller](../docs/replication-controller.md) named `my-nginx` to ensure that there are always two pods running. +The [`kubectl run`](../docs/user-guide/kubectl/kubectl_run.md) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](../docs/pods.md) listening on port 80. It will also create a [replication controller](../docs/replication-controller.md) named `my-nginx` to ensure that there are always two pods running. ```bash kubectl run my-nginx --image=nginx --replicas=2 --port=80 diff --git a/examples/simple-yaml.md b/examples/simple-yaml.md index 602007ea701..ca7acd37964 100644 --- a/examples/simple-yaml.md +++ b/examples/simple-yaml.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + ## Getting started with config files. In addition to the imperative style commands described [elsewhere](simple-nginx.md), Kubernetes @@ -81,4 +95,6 @@ kubectl delete rc nginx ``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/simple-yaml.md?pixel)]() + diff --git a/examples/storm/README.md b/examples/storm/README.md index b2d5eb49c87..e6e06b877c4 100644 --- a/examples/storm/README.md +++ b/examples/storm/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Storm example Following this example, you will create a functional [Apache @@ -22,7 +36,7 @@ Source is freely available at: This example assumes you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` command line tool somewhere in your path. Please see the [getting -started](../../docs/getting-started-guides) for installation +started](../../docs/getting-started-guides/) for installation instructions for your platform. ## Step One: Start your ZooKeeper service @@ -168,4 +182,6 @@ Make sure the Nimbus Pod is running. ```kubectl create -f storm-worker-controller.json``` + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storm/README.md?pixel)]() + diff --git a/examples/update-demo/README.md b/examples/update-demo/README.md index bcbe7c3200e..aa38cb26e33 100644 --- a/examples/update-demo/README.md +++ b/examples/update-demo/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/update-demo/README.md?pixel)]() + diff --git a/examples/walkthrough/README.md b/examples/walkthrough/README.md index c18e6b24601..48766a369a0 100644 --- a/examples/walkthrough/README.md +++ b/examples/walkthrough/README.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Kubernetes 101 - Walkthrough ## Pods @@ -108,8 +122,10 @@ Finally, we have also introduced an environment variable to the ```git-monitor`` ### What's next? -Continue on to [Kubernetes 201](../walkthrough/k8s201.md) or +Continue on to [Kubernetes 201](k8s201.md) or for a complete application see the [guestbook example](../guestbook/README.md) + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/walkthrough/README.md?pixel)]() + diff --git a/examples/walkthrough/k8s201.md b/examples/walkthrough/k8s201.md index 5253f89f186..651cea33502 100644 --- a/examples/walkthrough/k8s201.md +++ b/examples/walkthrough/k8s201.md @@ -1,3 +1,17 @@ + + + + +

*** PLEASE NOTE: This document applies to the HEAD of the source +tree only. If you are using a released version of Kubernetes, you almost +certainly want the docs that go with that version.

+ +Documentation for specific releases can be found at +[releases.k8s.io](http://releases.k8s.io). + + + + # Kubernetes 201 - Labels, Replication Controllers, Services and Health Checking ### Overview @@ -148,7 +162,9 @@ spec: ``` ### What's next? -For a complete application see the [guestbook example](../guestbook). +For a complete application see the [guestbook example](../guestbook/). + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/walkthrough/k8s201.md?pixel)]() +