diff options
| -rw-r--r-- | sig-scalability/configs-and-limits/provider-configs.md | 2 | ||||
| -rw-r--r-- | sig-scalability/processes/formal-scalability-processes.md | 2 | ||||
| -rw-r--r-- | sig-scalability/processes/scalability-validation.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/sig-scalability/configs-and-limits/provider-configs.md b/sig-scalability/configs-and-limits/provider-configs.md index 9931393d..b763fc57 100644 --- a/sig-scalability/configs-and-limits/provider-configs.md +++ b/sig-scalability/configs-and-limits/provider-configs.md @@ -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) diff --git a/sig-scalability/processes/formal-scalability-processes.md b/sig-scalability/processes/formal-scalability-processes.md index d215d01c..d87b406c 100644 --- a/sig-scalability/processes/formal-scalability-processes.md +++ b/sig-scalability/processes/formal-scalability-processes.md @@ -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 diff --git a/sig-scalability/processes/scalability-validation.md b/sig-scalability/processes/scalability-validation.md index 2bcb80ca..6a9c9a54 100644 --- a/sig-scalability/processes/scalability-validation.md +++ b/sig-scalability/processes/scalability-validation.md @@ -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 |