Scaling a Multi-Tenant k8s Cluster in a TelcoScaling a Multi-Tenant k8s Cluster in a Telco Pablo Moncada October 28, 2020 About MasMovil group ● 4th telecom company in Spain ● Provides voice and broadband services to +12M customers ● Several0 码力 | 6 页 | 640.05 KB | 1 年前3
Building a Secure and Maintainable PaaSTIP: To change picture:Right click on image > Replace image > Select file 3 Requirements for Scaling Up TIP: To change picture:Right click on image > Replace image > Select file ❏ Secure Network0 码力 | 20 页 | 2.26 MB | 1 年前3
Cilium v1.7 Documentation--cluster eni-cluster -n ng-25560078 -N 2 [ℹ] scaling nodegroup stack "eksctl-test-cluster-nodegroup-ng- 25560078" in cluster eksctl-test-cluster-cluster [ℹ] scaling nodegroup, desired capacity from 0 to 2 --cluster eni-cluster -n ng-25560078 -N 2 [ℹ] scaling nodegroup stack "eksctl-test-cluster-nodegroup-ng- 25560078" in cluster eksctl-test-cluster-cluster [ℹ] scaling nodegroup, desired capacity from 0 to 2 --cluster eni-cluster -n ng-25560078 -N 2 [ℹ] scaling nodegroup stack "eksctl-test-cluster-nodegroup-ng- 25560078" in cluster eksctl-test-cluster-cluster [ℹ] scaling nodegroup, desired capacity from 0 to 20 码力 | 885 页 | 12.41 MB | 1 年前3
Cilium v1.6 Documentation--cluster test-cluster -n ng-25560078 -N 2 [ℹ] scaling nodegroup stack "eksctl-test-cluster-nodegroup-ng- 25560078" in cluster eksctl-test-cluster-cluster [ℹ] scaling nodegroup, desired capacity from 0 to 2 --cluster eni-cluster -n ng-25560078 -N 2 [ℹ] scaling nodegroup stack "eksctl-test-cluster-nodegroup-ng- 25560078" in cluster eksctl-test-cluster-cluster [ℹ] scaling nodegroup, desired capacity from 0 to 20 码力 | 734 页 | 11.45 MB | 1 年前3
Cilium v1.10 Documentationenable the former, run: tuned-adm profile network-latency Set CPU governor to performance The CPU scaling up and down can impact latency tests and lead to sub-optimal performance. To achieve maximum consistent performance. Set the CPU governor to performance: for CPU in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do echo performance > $CPU done Stop irqbalance and pin the NIC interrupts to specific increased with bpf-policy-map-max in the Cilium ConfigMap. The first mark represents the action of scaling up the deployments, the second mark when 50000 pods were in ready state. It is expected to see the0 码力 | 1307 页 | 19.26 MB | 1 年前3
Cilium v1.11 Documentationenable the former, run: tuned-adm profile network-latency Set CPU governor to performance The CPU scaling up and down can impact latency tests and lead to sub-optimal performance. To achieve maximum consistent performance. Set the CPU governor to performance: for CPU in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do echo performance > $CPU done Stop irqbalance and pin the NIC interrupts to specific increased with bpf-policy-map-max in the Cilium ConfigMap. The first mark represents the action of scaling up the deployments, the second mark when 50000 pods were in ready state. It is expected to see the0 码力 | 1373 页 | 19.37 MB | 1 年前3
Cilium v1.5 Documentationto a limita�on in the load-balancing implementa�on, constant churn in the load balancing table by scaling the number of service backends up and down can reduce the maximum number of supported service backends0 码力 | 740 页 | 12.52 MB | 1 年前3
Cilium v1.8 Documentationincrease with bpf-policy-map-max in the Cilium ConfigMap. The first mark represents the action of scaling up the deployments, the second mark when 50000 pods were in ready state. It is expected to see the0 码力 | 1124 页 | 21.33 MB | 1 年前3
Cilium v1.9 Documentationincreased with bpf-policy-map-max in the Cilium ConfigMap. The first mark represents the action of scaling up the deployments, the second mark when 50000 pods were in ready state. It is expected to see the0 码力 | 1263 页 | 18.62 MB | 1 年前3
共 9 条
- 1













