Month: March 2019
-
Publishing Azure Functions on AKS through the Ambassador API gateway
In my last blog post I introduced you to the Ambassador Kubernetes-native microservices API gateway as an ingress controller running on Azure Kubernetes Service. -> https://www.danielstechblog.io/running-ambassador-api-gateway-on-azure-kubernetes-service/ Today I would like to show you how to publish an Azure Function running on Kubernetes through the Ambassador API gateway. It is nothing special compared to a web…
-
Running Ambassador API gateway on Azure Kubernetes Service
Lately I was playing around with the Ambassador Kubernetes-native microservices API gateway as an ingress controller on Azure Kubernetes Service. -> https://www.getambassador.io/ Ambassador is based on the popular L7 proxy Envoy by Lyft. Beside the API gateway capabilities, you can use Ambassador just as an ingress controller for publishing your container applications to the outside…
-
Azure Kubernetes Service cluster autoscaler configurations
Currently you have two options on Azure Kubernetes Service to run the cluster autoscaler. The first one is the integrated solution on the managed master control plane side. This one is in preview and only available when using the AKS VMSS preview. You can configure AKS during the creation process to use the cluster autoscaler…
-
Updating the base image of an VMSS aks-engine cluster
In mid-February was a CVE for runc published and immediately patched on the major cloud provider platforms. -> https://seclists.org/oss-sec/2019/q1/119 -> https://kubernetes.io/blog/2019/02/11/runc-and-cve-2019-5736/ -> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736 As an example if you were running an Azure Kubernetes Service cluster with Kubernetes version 1.12.4, you just needed to upgrade the cluster to version 1.12.5 to have all agent nodes patched…