update references to KEP template

committee-steering/governance/sig-governance.md

@@ -157,7 +157,7 @@ Issues impacting multiple subprojects in the SIG should be resolved by either:
 
 [lazy-consensus]: http://en.osswiki.info/concepts/lazy_consensus
 [super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote
-[KEP]: https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md
+[KEP]: https://git.k8s.io/enhancements/keps/YYYYMMDD-kep-template.md
 [sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454
 [OWNERS]: contributors/devel/owners.md
 [Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md

sig-architecture/README.md

@@ -120,7 +120,7 @@ Please see the [Conformance Test Review](https://github.com/kubernetes-sigs/arch
 Develop and drive technical enhancement review process
 
 * [KEP Process](https://github.com/kubernetes/community/blob/master/keps/0001-kubernetes-enhancement-proposal-process.md)
-* [Template](https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md)
+* [Template](https://git.k8s.io/enhancements/keps/YYYYMMDD-kep-template.md)
 
 Please see the [KEP Tracking](https://github.com/kubernetes-sigs/architecture-tracking/projects/2) board to follow the work of this sub-project. Please reach out to folks in the [OWNERS](https://github.com/kubernetes/community/blob/master/keps/OWNERS) file if you are interested in joining this effort.
 

sig-azure/charter.md

@@ -95,6 +95,6 @@ Issues impacting multiple subprojects in the SIG should be resolved by SIG Techn
 
 [lazy-consensus]: http://en.osswiki.info/concepts/lazy_consensus
 [super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote
-[KEP]: https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md
+[KEP]: https://git.k8s.io/enhancements/keps/YYYYMMDD-kep-template.md
 [sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454
 [OWNERS]: /contributors/guide/owners.md

sig-cloud-provider/CHARTER.md

@@ -47,7 +47,7 @@ Subprojects representing Kubernetes features may be retired at any point given a
 ## Technical Processes
 Subprojects (providers) of the SIG MUST use the following processes unless explicitly following alternatives they have defined.
 
-* Proposals will be sent as [KEP](https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md) PRs, and published to the official group mailing list as an announcement
+* Proposals will be sent as [KEP](https://git.k8s.io/enhancements/keps/YYYYMMDD-kep-template.md) PRs, and published to the official group mailing list as an announcement
 * Proposals, once submitted, SHOULD be placed on the next full meeting agenda
 * Decisions within the scope of individual subprojects should be made by lazy consensus by subproject owners, with fallback to majority vote by subproject owners; if a decision can’t be made, it should be escalated to the SIG Chairs
 * Issues impacting multiple subprojects in the SIG should be resolved by consensus of the owners of the involved subprojects; if a decision can’t be made, it should be escalated to the SIG Chairs

sig-release/charter.md

@@ -78,7 +78,7 @@ Additional requirements:
 - [sigs.yaml] must be updated to include subproject information and OWNERS files with subproject chairs
 
 
-[KEP]: /keps/0000-kep-template.md
+[KEP]: https://git.k8s.io/enhancements/keps/YYYYMMDD-kep-template.md
 [Kubernetes Charter README]: /committee-steering/governance/README.md
 [lazy-consensus]: http://communitymgt.wikia.com/wiki/Lazy_consensus
 [sig-governance]: /committee-steering/governance/sig-governance.md