diff options
| author | ramnar <raam.soft@gmail.com> | 2018-11-28 01:37:08 +0530 |
|---|---|---|
| committer | ramnar <raam.soft@gmail.com> | 2018-11-28 01:37:08 +0530 |
| commit | 249a50eb5ec4552b6ff46c5b4c8e4615b945e9d6 (patch) | |
| tree | 667efc93a24bf6e43270d46ce49722095ba2d7ac /sig-cloud-provider/CHARTER.md | |
| parent | 4fc2b6bf79e63b133e54d7f5b3fe40059f6605c3 (diff) | |
Broken Links fix for 2696
FILE: ./sig-cloud-provider/CHARTER.md
[✖] https://github.com/kubernetes/community/blob/master/keps/0002-controller-manager.md
→ Status: 404
[✖] https://github.com/kubernetes/community/blob/master/keps/0002-controller-manager.md#repository-requirements
→ Status: 404
FILE: ./github-management/setting-up-cla-check.md
[✖] https://identity.linuxfoundation.org/lfcla/github/postreceive?group=284&comment=no&target=https://identity.linuxfoundation.org/projects/cncf
→ Status: 404
FILE: ./sig-scalability/blogs/k8s-services-scalability-issues.md
[✖] https://cilium.io/blog/2018/04/17/why-is-the-kernel-community-replacing-iptables)
→ Status: 404
FILE: ./sig-scalability/goals.md
[✖] provider-configs.md → Status: 400 Error: ENOENT: no such file or
directory, access
'/home/jorge/src/kubernetes/community/sig-scalability/provider-configs.md'
Diffstat (limited to 'sig-cloud-provider/CHARTER.md')
| -rw-r--r-- | sig-cloud-provider/CHARTER.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sig-cloud-provider/CHARTER.md b/sig-cloud-provider/CHARTER.md index abe12c4b..47c1a210 100644 --- a/sig-cloud-provider/CHARTER.md +++ b/sig-cloud-provider/CHARTER.md @@ -19,7 +19,7 @@ The Cloud Provider SIG ensures that the Kubernetes ecosystem is evolving in a wa * Developing future functionality in Kubernetes to support use cases common to all providers while also allowing custom and pluggable implementations when required, some examples include but are not limited to: * Extendable node status’ and machine states based on provider * Extendable node address types based on provider - * See also [Cloud Controller Manager KEP](https://github.com/kubernetes/community/blob/master/keps/0002-controller-manager.md) + * See also [Cloud Controller Manager KEP](https://github.com/kubernetes/community/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md) * The collection of user experience reports from Kubernetes operators running on provider subprojects; and the delivery of roadmap information to SIG PM ## Organizational Management @@ -32,7 +32,7 @@ The Cloud Provider SIG ensures that the Kubernetes ecosystem is evolving in a wa ## Subproject Creation Each Kubernetes provider will (eventually) be a subproject under SIG Cloud Provider. To add new sub projects (providers), SIG Cloud Provider will maintain an open list of requirements that must be satisfied. -The current requirements can be seen [here](https://github.com/kubernetes/community/blob/master/keps/0002-controller-manager.md#repository-requirements). Each provider subproject is entitled to create 1..N repositories related to cluster turn up or operation on their platform, subject to technical standards set by SIG Cloud Provider. +The current requirements can be seen [here](https://github.com/kubernetes/community/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md#repository-requirements). Each provider subproject is entitled to create 1..N repositories related to cluster turn up or operation on their platform, subject to technical standards set by SIG Cloud Provider. Creation of a repository SHOULD follow the KEP process to preserve the motivation for the repository and any additional instructions for how other SIGs (e.g SIG Documentation and SIG Release) should interact with the repository Subprojects that fall under SIG Cloud Provider may also be features in Kubernetes that is requested or needed by all, or at least a large majority of providers. The creation process for these subprojects will follow the usual KEP process. |