From 04fc8ae3dd2c07e285d39b96be3657dea468763c Mon Sep 17 00:00:00 2001 From: Eric Paris Date: Thu, 3 Sep 2015 10:10:11 -0400 Subject: [PATCH] s|github.com/GoogleCloudPlatform/kubernetes|github.com/kubernetes/kubernetes| --- CHANGELOG.md | 2 +- .../fluentd-elasticsearch/fluentd-es-image/README.md | 2 +- .../addons/fluentd-gcp/fluentd-gcp-image/README.md | 2 +- docs/admin/authentication.md | 4 ++-- docs/admin/node.md | 2 +- docs/design/architecture.md | 2 +- docs/devel/cherry-picks.md | 2 +- docs/devel/cli-roadmap.md | 6 +++--- docs/devel/flaky-tests.md | 2 +- docs/devel/instrumentation.md | 12 ++++++------ docs/devel/issues.md | 2 +- docs/devel/making-release-notes.md | 2 +- docs/devel/pull-requests.md | 2 +- docs/getting-started-guides/aws.md | 2 +- docs/getting-started-guides/azure.md | 2 +- docs/getting-started-guides/binary_release.md | 4 ++-- docs/getting-started-guides/coreos/azure/README.md | 2 +- .../coreos/bare_metal_calico.md | 2 +- .../coreos/bare_metal_offline.md | 10 +++++----- docs/getting-started-guides/gce.md | 2 +- docs/getting-started-guides/mesos-docker.md | 4 ++-- docs/getting-started-guides/mesos.md | 2 +- docs/getting-started-guides/rackspace.md | 4 ++-- docs/getting-started-guides/scratch.md | 4 ++-- docs/getting-started-guides/ubuntu.md | 2 +- docs/getting-started-guides/vagrant.md | 2 +- docs/proposals/autoscaling.md | 2 +- docs/proposals/deployment.md | 2 +- docs/proposals/horizontal-pod-autoscaler.md | 8 ++++---- docs/proposals/job.md | 6 +++--- docs/roadmap.md | 2 +- docs/user-guide/application-troubleshooting.md | 4 ++-- docs/user-guide/compute-resources.md | 2 +- docs/user-guide/configuring-containers.md | 4 ++-- docs/user-guide/connecting-applications.md | 2 +- docs/user-guide/debugging-services.md | 2 +- docs/user-guide/deploying-applications.md | 2 +- docs/user-guide/node-selection/README.md | 4 ++-- docs/user-guide/pods.md | 2 +- docs/user-guide/prereqs.md | 2 +- docs/user-guide/replication-controller.md | 2 +- docs/user-guide/services.md | 2 +- docs/user-guide/walkthrough/README.md | 2 +- docs/user-guide/walkthrough/k8s201.md | 4 ++-- examples/javaee/README.md | 2 +- logo_usage_guidelines.md | 8 ++++---- third_party/swagger-ui/README.md | 2 +- 47 files changed, 75 insertions(+), 75 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3c45c725a88..a4daafba0fc 100644 --- a/CHANGELOG.md +++ b/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)]() diff --git a/cluster/addons/fluentd-elasticsearch/fluentd-es-image/README.md b/cluster/addons/fluentd-elasticsearch/fluentd-es-image/README.md index 8040f686db0..1dd1268ff1f 100644 --- a/cluster/addons/fluentd-elasticsearch/fluentd-es-image/README.md +++ b/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/). diff --git a/cluster/addons/fluentd-gcp/fluentd-gcp-image/README.md b/cluster/addons/fluentd-gcp/fluentd-gcp-image/README.md index f7393f02f1c..a663d2f131b 100644 --- a/cluster/addons/fluentd-gcp/fluentd-gcp-image/README.md +++ b/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/). diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md index 8ab706f2a5f..c6039a4f0e5 100644 --- a/docs/admin/authentication.md +++ b/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 diff --git a/docs/admin/node.md b/docs/admin/node.md index 569d5c592a0..2d5520311a3 100644 --- a/docs/admin/node.md +++ b/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). diff --git a/docs/design/architecture.md b/docs/design/architecture.md index b17345efc94..2a761dea645 100644 --- a/docs/design/architecture.md +++ b/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. diff --git a/docs/devel/cherry-picks.md b/docs/devel/cherry-picks.md index 519c73c3dc9..7cb6046563b 100644 --- a/docs/devel/cherry-picks.md +++ b/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) diff --git a/docs/devel/cli-roadmap.md b/docs/devel/cli-roadmap.md index 6908455566d..42784dbcf4e 100644 --- a/docs/devel/cli-roadmap.md +++ b/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) diff --git a/docs/devel/flaky-tests.md b/docs/devel/flaky-tests.md index 9db9e15cd56..3a7af51e4f3 100644 --- a/docs/devel/flaky-tests.md +++ b/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. diff --git a/docs/devel/instrumentation.md b/docs/devel/instrumentation.md index 8cc9e2b2b1c..683f9d936ea 100644 --- a/docs/devel/instrumentation.md +++ b/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: diff --git a/docs/devel/issues.md b/docs/devel/issues.md index 46beb9ce17e..c7bda07b7db 100644 --- a/docs/devel/issues.md +++ b/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 ---------- diff --git a/docs/devel/making-release-notes.md b/docs/devel/making-release-notes.md index 1efab1ac7da..871e65b48cd 100644 --- a/docs/devel/making-release-notes.md +++ b/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. diff --git a/docs/devel/pull-requests.md b/docs/devel/pull-requests.md index 157646c0540..a81c01c57d7 100644 --- a/docs/devel/pull-requests.md +++ b/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) diff --git a/docs/getting-started-guides/aws.md b/docs/getting-started-guides/aws.md index 526b10ab355..a55c1f92b3d 100644 --- a/docs/getting-started-guides/aws.md +++ b/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: diff --git a/docs/getting-started-guides/azure.md b/docs/getting-started-guides/azure.md index c0c1cf30342..1983bc8773d 100644 --- a/docs/getting-started-guides/azure.md +++ b/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 `/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 `/cluster/kube-up.sh` script to start the cluster: cd kubernetes cluster/kube-up.sh diff --git a/docs/getting-started-guides/binary_release.md b/docs/getting-started-guides/binary_release.md index 49e0f12b930..d483e765558 100644 --- a/docs/getting-started-guides/binary_release.md +++ b/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 ``` diff --git a/docs/getting-started-guides/coreos/azure/README.md b/docs/getting-started-guides/coreos/azure/README.md index 40ec141dc1d..4bee80ff37a 100644 --- a/docs/getting-started-guides/coreos/azure/README.md +++ b/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/ ``` diff --git a/docs/getting-started-guides/coreos/bare_metal_calico.md b/docs/getting-started-guides/coreos/bare_metal_calico.md index 2945514301c..d2bef03e92e 100644 --- a/docs/getting-started-guides/coreos/bare_metal_calico.md +++ b/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 ``` diff --git a/docs/getting-started-guides/coreos/bare_metal_offline.md b/docs/getting-started-guides/coreos/bare_metal_offline.md index 1083c91e128..c32a5172142 100644 --- a/docs/getting-started-guides/coreos/bare_metal_offline.md +++ b/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] diff --git a/docs/getting-started-guides/gce.md b/docs/getting-started-guides/gce.md index 1ae240f0ba6..cf542d42de9 100644 --- a/docs/getting-started-guides/gce.md +++ b/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 `/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 `/cluster/kube-up.sh` script to start the cluster: ```bash cd kubernetes diff --git a/docs/getting-started-guides/mesos-docker.md b/docs/getting-started-guides/mesos-docker.md index 597841d1956..e56b230bf0a 100644 --- a/docs/getting-started-guides/mesos-docker.md +++ b/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 diff --git a/docs/getting-started-guides/mesos.md b/docs/getting-started-guides/mesos.md index 888447147b9..15539984b47 100644 --- a/docs/getting-started-guides/mesos.md +++ b/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 diff --git a/docs/getting-started-guides/rackspace.md b/docs/getting-started-guides/rackspace.md index 9f7a3f08a35..c0066c582bb 100644 --- a/docs/getting-started-guides/rackspace.md +++ b/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 diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md index 0ac88880870..1a74a3eef21 100644 --- a/docs/getting-started-guides/scratch.md +++ b/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. diff --git a/docs/getting-started-guides/ubuntu.md b/docs/getting-started-guides/ubuntu.md index 0ed0cc7719c..3c2c484e02f 100644 --- a/docs/getting-started-guides/ubuntu.md +++ b/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) diff --git a/docs/getting-started-guides/vagrant.md b/docs/getting-started-guides/vagrant.md index 6eb7cf674e6..49c1828c379 100644 --- a/docs/getting-started-guides/vagrant.md +++ b/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 diff --git a/docs/proposals/autoscaling.md b/docs/proposals/autoscaling.md index 9c5ec752261..ea60af7443e 100644 --- a/docs/proposals/autoscaling.md +++ b/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) diff --git a/docs/proposals/deployment.md b/docs/proposals/deployment.md index 0a79ca860db..6819acee5b0 100644 --- a/docs/proposals/deployment.md +++ b/docs/proposals/deployment.md @@ -260,7 +260,7 @@ Apart from the above, we want to add support for the following: ## References -- https://github.com/GoogleCloudPlatform/kubernetes/issues/1743 has most of the +- https://github.com/kubernetes/kubernetes/issues/1743 has most of the discussion that resulted in this proposal. diff --git a/docs/proposals/horizontal-pod-autoscaler.md b/docs/proposals/horizontal-pod-autoscaler.md index c10f54f7881..6ae84532fc7 100644 --- a/docs/proposals/horizontal-pod-autoscaler.md +++ b/docs/proposals/horizontal-pod-autoscaler.md @@ -61,7 +61,7 @@ HorizontalPodAutoscaler object will be bound with exactly one Scale subresource autoscaling associated replication controller/deployment through it. The main advantage of such approach is that whenever we introduce another type we want to auto-scale, we just need to implement Scale subresource for it (w/o modifying autoscaler code or API). -The wider discussion regarding Scale took place in [#1629](https://github.com/GoogleCloudPlatform/kubernetes/issues/1629). +The wider discussion regarding Scale took place in [#1629](https://github.com/kubernetes/kubernetes/issues/1629). Scale subresource will be present in API for replication controller or deployment under the following paths: @@ -192,7 +192,7 @@ The autoscaler will be implemented as a control loop. It will periodically (e.g.: every 1 minute) query pods described by ```Status.PodSelector``` of Scale subresource, and check their average CPU or memory usage from the last 1 minute (there will be API on master for this purpose, see -[#11951](https://github.com/GoogleCloudPlatform/kubernetes/issues/11951). +[#11951](https://github.com/kubernetes/kubernetes/issues/11951). Then, it will compare the current CPU or memory consumption with the Target, and adjust the count of the Scale if needed to match the target (preserving condition: MinCount <= Count <= MaxCount). @@ -265,9 +265,9 @@ Our design is in general compatible with them. and then turned-on when there is a demand for them. When a request to service with no pods arrives, kube-proxy will generate an event for autoscaler to create a new pod. - Discussed in [#3247](https://github.com/GoogleCloudPlatform/kubernetes/issues/3247). + Discussed in [#3247](https://github.com/kubernetes/kubernetes/issues/3247). * When scaling down, make more educated decision which pods to kill (e.g.: if two or more pods are on the same node, kill one of them). - Discussed in [#4301](https://github.com/GoogleCloudPlatform/kubernetes/issues/4301). + Discussed in [#4301](https://github.com/kubernetes/kubernetes/issues/4301). * Allow rule based autoscaling: instead of specifying the target value for metric, specify a rule, e.g.: “if average CPU consumption of pod is higher than 80% add two more replicas”. This approach was initially suggested in diff --git a/docs/proposals/job.md b/docs/proposals/job.md index 57717ea58a0..198a1437fbd 100644 --- a/docs/proposals/job.md +++ b/docs/proposals/job.md @@ -40,8 +40,8 @@ for managing pod(s) that require running once to completion even if the machine the pod is running on fails, in contrast to what ReplicationController currently offers. Several existing issues and PRs were already created regarding that particular subject: -* Job Controller [#1624](https://github.com/GoogleCloudPlatform/kubernetes/issues/1624) -* New Job resource [#7380](https://github.com/GoogleCloudPlatform/kubernetes/pull/7380) +* Job Controller [#1624](https://github.com/kubernetes/kubernetes/issues/1624) +* New Job resource [#7380](https://github.com/kubernetes/kubernetes/pull/7380) ## Use Cases @@ -181,7 +181,7 @@ Below are the possible future extensions to the Job controller: * Be able to limit the execution time for a job, similarly to ActiveDeadlineSeconds for Pods. * Be able to create a chain of jobs dependent one on another. * Be able to specify the work each of the workers should execute (see type 1 from - [this comment](https://github.com/GoogleCloudPlatform/kubernetes/issues/1624#issuecomment-97622142)) + [this comment](https://github.com/kubernetes/kubernetes/issues/1624#issuecomment-97622142)) * Be able to inspect Pods running a Job, especially after a Job has finished, e.g. by providing pointers to Pods in the JobStatus ([see comment](https://github.com/kubernetes/kubernetes/pull/11746/files#r37142628)). diff --git a/docs/roadmap.md b/docs/roadmap.md index 38c8d98bdec..2b01a0c4e77 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -35,7 +35,7 @@ Documentation for other releases can be found at We're in the process of prioritizing changes to be made after 1.0. -Please watch the [Github milestones] (https://github.com/GoogleCloudPlatform/kubernetes/milestones) for our future plans. +Please watch the [Github milestones] (https://github.com/kubernetes/kubernetes/milestones) for our future plans. diff --git a/docs/user-guide/application-troubleshooting.md b/docs/user-guide/application-troubleshooting.md index 54cb40fde7d..abe7778fc32 100644 --- a/docs/user-guide/application-troubleshooting.md +++ b/docs/user-guide/application-troubleshooting.md @@ -58,7 +58,7 @@ This is *not* a guide for people who want to debug their cluster. For that you ## FAQ -Users are highly encouraged to check out our [FAQ](https://github.com/GoogleCloudPlatform/kubernetes/wiki/User-FAQ) +Users are highly encouraged to check out our [FAQ](https://github.com/kubernetes/kubernetes/wiki/User-FAQ) ## Diagnosing the problem @@ -152,7 +152,7 @@ If you misspelled `command` as `commnd` then will give an error like this: ``` I0805 10:43:25.129850 46757 schema.go:126] unknown field: commnd -I0805 10:43:25.129973 46757 schema.go:129] this may be a false alarm, see https://github.com/GoogleCloudPlatform/kubernetes/issues/6842 +I0805 10:43:25.129973 46757 schema.go:129] this may be a false alarm, see https://github.com/kubernetes/kubernetes/issues/6842 pods/mypod ``` diff --git a/docs/user-guide/compute-resources.md b/docs/user-guide/compute-resources.md index 8e961d35e6e..0ff1442daa4 100644 --- a/docs/user-guide/compute-resources.md +++ b/docs/user-guide/compute-resources.md @@ -255,7 +255,7 @@ You can call `get pod` with the `-o template -t ...` option to fetch the status ```console [13:59:01] $ ./cluster/kubectl.sh get pod -o template -t '{{range.status.containerStatuses}}{{"Container Name: "}}{{.name}}{{"\r\nLastState: "}}{{.lastState}}{{end}}' simmemleak-60xbc Container Name: simmemleak -LastState: map[terminated:map[exitCode:137 reason:OOM Killed startedAt:2015-07-07T20:58:43Z finishedAt:2015-07-07T20:58:43Z containerID:docker://0e4095bba1feccdfe7ef9fb6ebffe972b4b14285d5acdec6f0d3ae8a22fad8b2]][13:59:03] clusterScaleDoc ~/go/src/github.com/GoogleCloudPlatform/kubernetes $ +LastState: map[terminated:map[exitCode:137 reason:OOM Killed startedAt:2015-07-07T20:58:43Z finishedAt:2015-07-07T20:58:43Z containerID:docker://0e4095bba1feccdfe7ef9fb6ebffe972b4b14285d5acdec6f0d3ae8a22fad8b2]][13:59:03] clusterScaleDoc ~/go/src/github.com/kubernetes/kubernetes $ ``` We can see that this container was terminated because `reason:OOM Killed`, where *OOM* stands for Out Of Memory. diff --git a/docs/user-guide/configuring-containers.md b/docs/user-guide/configuring-containers.md index 493b4d36d7e..76bc72fd00f 100644 --- a/docs/user-guide/configuring-containers.md +++ b/docs/user-guide/configuring-containers.md @@ -109,12 +109,12 @@ pods/hello-world `kubectl create --validate` currently warns about problems it detects, but creates the resource anyway, unless a required field is absent or a field value is invalid. Unknown API fields are ignored, so be careful. This pod was created, but with no `command`, which is an optional field, since the image may specify an `Entrypoint`. View the [Pod API -object](https://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_pod) +object](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_pod) to see the list of valid fields. ## Environment variables and variable expansion -Kubernetes [does not automatically run commands in a shell](https://github.com/GoogleCloudPlatform/kubernetes/wiki/User-FAQ#use-of-environment-variables-on-the-command-line) (not all images contain shells). If you would like to run your command in a shell, such as to expand environment variables (specified using `env`), you could do the following: +Kubernetes [does not automatically run commands in a shell](https://github.com/kubernetes/kubernetes/wiki/User-FAQ#use-of-environment-variables-on-the-command-line) (not all images contain shells). If you would like to run your command in a shell, such as to expand environment variables (specified using `env`), you could do the following: ```yaml apiVersion: v1 diff --git a/docs/user-guide/connecting-applications.md b/docs/user-guide/connecting-applications.md index fca07b946a8..4739c32b37a 100644 --- a/docs/user-guide/connecting-applications.md +++ b/docs/user-guide/connecting-applications.md @@ -128,7 +128,7 @@ spec: app: nginx ``` -This specification will create a Service which targets TCP port 80 on any Pod with the `app=nginx` label, and expose it on an abstracted Service port (`targetPort`: is the port the container accepts traffic on, `port`: is the abstracted Service port, which can be any port other pods use to access the Service). View [service API object](https://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_service) to see the list of supported fields in service definition. +This specification will create a Service which targets TCP port 80 on any Pod with the `app=nginx` label, and expose it on an abstracted Service port (`targetPort`: is the port the container accepts traffic on, `port`: is the abstracted Service port, which can be any port other pods use to access the Service). View [service API object](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_service) to see the list of supported fields in service definition. Check your Service: ```console diff --git a/docs/user-guide/debugging-services.md b/docs/user-guide/debugging-services.md index 1750f2fec3f..a439f6cff38 100644 --- a/docs/user-guide/debugging-services.md +++ b/docs/user-guide/debugging-services.md @@ -548,7 +548,7 @@ us know, so we can help investigate! Contact us on [IRC](http://webchat.freenode.net/?channels=google-containers) or [email](https://groups.google.com/forum/#!forum/google-containers) or -[GitHub](https://github.com/GoogleCloudPlatform/kubernetes). +[GitHub](https://github.com/kubernetes/kubernetes). ## More information diff --git a/docs/user-guide/deploying-applications.md b/docs/user-guide/deploying-applications.md index a8fa89357ad..6d9af19284d 100644 --- a/docs/user-guide/deploying-applications.md +++ b/docs/user-guide/deploying-applications.md @@ -76,7 +76,7 @@ spec: Some differences compared to specifying just a pod are that the `kind` is `ReplicationController`, the number of `replicas` desired is specified, and the pod specification is under the `template` field. The names of the pods don’t need to be specified explicitly because they are generated from the name of the replication controller. View the [replication controller API -object](https://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_replicationcontroller) +object](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_replicationcontroller) to view the list of supported fields. This replication controller can be created using `create`, just as with pods: diff --git a/docs/user-guide/node-selection/README.md b/docs/user-guide/node-selection/README.md index d4e21841502..c97d1e24140 100644 --- a/docs/user-guide/node-selection/README.md +++ b/docs/user-guide/node-selection/README.md @@ -37,7 +37,7 @@ This example shows how to assign a [pod](../pods.md) to a specific [node](../../ ### Step Zero: Prerequisites -This example assumes that you have a basic understanding of Kubernetes pods and that you have [turned up a Kubernetes cluster](https://github.com/GoogleCloudPlatform/kubernetes#documentation). +This example assumes that you have a basic understanding of Kubernetes pods and that you have [turned up a Kubernetes cluster](https://github.com/kubernetes/kubernetes#documentation). ### Step One: Attach label to the node @@ -45,7 +45,7 @@ Run `kubectl get nodes` to get the names of your cluster's nodes. Pick out the o Then, to add a label to the node you've chosen, run `kubectl label nodes =`. For example, if my node name is 'kubernetes-foo-node-1.c.a-robinson.internal' and my desired label is 'disktype=ssd', then I can run `kubectl label nodes kubernetes-foo-node-1.c.a-robinson.internal disktype=ssd`. -If this fails with an "invalid command" error, you're likely using an older version of kubectl that doesn't have the `label` command. In that case, see the [previous version](https://github.com/GoogleCloudPlatform/kubernetes/blob/a053dbc313572ed60d89dae9821ecab8bfd676dc/examples/node-selection/README.md) of this guide for instructions on how to manually set labels on a node. +If this fails with an "invalid command" error, you're likely using an older version of kubectl that doesn't have the `label` command. In that case, see the [previous version](https://github.com/kubernetes/kubernetes/blob/a053dbc313572ed60d89dae9821ecab8bfd676dc/examples/node-selection/README.md) of this guide for instructions on how to manually set labels on a node. Also, note that label keys must be in the form of DNS labels (as described in the [identifiers doc](../../../docs/design/identifiers.md)), meaning that they are not allowed to contain any upper-case letters. diff --git a/docs/user-guide/pods.md b/docs/user-guide/pods.md index 4d6950688b2..ac2b6cecd16 100644 --- a/docs/user-guide/pods.md +++ b/docs/user-guide/pods.md @@ -114,7 +114,7 @@ The current best practice for pets is to create a replication controller with `r Pod is a top-level resource in the kubernetes REST API. More details about the API object can be found at: [Pod API -object](https://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_pod). +object](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_pod). diff --git a/docs/user-guide/prereqs.md b/docs/user-guide/prereqs.md index c0ce1ba03e0..3918364cc41 100644 --- a/docs/user-guide/prereqs.md +++ b/docs/user-guide/prereqs.md @@ -37,7 +37,7 @@ To deploy and manage applications on Kubernetes, you’ll use the Kubernetes com ## Installing kubectl -If you downloaded a pre-compiled [release](https://github.com/GoogleCloudPlatform/kubernetes/releases), kubectl should be under `platforms//` from the tar bundle. +If you downloaded a pre-compiled [release](https://github.com/kubernetes/kubernetes/releases), kubectl should be under `platforms//` from the tar bundle. If you built from source, kubectl should be either under `_output/local/bin//` or `_output/dockerized/bin//`. diff --git a/docs/user-guide/replication-controller.md b/docs/user-guide/replication-controller.md index 00033ba3834..d0d968104d8 100644 --- a/docs/user-guide/replication-controller.md +++ b/docs/user-guide/replication-controller.md @@ -122,7 +122,7 @@ For instance, a service might target all pods with `tier in (frontend), environm Replication controller is a top-level resource in the kubernetes REST API. More details about the API object can be found at: [ReplicationController API -object](https://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_replicationcontroller). +object](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_replicationcontroller). diff --git a/docs/user-guide/services.md b/docs/user-guide/services.md index 99242d6a476..2badff776ae 100644 --- a/docs/user-guide/services.md +++ b/docs/user-guide/services.md @@ -545,7 +545,7 @@ of which `Pods` they are actually accessing. Service is a top-level resource in the kubernetes REST API. More details about the API object can be found at: [Service API -object](https://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_service). +object](https://htmlpreview.github.io/?https://github.com/kubernetes/kubernetes/HEAD/docs/api-reference/definitions.html#_v1_service). diff --git a/docs/user-guide/walkthrough/README.md b/docs/user-guide/walkthrough/README.md index 14418d25c7e..fd5e5f92f01 100644 --- a/docs/user-guide/walkthrough/README.md +++ b/docs/user-guide/walkthrough/README.md @@ -35,7 +35,7 @@ Documentation for other releases can be found at For Kubernetes 101, we will cover kubectl, pods, volumes, and multiple containers -In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/GoogleCloudPlatform/kubernetes/releases) or [the source](https://github.com/GoogleCloudPlatform/kubernetes). +In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/kubernetes/kubernetes/releases) or [the source](https://github.com/kubernetes/kubernetes). **Table of Contents** diff --git a/docs/user-guide/walkthrough/k8s201.md b/docs/user-guide/walkthrough/k8s201.md index fa416d513ab..46b99f6d036 100644 --- a/docs/user-guide/walkthrough/k8s201.md +++ b/docs/user-guide/walkthrough/k8s201.md @@ -37,7 +37,7 @@ If you went through [Kubernetes 101](README.md), you learned about kubectl, pods For Kubernetes 201, we will pick up where 101 left off and cover some slightly more advanced topics in Kubernetes, related to application productionization, deployment and scaling. -In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/GoogleCloudPlatform/kubernetes/releases) or [the source](https://github.com/GoogleCloudPlatform/kubernetes). +In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/kubernetes/kubernetes/releases) or [the source](https://github.com/kubernetes/kubernetes). **Table of Contents** @@ -235,7 +235,7 @@ For more information, see [Services](../services.md). ## Health Checking -When I write code it never crashes, right? Sadly the [Kubernetes issues list](https://github.com/GoogleCloudPlatform/kubernetes/issues) indicates otherwise... +When I write code it never crashes, right? Sadly the [Kubernetes issues list](https://github.com/kubernetes/kubernetes/issues) indicates otherwise... Rather than trying to write bug-free code, a better approach is to use a management system to perform periodic health checking and repair of your application. That way a system outside of your application itself is responsible for monitoring the diff --git a/examples/javaee/README.md b/examples/javaee/README.md index 10f76263682..b5f609c3057 100644 --- a/examples/javaee/README.md +++ b/examples/javaee/README.md @@ -37,7 +37,7 @@ The following document describes the deployment of a Java EE application using [ ### Prerequisites -https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/user-guide/prereqs.md +https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/prereqs.md ### Start MySQL Pod diff --git a/logo_usage_guidelines.md b/logo_usage_guidelines.md index 1dba3b3413e..12661a5fd7d 100644 --- a/logo_usage_guidelines.md +++ b/logo_usage_guidelines.md @@ -2,17 +2,17 @@ These guidelines provide you with guidance for using the Kubernetes logo. You can use the logo on your website or in print without pre-approval, provided you follow these basic guidelines. -You may display, modify or use the Kubernetes logo only in connection with compliant implementations of Kubernetes and related uses in the following ways. A compliant implementation is an implementation of the unmodified Google version of Kubernetes found at https://github.com/GoogleCloudPlatform/kubernetes and compatible branches thereof, together with published specifications, APIs and operational patterns.  Acceptable related uses include display, modify or use of the Kubernetes logo in connection with your compliant implementation, your integration with a compliant implementation, your support for a compliant implementation, your Kubernetes-compatible product, or in collateral, presentations, and marketing materials relating to compliant implementations of Kubernetes. +You may display, modify or use the Kubernetes logo only in connection with compliant implementations of Kubernetes and related uses in the following ways. A compliant implementation is an implementation of the unmodified Google version of Kubernetes found at https://github.com/kubernetes/kubernetes and compatible branches thereof, together with published specifications, APIs and operational patterns.  Acceptable related uses include display, modify or use of the Kubernetes logo in connection with your compliant implementation, your integration with a compliant implementation, your support for a compliant implementation, your Kubernetes-compatible product, or in collateral, presentations, and marketing materials relating to compliant implementations of Kubernetes. Use of the Kubernetes logo or other Google brands in ways not expressly covered by this document is not allowed without prior written consent from Google -- see Google's [Guidelines for Third Party Use of Google Brand Features](http://www.google.com/intl/en/permissions/guidelines.html) for more information. ## Links to logo images -[SVG format](https://github.com/GoogleCloudPlatform/kubernetes/raw/master/logo.svg) +[SVG format](https://github.com/kubernetes/kubernetes/raw/master/logo.svg) -[PNG format](https://github.com/GoogleCloudPlatform/kubernetes/raw/master/logo.png) +[PNG format](https://github.com/kubernetes/kubernetes/raw/master/logo.png) -[PDF format](https://github.com/GoogleCloudPlatform/kubernetes/raw/master/logo.pdf) +[PDF format](https://github.com/kubernetes/kubernetes/raw/master/logo.pdf) [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/logo_usage_guidelines.md?pixel)]() diff --git a/third_party/swagger-ui/README.md b/third_party/swagger-ui/README.md index a8f7687335c..ac36ef48a7b 100644 --- a/third_party/swagger-ui/README.md +++ b/third_party/swagger-ui/README.md @@ -15,7 +15,7 @@ https://github.com/swagger-api/swagger-ui#how-to-use-it ## Local Modifications - Updated the url in index.html to "../../swaggerapi" as per instructions at: https://github.com/swagger-api/swagger-ui#how-to-use-it -- Modified swagger-ui.js to list resources and operations in sorted order: https://github.com/GoogleCloudPlatform/kubernetes/pull/3421 +- Modified swagger-ui.js to list resources and operations in sorted order: https://github.com/kubernetes/kubernetes/pull/3421 - Set supportedSubmitMethods: [] in index.html to remove "Try it out" buttons. LICENSE file has been created for compliance purposes.