Use git.k8s.io for links

7 files changed, 8 insertions, 8 deletions

diff --git a/community/2017-events/05-leadership-summit/announcement.md b/community/2017-events/05-leadership-summit/announcement.md
index dc03cb69..4417a910 100644
--- a/community/2017-events/05-leadership-summit/announcement.md
+++ b/community/2017-events/05-leadership-summit/announcement.md
@@ -1,5 +1,5 @@
 This is an announcement for the 2017 Kubernetes Leadership Summit, which will occur on June 2nd, 2017 in San Jose, CA. 
-This event will be similar to the [Kubernetes Developer's Summit](https://github.com/kubernetes/community/blob/master/community/2016-events/developer-summit-2016/Kubernetes_Dev_Summit.md) in November 
+This event will be similar to the [Kubernetes Developer's Summit](/community/2016-events/developer-summit-2016/Kubernetes_Dev_Summit.md) in November 
 2016, but involving a smaller smaller audience comprised solely of leaders and influencers of the community. These leaders and
 influences include the SIG leads, release managers, and representatives from several companies, including (but not limited to)
 Google, Red Hat, CoreOS, WeaveWorks, Deis, and Mirantis.
diff --git a/community/2017-events/05-leadership-summit/session-notes/0300-0345_CODEORGANIZATION.md b/community/2017-events/05-leadership-summit/session-notes/0300-0345_CODEORGANIZATION.md
index 8328fdbf..a6fa64de 100644
--- a/community/2017-events/05-leadership-summit/session-notes/0300-0345_CODEORGANIZATION.md
+++ b/community/2017-events/05-leadership-summit/session-notes/0300-0345_CODEORGANIZATION.md
@@ -39,7 +39,7 @@ Ideally, code would be divided along lines of ownership, by SIG and subproject,
 Next up:
 * [kubeadm](https://github.com/kubernetes/kubernetes/issues/35314)
 * Federation
-* [cloudprovider](https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/README.md) and [cluster](https://github.com/kubernetes/kubernetes/blob/master/cluster/README.md)
+* [cloudprovider](https://git.k8s.io/kubernetes/pkg/cloudprovider/README.md) and [cluster](https://git.k8s.io/kubernetes/cluster/README.md)
 * Scheduler
 * [Kubelet](https://github.com/kubernetes/kubernetes/issues/444)
 
diff --git a/community/2017-events/12-contributor-summit/ContribSummitInformation.md b/community/2017-events/12-contributor-summit/ContribSummitInformation.md
index b591adfd..7a6df6a3 100644
--- a/community/2017-events/12-contributor-summit/ContribSummitInformation.md
+++ b/community/2017-events/12-contributor-summit/ContribSummitInformation.md
@@ -18,7 +18,7 @@ Times in CST
 - 01:00 pm - Sessions resume  
 - 05:00 pm - Happy Hour onsite  
 
-View the complete session schedule [here](https://github.com/kubernetes/community/blob/master/community/2017-events/12-contributor-summit/schedule.png).  
+View the complete session schedule [here](/community/2017-events/12-contributor-summit/schedule.png).  
 Session schedule will be available onsite in print as well as on TVs.
 
 ## Where:
@@ -41,7 +41,7 @@ Level 3, Meeting Room 4, Meeting Room 6a, Meeting Room 6b - Breakout session roo
 *_Note-Your summit registration is NOT your KubeCon registration. Tickets are almost sold out for KubeCon, please purchase those separately from the [event page](http://events.linuxfoundation.org/events/kubecon-and-cloudnativecon-north-america/attend/register)._
 
 ## Invitations:
-Selected attendees are Kubernetes upstream contributors including SIG members and lottery winners from a [members of standing](https://github.com/kubernetes/community/blob/master/community-membership.md) pool.
+Selected attendees are Kubernetes upstream contributors including SIG members and lottery winners from a [members of standing](/community-membership.md) pool.
 We realize that this is not the best approach now that our community is growing in exponential ways. In 2018, we will be unfolding a new strategy for bringing our contributors together so all voices can be heard.
 
 Invites went out on October 19th. There are ten spots left. Please reach out to parispittman@google.com to claim one.
diff --git a/community/2017-events/12-contributor-summit/dashboard-ux-breakout.md b/community/2017-events/12-contributor-summit/dashboard-ux-breakout.md
index 205a12b5..3dad6fe2 100644
--- a/community/2017-events/12-contributor-summit/dashboard-ux-breakout.md
+++ b/community/2017-events/12-contributor-summit/dashboard-ux-breakout.md
@@ -6,7 +6,7 @@ Kubernetes Dashboard UX breakout session 12.5.17, led by Rahul Dhide ([rahuldhid
 
     * Dashboard [User Types and Use Cases](https://docs.google.com/document/d/1urAlgRP7AbcdsOMQ_piQQ6O1XTDIum_LmOUe8xsC4pE/edit)
 
-    * [SIG UI weekly](https://github.com/kubernetes/community/tree/master/sig-ui)
+    * [SIG UI weekly](/sig-ui)
 
 * **Notes**
 
diff --git a/community/2017-events/12-contributor-summit/feature-roadmap-2018.md b/community/2017-events/12-contributor-summit/feature-roadmap-2018.md
index a59b39b2..d2ae01ac 100644
--- a/community/2017-events/12-contributor-summit/feature-roadmap-2018.md
+++ b/community/2017-events/12-contributor-summit/feature-roadmap-2018.md
@@ -146,7 +146,7 @@ Questions:
 
     * Vision is that writing KEPs, know from them what the roadmap is; can write the blog post based on the value articulated in the KEPs.
 
-    * Right now they are [buried in community repo](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/0000-kep-template.md) 3 levels deep: a lot of great feedback so far. Joe wouldn't object to making it more discoverable.
+    * Right now they are [buried in community repo](/contributors/design-proposals/architecture/0000-kep-template.md) 3 levels deep: a lot of great feedback so far. Joe wouldn't object to making it more discoverable.
 
         * Kep.k8s.io for rendered versions?
 
diff --git a/community/2017-events/12-contributor-summit/kubernetes-client-libraries-open-space.md b/community/2017-events/12-contributor-summit/kubernetes-client-libraries-open-space.md
index a48fb15d..d23327d2 100644
--- a/community/2017-events/12-contributor-summit/kubernetes-client-libraries-open-space.md
+++ b/community/2017-events/12-contributor-summit/kubernetes-client-libraries-open-space.md
@@ -8,7 +8,7 @@ Three high-level topics:
 
 Early shout-out for the [Common LISP client](https://github.com/brendandburns/cl-k8s) :)
 
-Currently Java, Python, .Net, Javascript clients are all silver. Reference to the [badge and capabilities descriptions](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/csi-new-client-library-procedure.md#client-capabilities)
+Currently Java, Python, .Net, Javascript clients are all silver. Reference to the [badge and capabilities descriptions](/contributors/design-proposals/api-machinery/csi-new-client-library-procedure.md#client-capabilities)
 Python still outside the [clients org](https://github.com/kubernetes-client/) - should this move from incubator?
 
 Lots of code in client libraries to handle limitations in OpenAPI 2, some of which is fixed in 3. What is required/should we move to OpenAPI 3?
diff --git a/community/elections/README.md b/community/elections/README.md
index 2b60bbd7..14a1ea3f 100644
--- a/community/elections/README.md
+++ b/community/elections/README.md
@@ -1,6 +1,6 @@
 ## Kubernetes Elections 
 
-This document will outline how to conduct a Kubernetes Steering Committee Election. See the [Steering Committee Charter](https://github.com/kubernetes/steering/blob/master/charter.md) for more information of how the committee decides when to have an election, the method, and the maximal representation. 
+This document will outline how to conduct a Kubernetes Steering Committee Election. See the [Steering Committee Charter](https://git.k8s.io/steering/charter.md) for more information of how the committee decides when to have an election, the method, and the maximal representation. 
 
 ## Steering Committee chooses Election Deadlines and Officers