Merge pull request #1541 from cblecker/link-updates

Fix all the links

8 files changed, 10 insertions, 10 deletions

diff --git a/contributors/design-proposals/node/accelerator-monitoring.md b/contributors/design-proposals/node/accelerator-monitoring.md
index 122a6ffb..984ce656 100644
--- a/contributors/design-proposals/node/accelerator-monitoring.md
+++ b/contributors/design-proposals/node/accelerator-monitoring.md
@@ -83,7 +83,7 @@ From the summary API, they will flow to heapster and stackdriver.
 - Performance/Utilization testing: impact on cAdvisor/kubelet resource usage. Impact on GPU performance when we collect metrics.
 
 ## Alternatives Rejected
-Why collect GPU metrics in cAdvisor? Why not collect them in [device plugins](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/resource-management/device-plugin.md)? The path forward if we collected GPU metrics in device plugin is not clear and may take a lot of time to get finalized.
+Why collect GPU metrics in cAdvisor? Why not collect them in [device plugins](/contributors/design-proposals/resource-management/device-plugin.md)? The path forward if we collected GPU metrics in device plugin is not clear and may take a lot of time to get finalized.
 
 Here’s a rough sketch of how things could work:
 
diff --git a/contributors/design-proposals/node/cpu-manager.md b/contributors/design-proposals/node/cpu-manager.md
index 4d6366d4..2dde3b6f 100644
--- a/contributors/design-proposals/node/cpu-manager.md
+++ b/contributors/design-proposals/node/cpu-manager.md
@@ -418,7 +418,7 @@ func (p *dynamicPolicy) RemoveContainer(s State, containerID string) error {
 [cpuset-files]: http://man7.org/linux/man-pages/man7/cpuset.7.html#FILES
 [ht]: http://www.intel.com/content/www/us/en/architecture-and-technology/hyper-threading/hyper-threading-technology.html
 [hwloc]: https://www.open-mpi.org/projects/hwloc
-[node-allocatable]: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/node-allocatable.md#phase-2---enforce-allocatable-on-pods
+[node-allocatable]: /contributors/design-proposals/node/node-allocatable.md#phase-2---enforce-allocatable-on-pods
 [procfs]: http://man7.org/linux/man-pages/man5/proc.5.html
-[qos]: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/resource-qos.md
+[qos]: /contributors/design-proposals/node/resource-qos.md
 [topo]: http://github.com/intelsdi-x/swan/tree/master/pkg/isolation/topo
diff --git a/contributors/design-proposals/node/kubelet-authorizer.md b/contributors/design-proposals/node/kubelet-authorizer.md
index 065c8aa0..0352ea94 100644
--- a/contributors/design-proposals/node/kubelet-authorizer.md
+++ b/contributors/design-proposals/node/kubelet-authorizer.md
@@ -180,5 +180,5 @@ Future work could further limit a kubelet's API access:
 Features that expand or modify the APIs or objects accessed by the kubelet will need to involve the node authorizer.
 Known features in the design or development stages that might modify kubelet API access are:
 * [Dynamic kubelet configuration](https://github.com/kubernetes/features/issues/281)
-* [Local storage management](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/local-storage-overview.md)
+* [Local storage management](/contributors/design-proposals/storage/local-storage-overview.md)
 * [Bulk watch of secrets/configmaps](https://github.com/kubernetes/community/pull/443)
diff --git a/contributors/design-proposals/node/kubelet-eviction.md b/contributors/design-proposals/node/kubelet-eviction.md
index c777e7c7..a96702cc 100644
--- a/contributors/design-proposals/node/kubelet-eviction.md
+++ b/contributors/design-proposals/node/kubelet-eviction.md
@@ -242,7 +242,7 @@ the `kubelet` will select a subsequent pod.
 ## Eviction Strategy
 
 The `kubelet` will implement an eviction strategy oriented around
-[Priority](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/scheduling/pod-priority-api.md)
+[Priority](/contributors/design-proposals/scheduling/pod-priority-api.md)
 and pod usage relative to requests.  It will target pods that are the lowest
 Priority, and are the largest consumers of the starved resource relative to
 their scheduling request.
diff --git a/contributors/design-proposals/node/kubelet-systemd.md b/contributors/design-proposals/node/kubelet-systemd.md
index 8c69dc8f..cef68d2a 100644
--- a/contributors/design-proposals/node/kubelet-systemd.md
+++ b/contributors/design-proposals/node/kubelet-systemd.md
@@ -135,7 +135,7 @@ The `kubelet` should associate node bootstrapping semantics to the configured
 ### Node allocatable
 
 The proposal makes no changes to the definition as presented here:
-https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/node-allocatable.md
+https://git.k8s.io/kubernetes/docs/proposals/node-allocatable.md
 
 The node will report a set of allocatable compute resources defined as follows:
 
diff --git a/contributors/design-proposals/node/runtime-pod-cache.md b/contributors/design-proposals/node/runtime-pod-cache.md
index 49236ba0..752741f1 100644
--- a/contributors/design-proposals/node/runtime-pod-cache.md
+++ b/contributors/design-proposals/node/runtime-pod-cache.md
@@ -28,7 +28,7 @@ pod cache, we can further improve Kubelet's CPU usage by
     need to inspect containers with no state changes.
 
 ***Don't we already have a [container runtime cache]
-(https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/container/runtime_cache.go)?***
+(https://git.k8s.io/kubernetes/pkg/kubelet/container/runtime_cache.go)?***
 
 The runtime cache is an optimization that reduces the number of `GetPods()`
 calls from the workers. However,
diff --git a/contributors/design-proposals/node/sysctl.md b/contributors/design-proposals/node/sysctl.md
index 5c79a736..8ab61b8c 100644
--- a/contributors/design-proposals/node/sysctl.md
+++ b/contributors/design-proposals/node/sysctl.md
@@ -124,7 +124,7 @@ Some real-world examples for the use of sysctls:
 - a containerized IPv6 routing daemon requires e.g. `/proc/sys/net/ipv6/conf/all/forwarding` and
   `/proc/sys/net/ipv6/conf/all/accept_redirects` (compare
   [docker#4717](https://github.com/docker/docker/issues/4717#issuecomment-98653017))
-- the [nginx ingress controller in kubernetes/contrib](https://github.com/kubernetes/contrib/blob/master/ingress/controllers/nginx/examples/sysctl/change-proc-values-rc.yaml#L80)
+- the [nginx ingress controller in kubernetes/contrib](https://git.k8s.io/contrib/ingress/controllers/nginx/examples/sysctl/change-proc-values-rc.yaml#L80)
   uses a privileged sidekick container to set `net.core.somaxconn` and `net.ipv4.ip_local_port_range`.
 - a huge software-as-a-service provider uses shared memory (`kernel.shm*`) and message queues (`kernel.msg*`) to
   communicate between containers of their web-serving pods, configuring up to 20 GB of shared memory.
@@ -251,7 +251,7 @@ Issues:
 ## Design Alternatives and Considerations
 
 - Each pod has its own network stack that is shared among its containers.
-  A privileged side-kick or init container (compare https://github.com/kubernetes/contrib/blob/master/ingress/controllers/nginx/examples/sysctl/change-proc-values-rc.yaml#L80)
+  A privileged side-kick or init container (compare https://git.k8s.io/contrib/ingress/controllers/nginx/examples/sysctl/change-proc-values-rc.yaml#L80)
   is able to set `net.*` sysctls.
 
   Clearly, this is completely uncontrolled by the kubelet, but is a usable work-around if privileged
diff --git a/contributors/design-proposals/node/troubleshoot-running-pods.md b/contributors/design-proposals/node/troubleshoot-running-pods.md
index 7399e8ef..b72102f3 100644
--- a/contributors/design-proposals/node/troubleshoot-running-pods.md
+++ b/contributors/design-proposals/node/troubleshoot-running-pods.md
@@ -730,7 +730,7 @@ coupling it with container images.
 *   [CRI Tracking Issue](https://issues.k8s.io/28789)
 *   [CRI: expose optional runtime features](https://issues.k8s.io/32803)
 *   [Resource QoS in
-    Kubernetes](https://github.com/kubernetes/kubernetes/blob/master/docs/design/resource-qos.md)
+    Kubernetes](https://git.k8s.io/kubernetes/docs/design/resource-qos.md)
 *   Related Features
     *   [#1615](https://issues.k8s.io/1615) - Shared PID Namespace across
         containers in a pod