Avoid linking to the master branch of repositories

CONTRIBUTING.md

@@ -26,7 +26,7 @@ Read the following guide if you're interested in contributing to cluster-api.
 We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.
 
 Please fill out either the individual or corporate Contributor License Agreement (CLA). More information about the CLA
-and instructions for signing it [can be found here](https://github.com/kubernetes/community/blob/master/CLA.md).
+and instructions for signing it [can be found here](https://git.k8s.io/community/CLA.md).
 
 ***NOTE***: Only original source code from you and other people that have signed the CLA can be accepted into the
 *repository.
@@ -54,7 +54,7 @@ come up, including gaps in documentation!
         - 🌱 (:seedling:, minor or other)
 
 All changes must be code reviewed. Coding conventions and standards are explained in the official [developer
-docs](https://github.com/kubernetes/community/tree/master/contributors/devel). Expect reviewers to request that you
+docs](https://git.k8s.io/community/contributors/devel). Expect reviewers to request that you
 avoid common [go style mistakes](https://github.com/golang/go/wiki/CodeReviewComments) in your PRs.
 
 ## Triaging E2E test failures
@@ -213,7 +213,7 @@ against the kubernetes/org repo.
 
 However, if you are a member of any of the related Kubernetes GitHub organizations but not of the Kubernetes org, you
 will need explicit sponsorship for your membership request. You can read more about Kubernetes membership and
-sponsorship [here](https://github.com/kubernetes/community/blob/master/community-membership.md).
+sponsorship [here](https://git.k8s.io/community/community-membership.md).
 
 Cluster API maintainers can assign you an issue or pull request by leaving a `/assign <your Github ID>` comment on the
 issue or pull request.

REVIEWING.md

@@ -119,7 +119,7 @@ This makes any change that can impact the Cluster API contract critical and usua
 
 ### Logging
 
-- For CAPI controllers see [Kubernetes logging conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md).
+- For CAPI controllers see [Kubernetes logging conventions](https://git.k8s.io/community/contributors/devel/sig-instrumentation/logging.md).
 - For clusterctl see [clusterctl logging conventions](https://github.com/kubernetes-sigs/cluster-api/blob/master/cmd/clusterctl/log/doc.go).
 
 ### Testing

SECURITY_CONTACTS

@@ -4,7 +4,7 @@
 # to for triaging and handling of incoming issues.
 #
 # The below names agree to abide by the
-# [Embargo Policy](https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/security-release-process.md#embargo-policy)
+# [Embargo Policy](https://git.k8s.io/sig-release/security-release-process-documentation/security-release-process.md#embargo-policy)
 # and will be removed and replaced if they violate that agreement.
 #
 # DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE

VERSIONING.md

@@ -77,7 +77,7 @@ separately.
 Cluster API follows the standard Kubernetes workflow: any PR needs
 `lgtm` and `approved` labels, PRs authors must have signed the CNCF CLA,
 and PRs must pass the tests before being merged.  See [the contributor
-docs](https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#the-testing-and-merge-workflow)
+docs](https://git.k8s.io/community/contributors/guide/pull-requests.md#the-testing-and-merge-workflow)
 for more info.
 
 We use the same priority and kind labels as Kubernetes.  See the labels

cmd/clusterctl/log/doc.go

@@ -21,7 +21,7 @@ that defaults to NullLogger.
 You can set a custom logger by calling log.SetLogger.
 
 NewLogger returns a clusterctl friendly logr.Logger derived from
-https://github.com/kubernetes/klog/blob/master/klogr/klogr.go.
+https://git.k8s.io/klog/klogr/klogr.go.
 
 The logger is designed to print logs to stdout with a formatting that is easy to read for users
 but also simple to parse for identifying specific values.

docs/book/src/developer/e2e.md

@@ -215,7 +215,7 @@ test specs for the most common Cluster API use cases.
 [WaitForClusterToProvision]: https://pkg.go.dev/sigs.k8s.io/cluster-api/test/framework?tab=doc#WaitForClusterToProvision
 [WaitForKubeadmControlPlaneMachinesToExist]: https://pkg.go.dev/sigs.k8s.io/cluster-api/test/framework?tab=doc#WaitForKubeadmControlPlaneMachinesToExist
 [controller-runtime Client]: https://pkg.go.dev/sigs.k8s.io/controller-runtime@v0.5.2/pkg/client?tab=doc#Client
-[boskos]: https://github.com/kubernetes/test-infra/tree/master/boskos
+[boskos]: https://git.k8s.io/test-infra/boskos
 [E2E config file]: https://pkg.go.dev/sigs.k8s.io/cluster-api/test/framework/clusterctl?tab=doc#E2EConfig
 [example E2E config file]: https://github.com/kubernetes-sigs/cluster-api/blob/master/test/e2e/config/docker.yaml
 [NewKindClusterProvider]: https://pkg.go.dev/sigs.k8s.io/cluster-api/test/framework/bootstrap?tab=doc#NewKindClusterProvider

docs/book/src/developer/providers/implementers-guide/configure.md

@@ -56,7 +56,7 @@ patchesStrategicMerge
 ```
 
 [kustomizeyaml]: https://github.com/kubernetes-sigs/kustomize/blob/master/docs/glossary.md#kustomization
-[patch]: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md
+[patch]: https://git.k8s.io/community/contributors/devel/sig-api-machinery/strategic-merge-patch.md
 
 ## Our configuration
 

docs/book/src/reference/glossary.md

@@ -27,7 +27,7 @@ A temporary cluster that is used to provision a Target Management cluster.
 ---
 
 ### CAEP
-Cluster API Enhancement Proposal - patterned after [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/README.md). See [template](https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/proposals/YYYYMMDD-template.md)
+Cluster API Enhancement Proposal - patterned after [KEP](https://git.k8s.io/enhancements/keps/README.md). See [template](https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/proposals/YYYYMMDD-template.md)
 
 ### CAPI
 Core Cluster API

docs/developer/releasing.md

@@ -61,7 +61,7 @@ For version v0.x.y:
 1. Push the tag to the GitHub repository `git push origin v0.x.y`
     1. NB: `origin` should be the name of the remote pointing to `github.com/kubernetes-sigs/cluster-api`
 1. Run `make release` to build artifacts (the image is automatically built by CI)
-1. Follow the [Image Promotion process](https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io#image-promoter) to promote the image from the staging repo to `us.gcr.io/k8s-artifacts-prod/cluster-api`
+1. Follow the [Image Promotion process](https://git.k8s.io/k8s.io/k8s.gcr.io#image-promoter) to promote the image from the staging repo to `us.gcr.io/k8s-artifacts-prod/cluster-api`
 1. Create a release in GitHub based on the tag created above
 1. Release notes can be created by running `make release-notes`, which will generate an output that can be copied to the drafted release in GitHub.
    Pay close attention to the `## :question: Sort these by hand` section, as it contains items that need to be manually sorted.

docs/proposals/20191017-kubeadm-based-control-plane.md

@@ -126,10 +126,10 @@ Non-Goals listed in this document are intended to scope bound the current v1alph
 - To manage etcd clusters in any topology other than stacked etcd (externally managed etcd clusters can still be leveraged).
 - To address disaster recovery constraints, e.g. restoring a control plane from 0 replicas using a filesystem or volume snapshot copy of data persisted in etcd.
 - To support rollbacks, as there is no data store rollback guarantee for Kubernetes. Consumers should perform backups of the cluster prior to performing potentially destructive operations.
-- To mutate the configuration of live, running clusters (e.g. changing api-server flags), as this is the responsibility of the [component configuration working group](https://github.com/kubernetes/community/tree/master/wg-component-standard).
+- To mutate the configuration of live, running clusters (e.g. changing api-server flags), as this is the responsibility of the [component configuration working group](https://git.k8s.io/community/wg-component-standard).
 - To provide configuration of external cloud providers (i.e. the [cloud-controller-manager](https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/)).This is deferred to kubeadm.
 - To provide CNI configuration. This is deferred to external, higher level tooling.
-- To provide the upgrade logic to handle changes to infrastructure (networks, firewalls etc…) that may need to be done to support a control plane on a newer version of Kubernetes (e.g. a cloud controller manager requires updated permissions against infrastructure APIs). We expect the work on [add-on components](https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle#cluster-addons)) to help to resolve some of these issues.
+- To provide the upgrade logic to handle changes to infrastructure (networks, firewalls etc…) that may need to be done to support a control plane on a newer version of Kubernetes (e.g. a cloud controller manager requires updated permissions against infrastructure APIs). We expect the work on [add-on components](https://git.k8s.io/community/sig-cluster-lifecycle#cluster-addons)) to help to resolve some of these issues.
 - To provide automation around the horizontal or vertical scaling of control plane components, especially as etcd places hard performance limits beyond 3 nodes (due to latency).
 - To support upgrades where the infrastructure does not rely on a Load Balancer for access to the API Server.
 - To implement a fully modeled state machine and/or Conditions, a larger effort for Cluster API more broadly is being organized on [this issue](https://github.com/kubernetes-sigs/cluster-api/issues/1658))

docs/scope-and-objectives.md

@@ -81,7 +81,7 @@ We are building a set of Kubernetes cluster management APIs to enable common clu
 
 ## Motivation
 
-Kubernetes has a common set of APIs (see the [Kubernetes API Conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md)) to orchestrate containers regardless of deployment mechanism or cloud provider. Kubernetes also has APIs for handling some infrastructure, like load-balancers, ingress rules, or persistent volumes, but not for creating new machines.
+Kubernetes has a common set of APIs (see the [Kubernetes API Conventions](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md)) to orchestrate containers regardless of deployment mechanism or cloud provider. Kubernetes also has APIs for handling some infrastructure, like load-balancers, ingress rules, or persistent volumes, but not for creating new machines.
 As a result, existing popular deployment mechanisms that manage Kubernetes clusters each have unique APIs and implementations for how to handle lifecycle events like cluster creation or deletion, control plane upgrades, and node upgrades.
 
 

logos/icons/README.md

@@ -1,6 +1,6 @@
 # Cluster API Icons Set
 
-These icons are a way to standardize Cluster API architecture diagrams, building on top of the [Kubernetes Icon Set](https://github.com/kubernetes/community/tree/master/icons). Having uniform architecture diagrams improve understandibility.
+These icons are a way to standardize Cluster API architecture diagrams, building on top of the [Kubernetes Icon Set](https://git.k8s.io/community/icons). Having uniform architecture diagrams improve understandibility.
 
 ## License
 The Kubernetes Icons Set is licensed under a choice of either Apache-2.0