Use git.k8s.io for links

.generated_files

@@ -1,7 +1,7 @@
 # Files that should be ignored by tools which do not want to consider generated
 # code.
 #
-# https://github.com/kubernetes/contrib/blob/master/mungegithub/mungers/size.go
+# https://git.k8s.io/contrib/mungegithub/mungers/size.go
 #
 # This file is a series of lines, each of the form:
 #     <type> <name>

.github/PULL_REQUEST_TEMPLATE

@@ -1,6 +1,6 @@
 <!--  Thanks for sending a pull request!  Here are some tips for you:
 - If this is your first contribution, read our Getting Started guide https://github.com/kubernetes/community#your-first-contribution
-- If you are editing SIG information, please follow these instructions: https://github.com/kubernetes/community/tree/master/generator
+- If you are editing SIG information, please follow these instructions: https://git.k8s.io/community/generator
   You will need to follow these steps:
   1. Edit sigs.yaml with your change 
   2. Generate docs with `make generate`. To build docs for one sig, run `make WHAT=sig-apps generate`

CLA.md

@@ -75,6 +75,6 @@ Someone from the CNCF will respond to your ticket to help.
 [Corporation signup]: https://identity.linuxfoundation.org/node/285/organization-signup
 [Individual signup]: https://identity.linuxfoundation.org/projects/cncf
 [git email]: https://help.github.com/articles/setting-your-email-in-git
-[third_party]: https://github.com/kubernetes/kubernetes/tree/master/third_party
-[vendor]: https://github.com/kubernetes/kubernetes/tree/master/vendor
+[third_party]: https://git.k8s.io/kubernetes/third_party
+[vendor]: https://git.k8s.io/kubernetes/vendor
 [documentation]: https://help.github.com/articles/setting-your-commit-email-address-on-github/

CONTRIBUTING.md

@@ -36,4 +36,4 @@ Edits in SIG sub-directories should follow any additional guidelines described
 by the respective SIG leads in the sub-directory's `CONTRIBUTING` file
 (e.g. [sig-cli/CONTRIBUTING](sig-cli/CONTRIBUTING.md)).
 
