From 78a7a8103f6bf5fb8ed8c83f07396e97d75b8925 Mon Sep 17 00:00:00 2001 From: Oleg Pykhalov Date: Thu, 29 Feb 2024 11:10:26 +0300 Subject: [PATCH] infrastructure: cluster1: cilium: values: Configure. Copy configuration. --- infrastructure/cluster1/cilium/values.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/infrastructure/cluster1/cilium/values.yaml b/infrastructure/cluster1/cilium/values.yaml index 24e7eacba..9b5fdb084 100644 --- a/infrastructure/cluster1/cilium/values.yaml +++ b/infrastructure/cluster1/cilium/values.yaml @@ -7,3 +7,15 @@ cluster: # -- Configure the underlying network MTU to overwrite auto-detected MTU. MTU: 1500 + +# -- Allows to explicitly specify the IPv4 CIDR for native routing. +# When specified, Cilium assumes networking for this CIDR is preconfigured and +# hands traffic destined for that range to the Linux network stack without +# applying any SNAT. +# Generally speaking, specifying a native routing CIDR implies that Cilium can +# depend on the underlying networking stack to route packets to their +# destination. To offer a concrete example, if Cilium is configured to use +# direct routing and the Kubernetes CIDR is included in the native routing CIDR, +# the user must configure the routes to reach pods, either manually or by +# setting the auto-direct-node-routes flag. +ipv4NativeRoutingCIDR: "10.0.0.0/9"