180 points by containerwiz 1 year ago flag hide 10 comments
k8suser 1 year ago next
Great post! We've been using Kubernetes for a while and have faced similar challenges. Curious to know more about the specific changes you made to improve performance.
devopspro 1 year ago next
We primarily focused on optimizing resource allocation, autoscaling, and networking. We also adopted some best practices around container images and resource utilization.
k8suser 1 year ago next
How did you optimize resource allocation? We've struggled with that in the past.
devopspro 1 year ago next
We took advantage of Kubernetes' built-in features, such as namespace resource quotas, pod priority and preemption, and resource requests and limits for containers. This allowed us to set and enforce usage limits for various components, reducing competition for resources and improving overall performance.
sysadminjim 1 year ago prev next
Thanks for sharing! Did you encounter any challenges implementing autoscaling?
devopspro 1 year ago next
Yes, we faced a few. Autoscaling can be complex, since it involves considerations for both horizontal scaling (adding/removing containers in a pod) and vertical scaling (adding/removing pods in a deployment). You need to balance resource availability with response time and potential costs. Our team worked closely with the Dev and Infrastructure teams to monitor application performance and ensure successful autoscaling.
orchestrationqueen 1 year ago prev next
I assume you used the Kubernetes horizontal pod autoscaler (HPA) for horizontal scaling. How about vertical scaling?
devopspro 1 year ago next
That's correct, we used HPA for horizontal scaling. For vertical scaling, we used the Kubernetes cluster autoscaler (KCA). It makes decisions based on resource availability and use case requirements and provides well-performing solutions for increasing and decreasing the cluster size. It also helps in reducing the costs and increasing the profit margins.
containerman 1 year ago prev next
Could you share more on the networking front? We experience some latency issues.
devopspro 1 year ago next
Sure! We saw latency issues as well and focused on optimizing our CNI (container network interface). We adopted the Calico plugin and used a mix of L2 and L3 networking to improve traffic management, reduce latency, and improve security. We also took steps to guarantee pod-to-pod communication and network policy enforcement.