kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix some broken links from sig-scalability documents

This commit is contained in:
S Nitesh Singh 2021-08-25 10:46:34 +05:30
parent 225abf58b1
commit e70361c354
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
sig-scalability/configs-and-limits/provider-configs.md
View File

@ -161,4 +161,4 @@ Motivated by many of the issues above, an alternative configuration is reasonabl
CoreOS commentary on etcd sizing.
[Hardware guidelines for administering etcd clusters](https://github.com/etcd-io/website/blob/master/content/docs/v3.4/op-guide/hardware.md)
[Hardware guidelines for administering etcd clusters](https://github.com/etcd-io/website/blob/master/content/en/docs/v3.4/op-guide/hardware.md)

2
sig-scalability/processes/formal-scalability-processes.md
View File

@ -6,7 +6,7 @@ _by Shyam JVS, Google Inc_
## Introduction
Scalability is a very crucial aspect of kubernetes and has allowed many customers to adopt it with confidence. K8s [started scaling to 5000](https://kubernetes.io/blog/2017/03/scalability-updates-in-kubernetes-1.6) nodes beginning from release 1.6. Building and maintaining a performant and scalable system needs conscious efforts from the whole developer community. Lack of solid measures have caused problems (both scalability and release-related) in the past - for e.g during [release-1.7](https://github.com/kubernetes/kubernetes/issues/47344), [release-1.8](https://github.com/kubernetes/kubernetes/issues/53255) and [in general](https://github.com/kubernetes/kubernetes/issues/56062). We need them to ensure that the effort is well-streamlined with proper checks and balances in place. Of course they may evolve over time to suit the community/project’s needs better.
Scalability is a very crucial aspect of kubernetes and has allowed many customers to adopt it with confidence. K8s [started scaling to 5000](https://kubernetes.io/blog/2017/03/scalability-updates-in-kubernetes-1-6) nodes beginning from release 1.6. Building and maintaining a performant and scalable system needs conscious efforts from the whole developer community. Lack of solid measures have caused problems (both scalability and release-related) in the past - for e.g during [release-1.7](https://github.com/kubernetes/kubernetes/issues/47344), [release-1.8](https://github.com/kubernetes/kubernetes/issues/53255) and [in general](https://github.com/kubernetes/kubernetes/issues/56062). We need them to ensure that the effort is well-streamlined with proper checks and balances in place. Of course they may evolve over time to suit the community/project’s needs better.
## Goal

2
sig-scalability/processes/scalability-validation.md
View File

@ -120,7 +120,7 @@ Responsibilities lying with other SIGs/teams as applicable (could be sig-scalabi
[#47344]: https://github.com/kubernetes/kubernetes/issues/47344
[supporting]: http://blog.kubernetes.io/2017/03/scalability-updates-in-kubernetes-1.6.html
[supporting]: http://blog.kubernetes.io/2017/03/scalability-updates-in-kubernetes-1-6
[here]: https://docs.google.com/document/d/15rD6XBtKyvXXifkRAsAVFBqEGApQxDRWM3H1bZSBsKQ
[#47865]: https://github.com/kubernetes/kubernetes/issues/47865
[test_owners.csv]: https://github.com/kubernetes/kubernetes/blob/master/test/test_owners.csv