fix cilium routing and cluster dns
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Successful in 1m0s
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Successful in 1m0s
This commit is contained in:
@@ -8,8 +8,23 @@ k8sServicePort: 6443
|
||||
ipam:
|
||||
mode: kubernetes
|
||||
|
||||
routingMode: tunnel
|
||||
tunnelProtocol: vxlan
|
||||
# k3d nodes share a directly reachable Docker bridge. Native routing avoids
|
||||
# nested VXLAN service paths that can prevent pod access to ClusterIP services.
|
||||
routingMode: native
|
||||
autoDirectNodeRoutes: true
|
||||
# K3s allocates pod addresses from this cluster-wide CIDR. Native routing
|
||||
# requires the CIDR so Cilium can distinguish pod traffic from underlay traffic.
|
||||
ipv4NativeRoutingCIDR: 10.42.0.0/16
|
||||
|
||||
# The k3d nodes run as nested containers on the Flatcar host. eBPF masquerade
|
||||
# keeps return traffic for cross-node service backends inside the Cilium path.
|
||||
bpf:
|
||||
masquerade: true
|
||||
|
||||
# Keep socket load-balancing in the node namespace for the nested k3d profile.
|
||||
# Pod traffic is handled by the eBPF service datapath instead.
|
||||
socketLB:
|
||||
hostNamespaceOnly: true
|
||||
|
||||
hubble:
|
||||
enabled: true
|
||||
@@ -20,4 +35,3 @@ hubble:
|
||||
|
||||
operator:
|
||||
replicas: 1
|
||||
|
||||
|
||||
Reference in New Issue
Block a user