# coredns-scaling

Published articles for coredns-scaling.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Configuring Azure Kubernetes Service Control Planes and Node Pools

DevFeed: [Configuring Azure Kubernetes Service Control Planes and Node Pools](<https://devfeed.tech/articles/unlock-aks-potential-master-control-plane-and-node-pools-20141.md>)

Original publisher: [Read original article](<https://medium.com/myntra-engineering/unlock-aks-potential-master-control-plane-and-node-pools-0f7bf2eccb00?source=rss----7484818e9f88---4>)

Author: Sumit Prasad

Published: 2024-12-12T12:53:34Z

Content type: tutorial

Language: en

Sources: [Myntra](<https://devfeed.tech/sources/myntra.md>)

Topics: [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [Containers](<https://devfeed.tech/topics/containers.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [DevOps](<https://devfeed.tech/topics/devops.md>)

Tags: [aks](<https://devfeed.tech/tags/aks.md>), [aks-best-practices](<https://devfeed.tech/tags/aks-best-practices.md>), [aks-upgrade](<https://devfeed.tech/tags/aks-upgrade.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-kubernetes-service](<https://devfeed.tech/tags/azure-kubernetes-service.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [components](<https://devfeed.tech/tags/components.md>), [coredns-scaling](<https://devfeed.tech/tags/coredns-scaling.md>), [devops](<https://devfeed.tech/tags/devops.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [guide](<https://devfeed.tech/tags/guide.md>), [ingress](<https://devfeed.tech/tags/ingress.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [performance-optimization](<https://devfeed.tech/tags/performance-optimization.md>), [scalability](<https://devfeed.tech/tags/scalability.md>)

### AI overview

This guide explains how to configure Azure Kubernetes Service (AKS) for performance and scalability. It describes the managed control plane, worker-node-based node pools, workload separation, and taints used to isolate system, ingress, platform, and application workloads.

### Source excerpt

Introduction In this guide, we'll explore the intricacies of configuring Azure Kubernetes Service (AKS) for optimal performance and scalability. As a fully managed container orchestration service by Microsoft Azure, AKS simplifies deploying, managing, and scaling containerized applications using Kubernetes. Drawing from our extensive experience running AKS at scale, this blog aims to provide practical insights and solutions to common challenges faced by DevOps engineers, system administrators, and Kubernetes enthusiasts. We'll walk you through the AKS setup, offering step-by-step guidance, best practices, and tips from real-world scenarios. From fine-tuning the control plane to optimizing node pools, our goal is to equip you with the knowledge to leverage AKS in production environments fully. Join us as we delve into key considerations, navigate potential pitfalls, and share advanced configurations. Whether you're just getting started with AKS or looking to enhance your existing setup, this blog promises a comprehensive dive into Azure Kubernetes Service, informed by our hands-on experiences and lessons learned. AKS Architecture The AKS control plane, a managed service provided by Azure, oversees the management and orchestration of the Kubernetes cluster. It handles tasks such as scheduling, scaling, and monitoring the cluster. Node pools, or worker nodes, are the virtual machine scale sets that run the containers in the AKS cluster, executing workloads and running applications. Our AKS architecture, illustrated in the diagram below, includes multiple node pools, each dedicated to a specific purpose: System Node Pool: Hosts system-critical pods or add-on services managed by AKS. User Node Pools: Three user node pools are designated for: Platform components Ingress Application pods To ensure each node pool serves its intended purpose, we apply taints during their creation: The system node pool has a taint with the key-value pair CriticalAddonsOnly=true:NoSchedule. Th