Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the support of the default CNI of GKE by Kuma CNI #2154

Open
jijiechen opened this issue Jan 16, 2025 · 0 comments
Open

Document the support of the default CNI of GKE by Kuma CNI #2154

jijiechen opened this issue Jan 16, 2025 · 0 comments
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@jijiechen
Copy link
Member

Description

On GKE clusters, our docs says that the users must have network policy enabled to use Kuma CNI.

Page location: https://kuma.io/docs/2.9.x/production/dp-config/cni/#configure-the-kuma-cni

This is actually not requried according to a manual verification: the default CNI on GKE standard clusters have similar CNI configurations to other CNI implementations on GKE (Calico and Cilium), the only difference is file name of the conflist.

The default file name of the conflist is 10-containerd-net.conflist

@Icarus9913 and I have tested the following installation on a GKE standard cluster and Kuma CNI worked well and demo app pod ran successfully:

./kuma-2.9.0/bin/kumactl install control-plane \
  --set "kuma.cni.enabled=true" \
  --set "kuma.cni.chained=true" \
  --set "kuma.cni.netDir=/etc/cni/net.d" \
  --set "kuma.cni.binDir=/home/kubernetes/bin" \
  --set "kuma.cni.confName=10-containerd-net.conflist" \
  | kubectl apply -f -
@jijiechen jijiechen added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Jan 16, 2025
@lukidzi lukidzi added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

2 participants