Azure Kubernetes Service (AKS) is incredibly multifaceted. For example, you can test the connectivity of an SQL server that’s using a private endpoint connection to your AKS cluster using a pod. You can even manage SQL databases without deploying a VM or installing SQL Server Management Studio or other software.
Microsoft has recently added a new feature, which is the possibility to issue Kubernetes command-line interface (CLI) commands directly from Azure CLI. This is a serious step forward in the direction of further simplification of Azure workload and routine, which can be appreciated by Azure Kubernetes Services (AKS).
Microsoft has recently added two new features to help with your daily Azure Kubernetes Service (AKS) work. The first feature allows you to schedule maintenance windows every week to minimize workload impact. The second one offers different auto-upgrade variations where you can tweak what’ll happen to your existing version, when, and how.
You may be needing to make a certificate authority rotation or experiencing a crash. In Azure Kubernetes Service (AKS), all pods are assigned the same priority, except the default pods that are created along with AKS. This means all pods will restart randomly. By assigning priority, you can secure that all systems function properly after reboot.
Azure Migrate has recently seen an update to its features. It can now help you move your ASP.NET and Java applications to an Azure Kubernetes Service (AKS) container. Usually, such apps would be hosted on Tomcat/IIS. It would be quite a chore to move them to Kubernetes. However, said new capability makes the process much more streamlined.
Azure Resource Mover is a feature that helps to move your Azure resources from one Azure region to another with ease. The feature also notifies you about relevant dependencies to help prepare your target and source region for proper functionality after moving. This removes the need to exercise the procedure using various windows and services. Everything is done in one place.
Operating VMs can be overwhelming when you’re overseeing an enterprise-class IT environment. Azure Automanage is a new feature that applies Azure best practices configurations to a VM based on its services. Once the VM is onboard, the feature applies the most appropriate configs to it, monitors it for drift, and auto-corrects it in case of deviation.
Azure Kubernetes Service (AKS) recently introduced the ability to view the state of your AKS resources from a GUI. Azure Portal now enables you to view in-depth details of your workloads in real-time. You can view the workload of your deployments, pods, and replica sets, and various other capabilities without digging in the cmdline.
The issue with, for example, employees leaving your company is that they can take the Kube file with them. With that file, they can access your Azure Kubernetes Service (AKS). One way to avoid that is to remove the opportunity of access entirely by renewing certificate authority for the designated AKS cluster.
Normally, the pods within your Azure Kubernetes Service (AKS) communicate freely. Such a situation can compromise your security if met with a certain threat. To avoid that, you can use Azure or Calico Network Policies to restrict communication and allow only a set configuration for communication between your pods to avoid unnecessary cyber threats.
