diff options
| author | Claes Mogren <mogren@amazon.com> | 2018-10-22 14:44:46 -0700 |
|---|---|---|
| committer | Claes Mogren <mogren@amazon.com> | 2018-10-22 15:01:25 -0700 |
| commit | 7c88effff5507ea02b3090660e556cddcd207f4c (patch) | |
| tree | 9c15f556f39d2fcae91fcffc0964977ba69f4362 /sig-scalability/processes | |
| parent | 96cd7b1427130f109ba1199d6c0e48226dccc797 (diff) | |
Fix blog links after migration from blog.kubernetes.io to kubernetes.io/blog
Diffstat (limited to 'sig-scalability/processes')
| -rw-r--r-- | sig-scalability/processes/formal-scalability-processes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sig-scalability/processes/formal-scalability-processes.md b/sig-scalability/processes/formal-scalability-processes.md index 997eec47..c5f51165 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](http://blog.kubernetes.io/2017/03/scalability-updates-in-kubernetes-1.6.html) 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 |