s|github.com/GoogleCloudPlatform/kubernetes|github.com/kubernetes/kubernetes|

Author: eparis

CHANGELOG.md

@@ -1,4 +1,4 @@
-Please see the [Releases Page](https://github.com/GoogleCloudPlatform/kubernetes/releases)
+Please see the [Releases Page](https://github.com/kubernetes/kubernetes/releases)
 
 
 [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/CHANGELOG.md?pixel)]()

cluster/addons/fluentd-elasticsearch/fluentd-es-image/README.md

@@ -2,7 +2,7 @@
 This directory contains the source files needed to make a Docker image
 that collects Docker container log files using [Fluentd](http://www.fluentd.org/)
 and sends them to an instance of [Elasticsearch](http://www.elasticsearch.org/).
-This image is designed to be used as part of the [Kubernetes](https://github.com/GoogleCloudPlatform/kubernetes)
+This image is designed to be used as part of the [Kubernetes](https://github.com/kubernetes/kubernetes)
 cluster bring up process. The image resides at DockerHub under the name
 [kubernetes/fluentd-eslasticsearch](https://registry.hub.docker.com/u/kubernetes/fluentd-elasticsearch/).
 

cluster/addons/fluentd-gcp/fluentd-gcp-image/README.md

@@ -2,7 +2,7 @@
 This directory contains the source files needed to make a Docker image
 that collects Docker container log files using [Fluentd](http://www.fluentd.org/)
 and sends them to GCP.
-This image is designed to be used as part of the [Kubernetes](https://github.com/GoogleCloudPlatform/kubernetes)
+This image is designed to be used as part of the [Kubernetes](https://github.com/kubernetes/kubernetes)
 cluster bring up process. The image resides at DockerHub under the name
 [kubernetes/fluentd-gcp](https://registry.hub.docker.com/u/kubernetes/fluentd-gcp/).
 

docs/admin/authentication.md

@@ -88,8 +88,8 @@ option to the apiserver during startup. The plugin is implemented in
 For details on how to use keystone to manage projects and users, refer to the
 [Keystone documentation](http://docs.openstack.org/developer/keystone/). Please note that
 this plugin is still experimental which means it is subject to changes.
-Please refer to the [discussion](https://github.com/GoogleCloudPlatform/kubernetes/pull/11798#issuecomment-129655212)
-and the [blueprint](https://github.com/GoogleCloudPlatform/kubernetes/issues/11626) for more details
+Please refer to the [discussion](https://github.com/kubernetes/kubernetes/pull/11798#issuecomment-129655212)
+and the [blueprint](https://github.com/kubernetes/kubernetes/issues/11626) for more details
 
 ## Plugin Development
 

docs/admin/node.md

@@ -253,7 +253,7 @@ on each kubelet where you want to reserve resources.
 
 Node is a top-level resource in the kubernetes REST API. More details about the
 API object can be found at: [Node API
-object](https://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_node).
+object](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_node).
 
 
 <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

docs/design/architecture.md

@@ -51,7 +51,7 @@ The `kubelet` manages [pods](../user-guide/pods.md) and their containers, their
 
 ### `kube-proxy`
 
-Each node also runs a simple network proxy and load balancer (see the [services FAQ](https://github.com/GoogleCloudPlatform/kubernetes/wiki/Services-FAQ) for more details).  This reflects `services` (see [the services doc](../user-guide/services.md) for more details) as defined in the Kubernetes API on each node and can do simple TCP and UDP stream forwarding (round robin) across a set of backends.
+Each node also runs a simple network proxy and load balancer (see the [services FAQ](https://github.com/kubernetes/kubernetes/wiki/Services-FAQ) for more details).  This reflects `services` (see [the services doc](../user-guide/services.md) for more details) as defined in the Kubernetes API on each node and can do simple TCP and UDP stream forwarding (round robin) across a set of backends.
 
 Service endpoints are currently found via [DNS](../admin/dns.md) or through environment variables (both [Docker-links-compatible](https://docs.docker.com/userguide/dockerlinks/) and Kubernetes `{FOO}_SERVICE_HOST` and `{FOO}_SERVICE_PORT` variables are supported).  These variables resolve to ports managed by the service proxy.
 

docs/devel/cherry-picks.md

@@ -62,7 +62,7 @@ conflict***.
 
 Now that we've structured cherry picks as PRs, searching for all cherry-picks
 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)
+[this query is all of the v0.21.x cherry-picks](https://github.com/kubernetes/kubernetes/pulls?utf8=%E2%9C%93&q=is%3Apr+%22automated+cherry+pick%22+base%3Arelease-0.21)
 
 
 <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

docs/devel/cli-roadmap.md

@@ -34,9 +34,9 @@ Documentation for other releases can be found at
 # Kubernetes CLI/Configuration Roadmap
 
 See github issues with the following labels:
-* [area/app-config-deployment](https://github.com/GoogleCloudPlatform/kubernetes/labels/area/app-config-deployment)
-* [component/CLI](https://github.com/GoogleCloudPlatform/kubernetes/labels/component/CLI)
-* [component/client](https://github.com/GoogleCloudPlatform/kubernetes/labels/component/client)
+* [area/app-config-deployment](https://github.com/kubernetes/kubernetes/labels/area/app-config-deployment)
+* [component/CLI](https://github.com/kubernetes/kubernetes/labels/component/CLI)
+* [component/client](https://github.com/kubernetes/kubernetes/labels/component/client)
 
 
 <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

docs/devel/flaky-tests.md

@@ -64,7 +64,7 @@ spec:
         - name: TEST_PACKAGE
           value: pkg/tools
         - name: REPO_SPEC
-          value: https://github.com/GoogleCloudPlatform/kubernetes
+          value: https://github.com/kubernetes/kubernetes
 ```
 
 Note that we omit the labels and the selector fields of the replication controller, because they will be populated from the labels field of the pod template by default.

docs/devel/instrumentation.md

@@ -44,18 +44,18 @@ We use the Prometheus monitoring system's golang client library for instrumentin
   2. Give the metric a name and description.
   3. Pick whether you want to distinguish different categories of things using labels on the metric. If so, add "Vec" to the name of the type of metric you want and add a slice of the label names to the definition.
 
-   https://github.com/GoogleCloudPlatform/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L53
-   https://github.com/GoogleCloudPlatform/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/kubelet/metrics/metrics.go#L31
+   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L53
+   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/kubelet/metrics/metrics.go#L31
 
 3. Register the metric so that prometheus will know to export it.
 
-   https://github.com/GoogleCloudPlatform/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/kubelet/metrics/metrics.go#L74
-   https://github.com/GoogleCloudPlatform/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L78
+   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/kubelet/metrics/metrics.go#L74
+   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L78
 
 4. Use the metric by calling the appropriate method for your metric type (Set, Inc/Add, or Observe, respectively for Gauge, Counter, or Histogram/Summary), first calling WithLabelValues if your metric has any labels
 
-   https://github.com/GoogleCloudPlatform/kubernetes/blob/3ce7fe8310ff081dbbd3d95490193e1d5250d2c9/pkg/kubelet/kubelet.go#L1384
-   https://github.com/GoogleCloudPlatform/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L87
+   https://github.com/kubernetes/kubernetes/blob/3ce7fe8310ff081dbbd3d95490193e1d5250d2c9/pkg/kubelet/kubelet.go#L1384
+   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L87
 
 
 These are the metric type definitions if you're curious to learn about them or need more information:

docs/devel/issues.md

@@ -33,7 +33,7 @@ Documentation for other releases can be found at
 GitHub Issues for the Kubernetes Project
 ========================================
 
-A list quick overview of how we will review and prioritize incoming issues at https://github.com/GoogleCloudPlatform/kubernetes/issues
+A list quick overview of how we will review and prioritize incoming issues at https://github.com/kubernetes/kubernetes/issues
 
 Priorities
 ----------

docs/devel/making-release-notes.md

@@ -66,7 +66,7 @@ With the final markdown all set, cut and paste it to the top of `CHANGELOG.md`
 
 ### 5) Update the Release page
 
-   * Switch to the [releases](https://github.com/GoogleCloudPlatform/kubernetes/releases) page.
+   * Switch to the [releases](https://github.com/kubernetes/kubernetes/releases) page.
    * Open up the release you are working on.
    * Cut and paste the final markdown from above into the release notes
    * Press Save.

docs/devel/pull-requests.md

@@ -52,7 +52,7 @@ Life of a Pull Request
 
 Unless in the last few weeks of a milestone when we need to reduce churn and stabilize, we aim to be always accepting pull requests.
 
-Either the [on call](https://github.com/GoogleCloudPlatform/kubernetes/wiki/Kubernetes-on-call-rotation) manually or the [submit queue](https://github.com/contrib/tree/master/submit-queue) automatically will manage merging PRs.
+Either the [on call](https://github.com/kubernetes/kubernetes/wiki/Kubernetes-on-call-rotation) manually or the [submit queue](https://github.com/contrib/tree/master/submit-queue) automatically will manage merging PRs.
 
 There are several requirements for the submit queue to work:
 * Author must have signed CLA ("cla: yes" label added to PR)

docs/getting-started-guides/aws.md

@@ -106,7 +106,7 @@ EC2 with user data (cloud-config).
 ### Command line administration tool: `kubectl`
 
 The cluster startup script will leave you with a `kubernetes` directory on your workstation.
-Alternately, you can download the latest Kubernetes release from [this page](https://github.com/GoogleCloudPlatform/kubernetes/releases).
+Alternately, you can download the latest Kubernetes release from [this page](https://github.com/kubernetes/kubernetes/releases).
 
 Next, add the appropriate binary folder to your `PATH` to access kubectl:
 

docs/getting-started-guides/azure.md

@@ -76,7 +76,7 @@ You can create a virtual network:
 
 Now you're ready.
 
-You can download and install the latest Kubernetes release from [this page](https://github.com/GoogleCloudPlatform/kubernetes/releases), then run the `<kubernetes>/cluster/kube-up.sh` script to start the cluster:
+You can download and install the latest Kubernetes release from [this page](https://github.com/kubernetes/kubernetes/releases), then run the `<kubernetes>/cluster/kube-up.sh` script to start the cluster:
 
     cd kubernetes
     cluster/kube-up.sh

docs/getting-started-guides/binary_release.md

@@ -37,7 +37,7 @@ You can either build a release from sources or download a pre-built release.  If
 
 ### Prebuilt Binary Release
 
-The list of binary releases is available for download from the [GitHub Kubernetes repo release page](https://github.com/GoogleCloudPlatform/kubernetes/releases).
+The list of binary releases is available for download from the [GitHub Kubernetes repo release page](https://github.com/kubernetes/kubernetes/releases).
 
 Download the latest release and unpack this tar file on Linux or OS X, cd to the created `kubernetes/` directory, and then follow the getting started guide for your cloud.
 
@@ -48,7 +48,7 @@ Get the Kubernetes source.  If you are simply building a release from source the
 Building a release is simple.
 
 ```bash
-git clone https://github.com/GoogleCloudPlatform/kubernetes.git
+git clone https://github.com/kubernetes/kubernetes.git
 cd kubernetes
 make release
 ```

docs/getting-started-guides/coreos/azure/README.md

@@ -57,7 +57,7 @@ In this guide I will demonstrate how to deploy a Kubernetes cluster to Azure clo
 To get started, you need to checkout the code:
 
 ```sh
-git clone https://github.com/GoogleCloudPlatform/kubernetes
+git clone https://github.com/kubernetes/kubernetes
 cd kubernetes/docs/getting-started-guides/coreos/azure/
 ```
 

docs/getting-started-guides/coreos/bare_metal_calico.md

@@ -63,7 +63,7 @@ In the next few steps you will be asked to configure these files and host them o
 To get the Kubernetes source, clone the GitHub repo, and build the binaries.
 
 ```
-git clone https://github.com/GoogleCloudPlatform/kubernetes.git
+git clone https://github.com/kubernetes/kubernetes.git
 cd kubernetes
 ./build/release.sh 
 ```

docs/getting-started-guides/coreos/bare_metal_offline.md

@@ -412,7 +412,7 @@ On the PXE server make and fill in the variables `vi /var/www/html/coreos/pxe-cl
           content: |
             [Unit]
             Description=Kubernetes API Server
-            Documentation=https://github.com/GoogleCloudPlatform/kubernetes
+            Documentation=https://github.com/kubernetes/kubernetes
             Requires=etcd.service
             After=etcd.service
             [Service]
@@ -432,7 +432,7 @@ On the PXE server make and fill in the variables `vi /var/www/html/coreos/pxe-cl
           content: |
             [Unit]
             Description=Kubernetes Controller Manager
-            Documentation=https://github.com/GoogleCloudPlatform/kubernetes
+            Documentation=https://github.com/kubernetes/kubernetes
             Requires=kube-apiserver.service
             After=kube-apiserver.service
             [Service]
@@ -448,7 +448,7 @@ On the PXE server make and fill in the variables `vi /var/www/html/coreos/pxe-cl
           content: |
             [Unit]
             Description=Kubernetes Scheduler
-            Documentation=https://github.com/GoogleCloudPlatform/kubernetes
+            Documentation=https://github.com/kubernetes/kubernetes
             Requires=kube-apiserver.service
             After=kube-apiserver.service
             [Service]
@@ -579,7 +579,7 @@ On the PXE server make and fill in the variables `vi /var/www/html/coreos/pxe-cl
           content: |
             [Unit]
             Description=Kubernetes Proxy
-            Documentation=https://github.com/GoogleCloudPlatform/kubernetes
+            Documentation=https://github.com/kubernetes/kubernetes
             Requires=setup-network-environment.service
             After=setup-network-environment.service
             [Service]
@@ -595,7 +595,7 @@ On the PXE server make and fill in the variables `vi /var/www/html/coreos/pxe-cl
           content: |
             [Unit]
             Description=Kubernetes Kubelet
-            Documentation=https://github.com/GoogleCloudPlatform/kubernetes
+            Documentation=https://github.com/kubernetes/kubernetes
             Requires=setup-network-environment.service
             After=setup-network-environment.service
             [Service]

docs/getting-started-guides/gce.md

@@ -90,7 +90,7 @@ By default, some containers will already be running on your cluster. Containers
 
 The script run by the commands above creates a cluster with the name/prefix "kubernetes". It defines one specific cluster config, so you can't run it more than once.
 
-Alternately, you can download and install the latest Kubernetes release from [this page](https://github.com/GoogleCloudPlatform/kubernetes/releases), then run the `<kubernetes>/cluster/kube-up.sh` script to start the cluster:
+Alternately, you can download and install the latest Kubernetes release from [this page](https://github.com/kubernetes/kubernetes/releases), then run the `<kubernetes>/cluster/kube-up.sh` script to start the cluster:
 
 ```bash
 cd kubernetes

docs/getting-started-guides/mesos-docker.md

@@ -151,12 +151,12 @@ host machine (mac).
 1. Checkout source
 
     ```
-    git clone https://github.com/GoogleCloudPlatform/kubernetes
+    git clone https://github.com/kubernetes/kubernetes
     cd kubernetes
     ```
 
     By default, that will get you the bleeding edge of master branch.
-    You may want a [release branch](https://github.com/GoogleCloudPlatform/kubernetes/releases) instead,
+    You may want a [release branch](https://github.com/kubernetes/kubernetes/releases) instead,
     if you have trouble with master.
 
 1. Build binaries

docs/getting-started-guides/mesos.md

@@ -85,7 +85,7 @@ ssh jclouds@${ip_address_of_master_node}
 Build Kubernetes-Mesos.
 
 ```bash
-git clone https://github.com/GoogleCloudPlatform/kubernetes
+git clone https://github.com/kubernetes/kubernetes
 cd kubernetes
 export KUBERNETES_CONTRIB=mesos
 make

docs/getting-started-guides/rackspace.md

@@ -91,9 +91,9 @@ There is a specific `cluster/rackspace` directory with the scripts for the follo
 - A number of the items in `config-default.sh` are overridable via environment variables.
 - For older versions please either:
  * Sync back to `v0.9` with `git checkout v0.9`
-  * Download a [snapshot of `v0.9`](https://github.com/GoogleCloudPlatform/kubernetes/archive/v0.9.tar.gz)
+  * Download a [snapshot of `v0.9`](https://github.com/kubernetes/kubernetes/archive/v0.9.tar.gz)
  * Sync back to `v0.3` with `git checkout v0.3`
-  * Download a [snapshot of `v0.3`](https://github.com/GoogleCloudPlatform/kubernetes/archive/v0.3.tar.gz)
+  * Download a [snapshot of `v0.3`](https://github.com/kubernetes/kubernetes/archive/v0.3.tar.gz)
 
 ## Network Design
 

docs/getting-started-guides/scratch.md

@@ -212,7 +212,7 @@ A Kubernetes binary release includes all the Kubernetes binaries as well as the
 You can use a Kubernetes binary release (recommended) or build your Kubernetes binaries following the instructions in the
 [Developer Documentation](../devel/README.md).  Only using a binary release is covered in this guide.
 
-Download the [latest binary release](https://github.com/GoogleCloudPlatform/kubernetes/releases/latest) and unzip it.
+Download the [latest binary release](https://github.com/kubernetes/kubernetes/releases/latest) and unzip it.
 Then locate `./kubernetes/server/kubernetes-server-linux-amd64.tar.gz` and unzip *that*.
 Then, within the second set of unzipped files, locate `./kubernetes/server/bin`, which contains
 all the necessary binaries.
@@ -226,7 +226,7 @@ we recommend that you run these as containers, so you need an image to be built.
 You have several choices for Kubernetes images:
 - Use images hosted on Google Container Registry (GCR):
   - e.g `gcr.io/google_containers/hyperkube:$TAG`, where `TAG` is the latest
-    release tag, which can be found on the [latest releases page](https://github.com/GoogleCloudPlatform/kubernetes/releases/latest).
+    release tag, which can be found on the [latest releases page](https://github.com/kubernetes/kubernetes/releases/latest).
   - Ensure $TAG is the same tag as the release tag you are using for kubelet and kube-proxy.
   - The [hyperkube](../../cmd/hyperkube/) binary is an all in one binary
     - `hyperkube kubelet ...` runs the kublet, `hyperkube apiserver ...` runs an apiserver, etc.

docs/getting-started-guides/ubuntu.md

@@ -69,7 +69,7 @@ Ubuntu 15 which use systemd instead of upstart. We are working around fixing thi
 First clone the kubernetes github repo
 
 ``` console
-$ git clone https://github.com/GoogleCloudPlatform/kubernetes.git
+$ git clone https://github.com/kubernetes/kubernetes.git
 ```
 
 Then download all the needed binaries into given directory (cluster/ubuntu/binaries)

docs/getting-started-guides/vagrant.md

@@ -72,7 +72,7 @@ export KUBERNETES_PROVIDER=vagrant
 curl -sS https://get.k8s.io | bash
 ```
 
-Alternatively, you can download [Kubernetes release](https://github.com/GoogleCloudPlatform/kubernetes/releases) and extract the archive. To start your local cluster, open a shell and run:
+Alternatively, you can download [Kubernetes release](https://github.com/kubernetes/kubernetes/releases) and extract the archive. To start your local cluster, open a shell and run:
 
 ```sh
 cd kubernetes

docs/proposals/autoscaling.md

@@ -47,7 +47,7 @@ done automatically based on statistical analysis and thresholds.
 * Provide a concrete proposal for implementing auto-scaling pods within Kubernetes
 * Implementation proposal should be in line with current discussions in existing issues:
     * Scale verb - [1629](http://issue.k8s.io/1629)
-    * Config conflicts - [Config](https://github.com/GoogleCloudPlatform/kubernetes/blob/c7cb991987193d4ca33544137a5cb7d0292cf7df/docs/config.md#automated-re-configuration-processes)
+    * Config conflicts - [Config](https://github.com/kubernetes/kubernetes/blob/c7cb991987193d4ca33544137a5cb7d0292cf7df/docs/config.md#automated-re-configuration-processes)
     * Rolling updates - [1353](http://issue.k8s.io/1353)
     * Multiple scalable types - [1624](http://issue.k8s.io/1624)