Merge pull request #4138 from soltysh/move_k8s_repo

Merged by openshift-bot

Author: OpenShift Bot

CONTRIBUTING.adoc

@@ -5,7 +5,7 @@ OpenShift Developers <[email protected]>
 :toc2:
 :sectanchors:
 
-The OpenShift architecture builds upon the flexibility and scalability of https://docker.com/[Docker] and https://github.com/GoogleCloudPlatform/kubernetes[Kubernetes] to deliver a powerful new https://www.youtube.com/watch?v=aZ40GobvA1c[Platform-as-a-Service] system. This article explains how to set up a development environment and get involved with this latest version of OpenShift.  Kubernetes is included in this repo for ease of development, and the version we include is periodically updated.
+The OpenShift architecture builds upon the flexibility and scalability of https://docker.com/[Docker] and https://github.com/kubernetes/kubernetes[Kubernetes] to deliver a powerful new https://www.youtube.com/watch?v=aZ40GobvA1c[Platform-as-a-Service] system. This article explains how to set up a development environment and get involved with this latest version of OpenShift.  Kubernetes is included in this repo for ease of development, and the version we include is periodically updated.
 
 To get started you can either:
 
@@ -24,7 +24,7 @@ The OpenShift team periodically publishes binaries to GitHub on https://github.c
 
 The tar file for each platform contains a single binary `openshift` which is the all-in-one OpenShift installation.
 
-* Use `sudo openshift start` to launch the server.  Root access is required to create services due to the need to modify IPTables.  See issue: https://github.com/GoogleCloudPlatform/kubernetes/issues/1859.
+* Use `sudo openshift start` to launch the server.  Root access is required to create services due to the need to modify IPTables.  See issue: https://github.com/kubernetes/kubernetes/issues/1859.
 * Use `oc login <server> ...` to connect to an OpenShift server
 * Use `openshift help` to see more about the commands in the binary
 
@@ -202,7 +202,7 @@ https://github.com/openshift/origin[github.com/openshift/origin]
 Ready to play with some code? Hop down and read up on our link:#_the_roadmap[roadmap] for ideas on where you can contribute.
 
 *If you are interested in contributing to Kubernetes directly:* +
-https://github.com/GoogleCloudPlatform/kubernetes#community-discussion-and-support[Join the Kubernetes community] and check out the https://github.com/GoogleCloudPlatform/kubernetes/blob/master/CONTRIBUTING.md[contributing guide].
+https://github.com/kubernetes/kubernetes#community-discussion-and-support[Join the Kubernetes community] and check out the https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md[contributing guide].
 
 == Troubleshooting
 

HACKING.md