-Attending a [SIG meeting](https://github.com/kubernetes/community/blob/master/sig-list.md) or posting on their mailing list might be prudent if you want to make extensive contributions.
+Attending a [SIG meeting](/sig-list.md) or posting on their mailing list might be prudent if you want to make extensive contributions.

README.md

@@ -78,8 +78,8 @@ If you want to work on a new idea of relatively small scope:
   1. Submit a [pull request] containing a tested change.
 
 
-[architecture]: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/architecture.md
-[cmd]: https://github.com/kubernetes/kubernetes/tree/master/cmd
+[architecture]: /contributors/design-proposals/architecture/architecture.md
+[cmd]: https://git.k8s.io/kubernetes/cmd
 [CLA]: CLA.md
 [Collaboration Guide]: contributors/devel/collab.md
 [Developer's Guide]: contributors/devel/development.md

communication.md

@@ -77,8 +77,8 @@ Kubernetes is the main focus of CloudNativeCon/KubeCon, held every spring in Eur
 [blog]: http://blog.kubernetes.io
 [calendar.google.com]: https://calendar.google.com/calendar/embed?src=cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com&ctz=America/Los_Angeles
 [CNCF code of conduct]: https://github.com/cncf/foundation/blob/master/code-of-conduct.md
-[communication]: https://github.com/kubernetes/community/blob/master/communication.md
-[community meeting]: https://github.com/kubernetes/community/blob/master/communication.md#weekly-meeting
+[communication]: /communication.md
+[community meeting]: /communication.md#weekly-meeting
 [events]: https://www.cncf.io/events/
 [file an issue]: https://github.com/kubernetes/kubernetes/issues/new
 [Google+]: https://plus.google.com/u/0/b/116512812300813784482/116512812300813784482
@@ -89,7 +89,7 @@ Kubernetes is the main focus of CloudNativeCon/KubeCon, held every spring in Eur
 [kubernetes-users]: https://groups.google.com/forum/#!forum/kubernetes-users
 [kubernetes.slackarchive.io]: http://kubernetes.slackarchive.io
 [kubernetes.slack.com]: http://kubernetes.slack.com
-[Special Interest Group]: https://github.com/kubernetes/community/blob/master/README.md#SIGs
+[Special Interest Group]: /README.md#SIGs
 [slack.k8s.io]: http://slack.k8s.io
 [Stack Overflow]: http://stackoverflow.com/questions/tagged/kubernetes
 [timezone table]: https://www.google.com/search?q=1000+am+in+pst

community-membership.md

@@ -229,7 +229,7 @@ TODO: Determine if this role is outdated and needs to be redefined or merged int
 - Primary reviewer for 20 substantial PRs
 - Reviewed or merged at least 50 PRs
 - Apply to [`kubernetes-maintainers`](https://github.com/orgs/kubernetes/teams/kubernetes-maintainers), with:
-  - A [Champion](https://github.com/kubernetes/community/blob/master/incubator.md#faq) from the existing
+  - A [Champion](/incubator.md#faq) from the existing
     kubernetes-maintainers members
   - A Sponsor from Project Approvers
   - Summary of contributions to the project

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.

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)
 

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 [email protected] to claim one.

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**
 

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?
 

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?

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
 

contributors/design-proposals/api-machinery/add-new-patchStrategy-to-clear-fields-not-present-in-patch.md

@@ -44,7 +44,7 @@ that does not contain a discriminator.
 |---|---|
 | non-inlined non-discriminated union | Yes |
 | non-inlined discriminated union | Yes |
-| inlined union with [patchMergeKey](https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#strategic-merge-patch) only | Yes |
+| inlined union with [patchMergeKey](/contributors/devel/api-conventions.md#strategic-merge-patch) only | Yes |
 | other inlined union | No |
 
 For the inlined union with patchMergeKey, we move the tag to the parent struct's instead of

contributors/design-proposals/api-machinery/admission-control-webhooks.md

@@ -21,7 +21,7 @@ This document proposes a detailed plan for bringing Webhooks to Beta. Highlights
 *   Versioned rather than Internal data sent on hook
 *   Ordering behavior within webhooks, and with other admission phases, is better defined
 
-This plan is compatible with the [original design doc]( https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/admission_control_extension.md).
+This plan is compatible with the [original design doc](/contributors/design-proposals/api-machinery/admission_control_extension.md).
 
 
 # Definitions 
@@ -391,12 +391,12 @@ Specific Use cases:
 
 *   Kubernetes static Admission Controllers
     *   Documented [here](https://kubernetes.io/docs/admin/admission-controllers/)
-    *   Discussed [here](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/admission_control_extension.md)
+    *   Discussed [here](/contributors/design-proposals/api-machinery/admission_control_extension.md)
     *   All are highly reliable.  Most are simple.  No external deps.
     *   Many need update checks.
     *   Can be separated into mutation and validate phases.
 *   OpenShift static Admission Controllers
-    *   Discussed [here](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/admission_control_extension.md)
+    *   Discussed [here](/contributors/design-proposals/api-machinery/admission_control_extension.md)
     *   Similar to Kubernetes ones.
 *   Istio, Case 1: Add Container to all Pods.
     *   Currently uses Initializer but can use Mutating Webhook.
@@ -411,7 +411,7 @@ Specific Use cases:
     *   Simple, can be highly reliable and fast. No external deps.
     *   No current use case for updates.
 
-Good further discussion of use cases [here](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/admission_control_extension.md)
+Good further discussion of use cases [here](/contributors/design-proposals/api-machinery/admission_control_extension.md)
 
 
 ## Details of Porting Admission Controllers