This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
permalink: https://aka.ms/FTAISVAKS
Many Independent Software Vendors (ISVs) today are developing on the Azure Kubernetes Service (AKS) platform and looking to take advantage of the flexibility that the Kubernetes platform provides to run multiple workloads in a shared cluster environment. There are many benefits to this approach including cost, management, and performance.
However, many customers have concerns around how to run their workloads in a shared Kubernetes environment while ensuring that they maintain a secure and performant runtime environment for their tenants. In this video we'll cover some of the considerations you'll need to take into consideration for your AKS solution as well as some of the Kubernetes primitives that will help you achieve a successful multi-tenant deployment.
For more information on the topics covered in this video please refer to the following docs:
AKS
- Best practices for cluster isolation - Azure Kubernetes Service | Microsoft Docs
- Best practices for scheduler features - Azure Kubernetes Service | Microsoft Docs
- Best practices for managing identity - Azure Kubernetes Service | Microsoft Docs
- Azure Policy Regulatory Compliance controls for Azure Kubernetes Service (AKS) - Azure Kubernetes Se...
- Secure pod traffic with network policy - Azure Kubernetes Service | Microsoft Docs
Kubernetes
- Limit Ranges | Kubernetes
- Resource Quotas | Kubernetes
- Pod Security Policies | Kubernetes
- Taints and Tolerations | Kubernetes
- Pod Priority and Preemption | Kubernetes
- Share a Cluster with Namespaces | Kubernetes
- Using RBAC Authorization | Kubernetes
- Network Policies | Kubernetes
Please let us know in the comments what you think, and if you have any questions!
Also, we'd love it if you spent 60 seconds submitting feedback about these videos! It really counts!
(note: this post is a repost of a video originally posted on April 26, 2021 that was accidentally deleted... sorry for any confusion!)