@@ -186,15 +186,15 @@ were properly reflected* in the Origin codebase.
 ### 1. Preparation
 
 Before you begin, make sure you have both [openshift/origin](https://github.com/openshift/origin) and
-[GoogleCloudPlatform/kubernetes](https://github.com/GoogleCloudPlatform/kubernetes) in your $GOPATH:
+[kubernetes/kubernetes](https://github.com/kubernetes/kubernetes) in your $GOPATH:
 
 ```
 $ go get github.com/openshift/origin
 $ go get k8s.io/kubernetes
 ```
 
 Check out the version of Kubernetes you want to rebase as a branch or tag named `stable_proposed` in
-[GoogleCloudPlatform/kubernetes](https://github.com/GoogleCloudPlatform/kubernetes). For example,
+[kubernetes/kubernetes](https://github.com/kubernetes/kubernetes). For example,
 if you are going to rebase the latest `master` of Kubernetes:
 
 ```

README.md

@@ -5,7 +5,7 @@ OpenShift Application Platform
 [![Travis](https://travis-ci.org/openshift/origin.svg?branch=master)](https://travis-ci.org/openshift/origin)
 
 This is the source repository for [OpenShift 3](https://openshift.github.io), based on top of [Docker](https://www.docker.io) containers and the
-[Kubernetes](https://github.com/GoogleCloudPlatform/kubernetes) container cluster manager.
+[Kubernetes](https://github.com/kubernetes/kubernetes) container cluster manager.
 OpenShift adds developer and operational centric tools on top of Kubernetes to enable rapid application development,
 easy deployment and scaling, and long-term lifecycle maintenance for small and large teams and applications.
 
@@ -108,8 +108,8 @@ We highly recommend trying out the [OpenShift walkthrough](https://github.com/op
 Both OpenShift and Kubernetes have a strong focus on documentation - see the following for more information about them:
 
 * [OpenShift Documentation](http://docs.openshift.org/latest/welcome/index.html)
-* [Kubernetes Getting Started](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/README.md)
-* [Kubernetes Documentation](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/README.md)
+* [Kubernetes Getting Started](https://github.com/kubernetes/kubernetes/blob/master/README.md)
+* [Kubernetes Documentation](https://github.com/kubernetes/kubernetes/blob/master/docs/README.md)
 
 
 ### Troubleshooting
@@ -177,7 +177,7 @@ You can develop [locally on your host](CONTRIBUTING.adoc#develop-locally-on-your
 
 First, **get up and running with the** [**Contributing Guide**](CONTRIBUTING.adoc).
 
-All contributions are welcome - OpenShift uses the Apache 2 license and does not require any contributor agreement to submit patches.  Please open issues for any bugs or problems you encounter, ask questions on the OpenShift IRC channel (#openshift-dev on freenode), or get involved in the [Kubernetes project](https://github.com/GoogleCloudPlatform/kubernetes) at the container runtime layer.
+All contributions are welcome - OpenShift uses the Apache 2 license and does not require any contributor agreement to submit patches.  Please open issues for any bugs or problems you encounter, ask questions on the OpenShift IRC channel (#openshift-dev on freenode), or get involved in the [Kubernetes project](https://github.com/kubernetes/kubernetes) at the container runtime layer.
 
 See [HACKING.md](https://github.com/openshift/origin/blob/master/HACKING.md) for more details on developing on OpenShift including how different tests are setup.
 

api/definitions/v1.pod/description.adoc

@@ -1,3 +1,3 @@
 A pod corresponds to a group of containers running together on the same machine. All containers in a pod share an IP address, and may have access to shared volumes and local fileystem. Like individual application containers, pods are considered to be relatively ephemeral rather than durable entities. Pods are scheduled to nodes and remain there until termination (according to restart policy) or deletion. When a node dies, the pods scheduled to that node are deleted. Specific pods are never rescheduled to new nodes; instead, they must be replaced by a component like the replication controller.
 
-See link:https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/pods.md[the Kubernetes pod documentation] for more information.
+See link:https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/pods.md[the Kubernetes pod documentation] for more information.

api/definitions/v1.service/description.adoc

@@ -4,4 +4,4 @@ Services may be exposed only inside the cluster (type ClusterIP), inside the clu
 
 If the selector for pods is not specified, the service endpoints may be managed by the client directly. Update the endpoint resource to program the service - this can be used to inject external network services into a namsepace.
 
-See link:https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/services.md[the Kubernetes service documentation] for more information.
+See link:https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/services.md[the Kubernetes service documentation] for more information.

docs/atomic-quick-start-tutorial.adoc

@@ -218,7 +218,7 @@ curl http://$IP_FROM_ABOVE:8080/
 
 18 Try new things
 -----------------
-That’s it, your system should be up and running.  You can now add new nodes.  Try adding the internal registry with the “oadm registry” command.  Or try adding the enterprise router with the “oadm router” command.  You can also take a look at other kubernetes examples: https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples
+That’s it, your system should be up and running.  You can now add new nodes.  Try adding the internal registry with the “oadm registry” command.  Or try adding the enterprise router with the “oadm router” command.  You can also take a look at other kubernetes examples: https://github.com/kubernetes/kubernetes/tree/master/examples
 
 [IMPORTANT]
 Remember to use the “oc” command instead of the “kubectl” command when using Atomic Enterprise Platform.

docs/cli.md

@@ -700,7 +700,7 @@ This destroys the session token, preventing further access until next login (wit
 
 ### oc config
 
-This manages the OpenShift [kubeconfig files](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/kubeconfig-file.md).
+This manages the OpenShift [kubeconfig files](https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/kubeconfig-file.md).
 The general form is:
 
 ```bash

docs/openshift_model.md

@@ -37,7 +37,7 @@ Model object that stores the logs from a particular build for later inspection.
 
 ## Deployment
 
-A deployment is a specially annotated [replicationController](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/replication-controller.md), specifying the desired configuration of that controller. See the [deployments](deployments.md) document.
+A deployment is a specially annotated [replicationController](https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/replication-controller.md), specifying the desired configuration of that controller. See the [deployments](deployments.md) document.
 
 ## DeploymentConfig
 

docs/proposals/metadata.md

@@ -162,7 +162,7 @@ to work properly. The UI might warn the user that deploying this Docker image
 may exceed their user quota.
 
 The values must be compatible with [Kubernetes
-quantity](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/resources.md#resource-quantities) values for CPU and memory.
+quantity](https://github.com/kubernetes/kubernetes/blob/master/docs/design/resources.md#resource-quantities) values for CPU and memory.
 
 *Example:*