replaced master with main for k/k links

Signed-off-by: RinkiyaKeDad <[email protected]>

Author: RinkiyaKeDad

committee-code-of-conduct/governance/onboarding-offboarding.md

@@ -26,7 +26,7 @@ Different actions on this list must be carried out by different members:
 **Who executes:** Carryover members should ensure that outgoing members are removed and incoming members are invited. 
 
 - [ ] Update `kubernetes/community` [`sigs.yaml`](https://github.com/kubernetes/community/blob/master/sigs.yaml) 
-- [ ] Update `kubernetes/k8s.io` [`groups.yaml`](https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml)
+- [ ] Update `kubernetes/k8s.io` [`groups.yaml`](https://github.com/kubernetes/k8s.io/blob/main/groups/groups.yaml)
 
     > **Note:** This file controls access to the mailing list and Google Drive! If you do not update this file, adding people manually (via the UIs) continually revert until this file is updated.
 

communication/moderation.md

@@ -253,7 +253,7 @@ This is the workflow for adding a moderator.
 - Ensure person is enrolled for a future bias training course, this can either
   be provided by the project or their employer.
 
-[[email protected] group]: https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml
+[[email protected] group]: https://github.com/kubernetes/k8s.io/blob/main/groups/groups.yaml
 
 ## References and Resources
 

sig-contributor-experience/README.md

@@ -116,7 +116,7 @@ Manages and controls Github permissions, repos, and groups, including Org Member
 ### k8s.io
 Creates and maintains shortcuts and automation apps running in the k8s.io domain.
 - **Owners:**
-  - [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io/blob/master/OWNERS)
+  - [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io/blob/main/OWNERS)
 ### mentoring
 Oversees and develops programs for helping contributors ascend the contributor ladder, including the New Contributor Workshops, Meet Our Contributors, and other programs.
 - **Owners:**

sig-node/archive/meeting-notes-2020.md

@@ -345,7 +345,7 @@ Total active pull requests: [186](https://github.com/kubernetes/kubernetes/pulls
 
 * [@[ruiwen-zhao](https://github.com/ruiwen-zhao)] [https://github.com/kubernetes/k8s.io/pull/1194](https://github.com/kubernetes/k8s.io/pull/1194) (Nvidia GPU device plugin)
   * GoogleCloudPlatform/container-engine-accelerators has been releasing device plugins through [Kubernetes’ addons](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/device-plugins/nvidia-gpu/daemonset.yaml#L39)
-  * After the [Vanity Domain Flip](https://github.com/kubernetes/k8s.io/blob/master/k8s.gcr.io/Vanity-Domain-Flip.md), the vanity domain (k8s.gcr.io) now points to {asia,eu,us}.gcr.io/k8s-artifacts-prod. The PR above is to create a repo in OSS community so that we can keep releasing the device plugin to the new domain.
+  * After the [Vanity Domain Flip](https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/Vanity-Domain-Flip.md), the vanity domain (k8s.gcr.io) now points to {asia,eu,us}.gcr.io/k8s-artifacts-prod. The PR above is to create a repo in OSS community so that we can keep releasing the device plugin to the new domain.
 * [@xing-yang, @yuxiangqian] ContainerNotifier
   * [enhancement issue](https://github.com/kubernetes/enhancements/issues/1977)
   * working on a KEP based on the doc [here](https://docs.google.com/document/d/1SWSlZoxY5zFjBKFKaATP07s3q02UenSp8R9-yRkCcwg/edit#)

sig-wg-lifecycle.md

@@ -130,4 +130,4 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
 [update meetings]: /communication/calendar-guidelines.md
 [community members]: /community-membership.md
 [mailing-list-guidelines.md]: /communication/mailing-list-guidelines.md
-[[email protected] group]: https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml
+[[email protected] group]: https://github.com/kubernetes/k8s.io/blob/main/groups/groups.yaml

wg-k8s-infra/annual-report-2020.md

@@ -181,7 +181,7 @@ A very rough breakdown of the $109k:
 Our community
 [readme](https://github.com/kubernetes/community/tree/master/wg-k8s-infra) is
 accurate if sparse. The
-[readme](https://github.com/kubernetes/k8s.io/blob/master/README.md) in k8s.io,
+[readme](https://github.com/kubernetes/k8s.io/blob/main/README.md) in k8s.io,
 which houses most of the actual infrastructure, is terse and slightly out of
 date (missing triage party)