Lets talk about: Azure Kubernetes Service (AKS)

Editor's Notes

• #5: From The CEO's Desk: Docker’s Moby and LinuxKit- Making Containers Mainstream! (opcito.com) The History of Kubernetes on a Timeline | @RisingStack
• #6: Top 10 Networking Features in Windows Server 2019: #1 Container Networking with Kubernetes | Argon Systems
• #7: Baseline architecture for an Azure Kubernetes Service (AKS) cluster - Azure Architecture Center | Microsoft Docs Networking configuration Cluster compute Identity management Secure data flow Business continuity Operations
• #11: Concepts - Kubernetes basics for Azure Kubernetes Services (AKS) - Azure Kubernetes Service | Microsoft Docs A Kubernetes cluster is divided into two components: The Control plane provides the core Kubernetes services and orchestration of application workloads. Nodes which run your application workloads. The control plane includes the following core Kubernetes components: kube-apiserver - The API server is how the underlying Kubernetes APIs are exposed. This component provides the interaction for management tools, such as kubectl or the Kubernetes dashboard. etcd - To maintain the state of your Kubernetes cluster and configuration, the highly available etcd is a key value store within Kubernetes. kube-scheduler - When you create or scale applications, the Scheduler determines what nodes can run the workload and starts them. kube-controller-manager - The Controller Manager oversees a number of smaller Controllers that perform actions such as replicating pods and handling node operations. Multiplayer Game Server Hosting Using AKS - Azure Gaming | Microsoft Docs
• #12: Multiplayer Game Server Hosting Using ACI - Azure Gaming | Microsoft Docs
• #14: Multiplayer Game Server Hosting Using Azure Service Fabric - Azure Gaming | Microsoft Docs
• #15: This reference implementation demonstrates the recommended starting (baseline) infrastructure architecture for a general purpose AKS cluster. This implementation and document is meant to guide an interdisciplinary team or multiple distinct teams like networking, security and development through the process of getting this secure baseline infrastructure deployed and understanding the components of it. We walk through the deployment here in a rather verbose method to help you understand each component of this cluster, ideally teaching you about each layer and providing you with the knowledge necessary to apply it to your workload.
• #16: The Drone Delivery app The Drone Delivery application is a sample application that consists of several microservices. Because it's a sample, the functionality is simulated, but the APIs and microservices interactions are intended to reflect real-world design patterns. Ingestion service. Receives client requests and buffers them. Scheduler service. Dispatches client requests and manages the delivery workflow. Supervisor service. Monitors the workflow for failures and applies compensating transactions. Account service. Manages user accounts. Third-party Transportation service. Manages third-party transportation options. Drone service. Schedules drones and monitors drones in flight. Package service. Manages packages. Delivery service. Manages deliveries that are scheduled or in-transit. Delivery History service. Stores the history of completed deliveries.
• #18: Azure Kubernetes Service (AKS) solution journey - Azure Architecture Center | Microsoft Docs
• #20: - DevSecOps for K8s, sysdig. Really good overview. Covers app dependency scanning, static code analysis, container image scanning, and how to do this on kubernetes -Notary v2: Supply Chain Security. Notary v1 was s docker project and since then there has been a lot of collaboration around it for v2. It essentially allows you as the container publisher to digitally sign collections and configure trusted publishers. Similar offering in ACR Content Trust and when you are pulling a signed docker image from ACR you are actually using the same library as the Notary CLI uses to validate the signature. Note ACR does not officially support the Notary CLI however but its compatible with some of its APIs -A High-Schooler’s Guide to Kubernetes Network Observability – actually by a highschooler, he is in university now talks about the project kube-netc but also goes through some really good basics of Networking observability in a cluster, K8s cronjobs: does anyone actually use this-Kevin is from Lyft, lots of cronjobs. Getting into some problems around distributed scheduling and pokes holes in the the cronjob object. (1) Stop Writing Operators - Joe Thompson, talks a lot about when to use/not use the operator pattern. Theres beena lot of momentum around the number of k8s operators that have been popping up