# Azure Kubernetes Service Azure Kubernetes Service (AKS) is a managed Kubernetes service for deploying, managing, and scaling containerized applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to secure Kubernetes in the age of AI workloads DevFeed: [How to secure Kubernetes in the age of AI workloads]() Original publisher: [Read original article]() Author: Mary Branscombe Published: 2026-06-04T16:45:57Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Kubernetes](), [Artificial Intelligence](), [Azure Kubernetes Service](), [networking](), [zero trust networking](), [Access Control](), [Vulnerabilities](), [Azure](), [Secrets Management]() Tags: [access-control](), [ai](), [ai-agents](), [azure](), [azure-kubernetes-service](), [kubernetes](), [microsoft-azure](), [networking](), [post](), [secrets](), [security](), [sponsor-microsoft-azure](), [sponsored-post](), [vulnerabilities](), [zero-trust]() ### AI overview The article examines how AI workloads and agents increase Kubernetes security challenges through unpredictable processes, traffic, tool use, registry access, and shared GPU infrastructure. It discusses a zero-trust approach and describes AKS network-isolated clusters that can bootstrap without public-internet egress by using private endpoints and Azure Container Registry. ### Source excerpt Securing Kubernetes has always been complex -- spanning access control, image vulnerabilities, secrets management, and networking. AI workloads make it The post How to secure Kubernetes in the age of AI workloads appeared first on The New Stack. ## Blog: Falco plugin for collecting AKS audit logs DevFeed: [Blog: Falco plugin for collecting AKS audit logs]() Original publisher: [Read original article]() Published: 2025-03-09T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Azure Kubernetes Service](), [Falco](), [Kubernetes](), [Security](), [threat detection](), [api server](), [Containers](), [Cloud Native Ecosystem](), [Kernel]() Tags: [aks](), [audit](), [auditlogs](), [azure](), [azure-kubernetes-service](), [falco](), [kubernetes](), [logs](), [plugin](), [security](), [threat-detection]() ### AI overview The article introduces a Falco plugin for collecting Azure Kubernetes Service (AKS) audit logs. It explains how Falco uses runtime and Kubernetes data for threat detection and outlines the required Event Hub configuration and storage setup for using the plugin. ### Source excerpt Troubleshooting Kubernetes events is challenging due to the multitude of data sources involved: container logs, Kubernetes events, cloud logs, and more. Among these sources, Kubernetes audit logs are especially valuable for identifying threats, as every action passing through the Kubernetes API server is recorded there. We already provide plugins that let you parse and use Falco to detect threats in audit logs from GKE and EKS clusters. With our latest plugin, you'll now have the same powerful threat detection capabilities for your Azure AKS clusters. What is Falco? Falco is a Cloud Native Computing Foundation project that provides runtime threat detection. Out of the box, Falco examines syscalls to alert you to any suspicious activity. And, since containers share the same kernel as their host, Falco can monitor not only activity on the host but also activity on all of the containers running on that host. Moreover, Falco pulls data from both Kubernetes and the container runtime to add additional context to its alerts. With Falco running on your GKE clusters you can be notified of a wide variety of events, such as: Did someone start a container with high privileges? Has someone shelled into a running container? Has an executable been added to the container after it was deployed? These are just a few examples. Falco has over 80 rules that can be used to make you aware of not only external threats but also when clusters aren't being operated in accordance with industry best practices. What is the AKS audit logs plugin? The AKS audit logs plugin extends Falco's capabilities to Microsoft Azure Kubernetes Service (AKS) clusters, providing you with the same security insights and threat detection Falco already offers for GKE and EKS environments. With this plugin, you can seamlessly integrate AKS audit logs into Falco's event processing pipeline, enabling it to identify anomalies, suspicious activities, and policy violations within your AKS-based workloads. Using AKS audit ## Configuring Azure Kubernetes Service Control Planes and Node Pools DevFeed: [Configuring Azure Kubernetes Service Control Planes and Node Pools]() Original publisher: [Read original article]() Author: Sumit Prasad Published: 2024-12-12T12:53:34Z Content type: tutorial Language: en Sources: [Myntra]() Topics: [Azure Kubernetes Service](), [Kubernetes](), [Azure](), [Containers](), [Orchestration](), [Scalability](), [Architecture & Design](), [DevOps]() Tags: [aks](), [aks-best-practices](), [aks-upgrade](), [architecture](), [azure](), [azure-kubernetes-service](), [best-practices](), [components](), [coredns-scaling](), [devops](), [getting-started](), [guide](), [ingress](), [kubernetes](), [performance-optimization](), [scalability]() ### 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 ## Future-Proof Your AKS Cluster with Strategic IP Address Planning DevFeed: [Future-Proof Your AKS Cluster with Strategic IP Address Planning]() Original publisher: [Read original article]() Author: Sumit Prasad Published: 2024-06-25T09:12:09Z Content type: tutorial Language: en Sources: [Myntra]() Topics: [Azure Kubernetes Service](), [Azure](), [Kubernetes](), [networking](), [configuration](), [Scalability]() Tags: [aks](), [azure](), [azure-kubernetes-service](), [cni](), [configuration](), [container-networking](), [ip-address-planning](), [kubernetes](), [kubernetes-scaling](), [load-balancer](), [networking](), [scalability]() ### AI overview This article explains IP address planning for Azure Kubernetes Service clusters using default Azure CNI networking. It compares static and dynamic IP allocation and describes how pod, node, and internal load balancer scaling affects subnet capacity and resource utilization. ### Source excerpt Scaling Kubernetes efficiently is an art that blends strategic planning with technical expertise. In Azure Kubernetes Service (AKS), mastering the allocation of IP addresses is crucial for ensuring seamless scalability and optimal performance. When configuring an AKS cluster with default Azure CNI networking, it's essential to address the nature of scaling Pods, Nodes, and internal LoadBalancer-type services. This blog delves into the intricate process of IP address planning, explicitly focusing on scaling Pods, Nodes, and Services in an AKS cluster. Discover how thoughtful IP management can prevent bottlenecks, optimize resource utilization, and pave the way for a robust production environment. Image Source: https://kubernetes.io/docs/images/kubernetes-cluster-network.svg We'll talk about two approaches to IP address planning in AKS: Static IP allocation and Dynamic IP allocation. Let us understand a bit about both, and then we will go deeper to understand each approach. Static IP Allocation: Suitable for predictable and stable environments where the maximum number of pods per node is known and does not change frequently. This approach can lead to IP wastage if the number of pods varies. Dynamic IP Allocation: Better for environments with varying workloads and dynamic scaling needs. It helps reduce IP wastage by allocating additional IPs only when necessary, but it requires careful subnet planning with a buffer to accommodate dynamic allocations. Static IP Allocation The default configuration in AKS uses static IP allocation based on the 'maximum number of pods per node' setting, counting all pods created from Deployments, Daemonsets, Statefulsets, or Jobs. The private subnet CIDR specified during node pool configuration assigns IP addresses to Pods, Nodes, and Load balancer type services for an internal network. It is essential to decide the "maximum pods per node" configuration and to have a dedicated subnet CIDR range before creating a node pool. AKS reserves th ## Azure Cache for Redis as Key-Value Store with SpinKube DevFeed: [Azure Cache for Redis as Key-Value Store with SpinKube]() Original publisher: [Read original article]() Author: Thorsten Hans Published: 2024-05-20T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Redis](), [Azure](), [Azure Kubernetes Service](), [Kubernetes]() Tags: [aks](), [apps](), [azure](), [cache](), [how-to](), [key-value-store](), [kubernetes](), [redis]() ### AI overview A tutorial showing how to run Spin Apps on Azure Kubernetes Service (AKS) and use Azure Cache for Redis as a key-value store. ### Source excerpt See how to run Spin Apps on Azure Kubernetes Service (AKS) and use Azure Cache for Redis as Key-Value Store ## Visit Fermyon at Microsoft Build DevFeed: [Visit Fermyon at Microsoft Build]() Original publisher: [Read original article]() Author: Mikkel Mørk Hegnhøj Published: 2024-05-15T12:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Azure Kubernetes Service](), [WebAssembly](), [Microsoft](), [Azure]() Tags: [azure](), [azure-kubernetes-service](), [microsoft](), [webassembly]() ### AI overview Fermyon announces its participation in Microsoft Build in Seattle, featuring demos and sessions on running WebAssembly-powered apps on Azure Kubernetes Service. ### Source excerpt We're at Microsoft Build next week in Seattle, with demos and sessions on running WebAssembly-powered apps on Azure Kubernetes Service. ## WebAssembly in Azure with Azure Kubernetes Service and SpinKube DevFeed: [WebAssembly in Azure with Azure Kubernetes Service and SpinKube]() Original publisher: [Read original article]() Author: Thorsten Hans Published: 2024-04-25T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Azure Kubernetes Service](), [Azure](), [App]() Tags: [app](), [azure](), [azure-kubernetes-service]() ### AI overview A brief tutorial introduction to running a simple Spin App on Azure Kubernetes Service with SpinKube. ### Source excerpt Let's run a simple Spin App on Azure Kubernetes Service with SpinKube. ## What's New in Teleport 11 DevFeed: [What's New in Teleport 11]() Original publisher: [Read original article]() Author: kenneth.dumez@goteleport.com (Kenneth DuMez) Published: 2022-11-09T00:00:00Z Content type: release Language: en Sources: [Teleport]() Topics: [Kubernetes](), [Helm charts](), [Security](), [Amazon EKS](), [Azure Kubernetes Service](), [OpenSSH](), [Protocol (disambiguation)](), [GitHub Actions]() Tags: [aks](), [azure-kubernetes-service](), [github-actions](), [helm-charts](), [new-features](), [overview](), [private-key](), [release](), [security](), [sftp]() ### AI overview An overview of Teleport 11 features, including hardware-backed private keys on Yubikey devices, server-side SFTP support, persistent-storage changes for Helm deployments, and automatic discovery and enrollment of EKS and AKS clusters. ### Source excerpt An overview of all of the new features added into Teleport 11. ## Updated Pluralsight Course - Kubernetes Installation and Configuration Fundamentals DevFeed: [Updated Pluralsight Course - Kubernetes Installation and Configuration Fundamentals]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2021-03-01T19:10:41Z Content type: release Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [Kubernetes](), [Pluralsight](), [Azure Kubernetes Service](), [Containers](), [Cloud]() Tags: [aks](), [cloud](), [container](), [containers](), [kubectl](), [kubernetes](), [pluralsight](), [training](), [yaml]() ### AI overview The article announces an updated Pluralsight course, Kubernetes Installation and Configuration Fundamentals, for IT professionals who design and maintain Kubernetes and container-based solutions. It highlights containerd, cluster configuration files, workload creation, YAML manifests, Kubernetes architecture, installation methods, cloud-managed Kubernetes services, and Azure Kubernetes Service. ### Source excerpt My updated course "Kubernetes Installation and Configuration Fundamentals" is now available on Pluralsight here! If you want to learn about the course, check out the trailer here or if you want to dive right in check it out here! This course targets IT professionals that design and maintain Kubernetes and container based solutions. The course can be used by both the IT pro learning new skills and the system administrator or developer preparing for using Kubernetes both on premises and in the Cloud. ## Memory Settings for Running SQL Server in Kubernetes DevFeed: [Memory Settings for Running SQL Server in Kubernetes]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2019-09-28T15:50:24Z Content type: tutorial Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [Kubernetes](), [sql-server](), [Azure Kubernetes Service](), [Containers]() Tags: [azure](), [azure-kubernetes-service](), [containers](), [deployment](), [kubernetes](), [linux](), [memory](), [performance](), [sql-server](), [yaml]() ### AI overview This tutorial explains why SQL Server workloads running in Kubernetes need memory and resource limits configured in the Pod specification. Using demonstrations on Azure Kubernetes Service, it shows that deploying without resource limits can cause workload failures and Pod termination under load. ### Source excerpt People often ask me what's the number one thing to look out for when running SQL Server on Kubernetes...the answer is memory settings. In this post, we're going to dig into why you need to configure resource limits in your SQL Server's Pod Spec when running SQL Server workloads in Kubernetes. I'm running these demos in Azure Kubernetes Service (AKS), but these concepts apply to any SQL Server environment running in Kubernetes.