Monthly Archives: April 2018

Keeping your ACS Engine Kubernetes cluster on Azure up-to-date

It is quite simple to keep a Kubernetes cluster created by ACS Engine on Azure up-to-date, because the master and agent nodes are configured by default to automatically apply security patches on a nightly schedule. But you need a solution like Kured to automatically reboot the agent nodes in the cluster, so the security patches take effect. Rebooting the master nodes is a manual task after all. -> Read more [...]

Keeping your AKS – Managed Kubernetes cluster on Azure up-to-date

It is quite simple to keep an AKS – Managed Kubernetes cluster on Azure up-to-date, because Microsoft automatically applies security patches to the nodes on a nightly schedule as described in the AKS FAQ on the Azure documentation page. -> https://docs.microsoft.com/en-us/azure/aks/faq#are-security-updates-applied-to-aks-agent-nodes But you need a solution like Kured to automatically reboot Read more [...]

Configuring and deploying the container monitoring solution for AKS – Managed Kubernetes on Azure

Running an AKS cluster or containers on Azure does not eliminate the need to monitor your workloads. Looking at Azure it is simple to configure and deploy a monitoring solution for AKS. All what you require to do so are the following Azure components. First, you need an Azure Log Analytics workspace and second, the container monitoring solution for Log Analytics. Log Analytics comes with a free Read more [...]