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-scalability | |
| 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-scalability')
| -rw-r--r-- | sig-scalability/blogs/k8s-services-scalability-issues.md | 2 | ||||
| -rw-r--r-- | sig-scalability/goals.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/sig-scalability/blogs/k8s-services-scalability-issues.md b/sig-scalability/blogs/k8s-services-scalability-issues.md index 422fc42a..e67152a3 100644 --- a/sig-scalability/blogs/k8s-services-scalability-issues.md +++ b/sig-scalability/blogs/k8s-services-scalability-issues.md @@ -21,7 +21,7 @@ Iptables can be slow in packet processing when a large number of services exist. - Moving from iptables to IPVS may help here if that works stably. We have the IPVS alternative [implemented](https://github.com/kubernetes/kubernetes/pull/46580), but it still hasn’t gone to GA. - For a long time the official kernel upstream answer for this issue was that nftables was going to solve all iptables-related scalability problems (both with packet processing and with rule changes), and there's now an out-of-tree nftables kube-proxy backend too ([#62720](https://github.com/kubernetes/kubernetes/issues/62720)). -- There's also an alternative plan to fix the packet processing speed problems by rewriting iptables to use eBPF inside the kernel (see - https://cilium.io/blog/2018/04/17/why-is-the-kernel-community-replacing-iptables). +- There's also an alternative plan to fix the packet processing speed problems by rewriting iptables to use eBPF inside the kernel (see - https://cilium.io/blog/2018/04/17/why-is-the-kernel-community-replacing-iptables ). ## Slow/failing iptables-restore operations when large number of rules exist diff --git a/sig-scalability/goals.md b/sig-scalability/goals.md index 1f497759..10bd51dd 100644 --- a/sig-scalability/goals.md +++ b/sig-scalability/goals.md @@ -72,7 +72,7 @@ NOTES: ## Control Plane Configurations for Testing -Configuration of the control plane for cluster testing varies by provider, and there are multiple reasonable configurations. Discussion and guideline of control plane configuration options and standards are documented [here](provider-configs.md). +Configuration of the control plane for cluster testing varies by provider, and there are multiple reasonable configurations. Discussion and guideline of control plane configuration options and standards are documented [here](configs-and-limits/provider-configs.md). ## Open Questions |