Tag: Kubernetes
-
An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 3
This is the third and final part of a three-part series about “An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI”. -> https://www.danielstechblog.io/an-experiment-enable-cilium-native-routing-on-azure-kubernetes-service-byocni-part-1/ -> https://www.danielstechblog.io/an-experiment-enable-cilium-native-routing-on-azure-kubernetes-service-byocni-part-2/ We will focus today on how to enable Cilium native routing with Azure Route Server and BGP on Azure Kubernetes Service BYOCNI. Azure Route Server Azure Route…
-
An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 2
This is the second part of a three-part series about “An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI”. -> https://www.danielstechblog.io/an-experiment-enable-cilium-native-routing-on-azure-kubernetes-service-byocni-part-1/ We will focus today on how to enable Cilium native routing with WireGuard Transparent Encryption on Azure Kubernetes Service BYOCNI. Enable Cilium native routing with WireGuard Transparent Encryption In this example,…
-
An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI – Part 1
This is the first part of a three-part series about “An experiment – Enable Cilium native routing on Azure Kubernetes Service BYOCNI”. Cilium supports two routing modes, encapsulation and native routing. Due to its versatility of not depending on the underlying network, the encapsulation, also called tunneling, mode is the default one for most Cilium…
-
Use node initialization taints on Azure Kubernetes Service with Cilium
On an Azure Kubernetes Service cluster with Bring Your Own Container Network Interface (BYOCNI) using Cilium, you could not use Cilium’s agent-not-ready taint functionality. -> https://docs.cilium.io/en/stable/installation/taints/ The reason for that is that the Azure control plane blocks add/remove operations on taints via the Kubernetes API. You have to remove taints via the Azure Kubernetes Service…
-
Cilium’s new Hubble flow policy log field
Cilium in version 1.18 introduced a new useful feature called “policy log field” for Hubble flows. -> https://isovalent.com/blog/post/cilium-1-18/#hubble-flow-policy-log-field This feature provides additional possibilities for further insights/checks on which network policy was applied to a network flow. We have a look at how to configure the policy log field and what a Hubble flow looks like…
-
Restrict access to the IMDS endpoint on Azure Kubernetes Service with Cilium
In today’s blog post, we take a look at restricting access to the Azure IMDS endpoint on an Azure Kubernetes Service (AKS) cluster with Cilium using the BYOCNI approach. The Instance Metadata Service (IMDS) endpoint, also known as short IMDS, can be called directly from every Azure VM or VMSS instance via the following command.…