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.

One vital element of cybersecurity is keeping all your IT resources up-to-date. In your Azure Kubernetes Service (AKS), for instance, Microsoft patches your nodes at night. Sometimes, you may not even know it. Sometimes, for the patch to activate, you need to reboot the node. But checking everything manually each time a patch comes out is a hassle.

For a number of reasons, you may want to wipe your Azure subscription clean of all the policies you have. Whether it’s because you’re testing and demo-ing something often, or because the subscription is too old and your working algorithms need resetting. Although it sounds like a hassle, you only need to enter two commands.

It’s time-consuming and, frankly, annoying to browse through various news feeds to be fully hands-on on all the changes and releases. Microsoft knows it, too, so it integrated a feature into Logic Apps Designer that informs you of the updates to where you need them. Choose a period, RSS feed items, mailbox, teams, or twitter, and you’re all set!

For whatever reason, you may want to switch your storage account from your primary region to the secondary one. In Azure Geo-Redundant Storage (GRS), there’s a feature that allows you to perform that action manually. There’s nothing overly complicated to it. The manual failover will take just a few minutes to conclude.

Let’s talk about an issue of having your Kubernetes namespace blocked with terminating status. The problem may arise during an attempt to remove a namespace in Kubernetes. To terminate a namespace properly and avoid this scenario, a certain command in a more updated version of kubectl should be used.

Now that we’ve discussed how to use Azure Kubernetes Service (AKS) and protect its related websites using Application Gateway and Let’s Encrypt, it’s time to perform! You obviously want to ensure that users are having the best experience with your AKS applications, which means that securing high availability whatever their geographic location is key.

Previously, we talked about Azure Kubernetes Service (AKS) and using Application Gateway as an Ingress controller and website application firewall (WAF). Now that we’ve got that out of the way, we should continue to strengthen the security of your AKS-related website by obtaining a digital certificate to enable HTTPS.

The previous article talked about using Azure Kubernetes Service (AKS) to orchestrate containers for your applications. But to use your fresh-out-the-oven apps effectively, you mustn’t forget about tight cybersecurity. Azure Application Gateway is one such service that can help you protect the websites you use for application operation.

Azure Blueprints has been available in preview for more than a year now, but not many people have gotten around to understand its use. It’s a neat tool for creating a “blueprint” of a repeatable set of Azure resources to organize environments quickly. Define your preferences so that routine resources management becomes easier.