cilium/cilium-cliPublic

NotificationsYou must be signed in to change notification settings
Fork211
Star465

CLI to install, manage & troubleshoot Kubernetes clusters running Cilium

License

Apache-2.0 license

465 stars 211 forks Branches Tags Activity

Star

Notifications

You must be signed in to change notification settings

Branches Tags

Folders and files

Name		Name	Last commit message	Last commit date
Latest commit History 2,831 Commits
.github		.github
cmd/cilium		cmd/cilium
vendor		vendor
.gitignore		.gitignore
.golangci.yml		.golangci.yml
CODEOWNERS		CODEOWNERS
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
RELEASE.md		RELEASE.md
SECURITY.md		SECURITY.md
action.yaml		action.yaml
go.mod		go.mod
go.sum		go.sum
stable.txt		stable.txt

Repository files navigation

Cilium CLI

Installation

To build and install, use theinstall target:

make install

You may set theBINDIR environment variable to install the binary in aspecific location instead of/usr/local/bin, e.g.

BINDIR=~/.local/bin make install

Alternatively, to install the latest binary release:

CILIUM_CLI_VERSION=$(curl -s https://raw.githubusercontent.com/cilium/cilium-cli/main/stable.txt)GOOS=$(go env GOOS)GOARCH=$(go env GOARCH)curl -L --remote-name-all https://github.com/cilium/cilium-cli/releases/download/${CILIUM_CLI_VERSION}/cilium-${GOOS}-${GOARCH}.tar.gz{,.sha256sum}sha256sum --check cilium-${GOOS}-${GOARCH}.tar.gz.sha256sumsudo tar -C /usr/local/bin -xzvf cilium-${GOOS}-${GOARCH}.tar.gzrm cilium-${GOOS}-${GOARCH}.tar.gz{,.sha256sum}

Seehttps://github.com/cilium/cilium-cli/releases for supportedGOOS/GOARCHbinary releases.

Releases

Release	Maintained	Compatible Cilium Versions
v0.18.2	Yes	Cilium 1.15 and newer

Capabilities

Install Cilium

To install Cilium while automatically detected:

cilium install🔮 Auto-detected Kubernetes kind: minikube✨ Running "minikube" validation checks✅ Detected minikube version "1.5.2"ℹ️  Cilium version not set, using default version "v1.9.1"🔮 Auto-detected cluster name: minikube🔑 Found existing CA in secret cilium-ca🔑 Generating certificates for Hubble...🚀 Creating service accounts...🚀 Creating cluster roles...🚀 Creating ConfigMap...🚀 Creating agent DaemonSet...🚀 Creating operator Deployment...

Supported Environments

minikube
kind
EKS
self-managed
GKE
AKS BYOCNI
k3s
Rancher

Cluster Context Management

cilium contextContext: minikubeCluster: minikubeAuth: minikubeHost: https://192.168.64.25:8443TLS server name:CA path: /Users/tgraf/.minikube/ca.crt

Hubble

cilium hubble enable🔑 Generating certificates for Relay...✨ Deploying Relay...

Status

cilium status    /¯¯\ /¯¯\__/¯¯\    Cilium:             OK \__/¯¯\__/    Operator:           OK /¯¯\__/¯¯\    Envoy DaemonSet:    OK \__/¯¯\__/    Hubble Relay:       OK    \__/       ClusterMesh:        disabledDaemonSet         cilium             Desired: 1, Ready: 1/1, Available: 1/1DaemonSet         cilium-envoy       Desired: 1, Ready: 1/1, Available: 1/1Deployment        cilium-operator    Desired: 1, Ready: 1/1, Available: 1/1Deployment        hubble-relay       Desired: 1, Ready: 1/1, Available: 1/1Containers:       cilium             Running: 1                  cilium-envoy       Running: 1                  cilium-operator    Running: 1                  hubble-relay       Running: 1Image versions    cilium             quay.io/cilium/cilium:v1.9.1: 1                  cilium-envoy       quay.io/cilium/cilium-envoy:v1.25.5-37a98693f069413c82bef1724dd75dcf1b564fd9@sha256:d10841c9cc5b0822eeca4e3654929418b6424c978fd818868b429023f6cc215d: 1                  cilium-operator    quay.io/cilium/operator-generic:v1.9.1: 1                  hubble-relay       quay.io/cilium/hubble-relay:v1.9.1: 1

Connectivity Check

cilium connectivity test --single-node⌛ Waiting for deployments to become ready🔭 Enabling Hubble telescope...⚠️  Unable to contact Hubble Relay: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp [::1]:4245: connect: connection refused"⚠️  Did you enable and expose Hubble + Relay?ℹ️  You can export Relay with a port-forward: kubectl port-forward -n kube-system deployment/hubble-relay 4245:4245ℹ️  Disabling Hubble telescope and flow validation...-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to pod cilium-test/echo-same-node-7f877bbf9-p2xg8...-------------------------------------------------------------------------------------------✅ client pod client-9f579495f-b2pcq was able to communicate with echo pod echo-same-node-7f877bbf9-p2xg8 (10.0.0.166)-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to outside of cluster...-------------------------------------------------------------------------------------------✅ client pod client-9f579495f-b2pcq was able to communicate with cilium.io-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to local host...-------------------------------------------------------------------------------------------✅ client pod client-9f579495f-b2pcq was able to communicate with local host-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to service echo-same-node...-------------------------------------------------------------------------------------------✅ client pod client-9f579495f-b2pcq was able to communicate with service echo-same-node

With Flow Validation

cilium hubble port-forward&cilium connectivity test --single-node⌛ Waiting for deployments to become ready🔭 Enabling Hubble telescope...Handling connection for 4245ℹ️  Hubble is OK, flows: 405/4096-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to pod cilium-test/echo-same-node-7f877bbf9-p2xg8...-------------------------------------------------------------------------------------------📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:Jan  6 13:41:17.739: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: SYN)Jan  6 13:41:17.739: 10.0.0.166:8080 -> 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: SYN, ACK)Jan  6 13:41:17.739: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)Jan  6 13:41:17.739: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:17.755: 10.0.0.166:8080 -> 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:17.756: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, FIN)Jan  6 13:41:17.757: 10.0.0.166:8080 -> 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, FIN)Jan  6 13:41:17.757: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)📄 Flow logs of pod cilium-test/echo-same-node-7f877bbf9-p2xg8:Jan  6 13:41:17.739: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: SYN)Jan  6 13:41:17.739: 10.0.0.166:8080 -> 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: SYN, ACK)Jan  6 13:41:17.739: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)Jan  6 13:41:17.739: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:17.755: 10.0.0.166:8080 -> 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:17.756: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, FIN)Jan  6 13:41:17.757: 10.0.0.166:8080 -> 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, FIN)Jan  6 13:41:17.757: 10.0.0.11:43876 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)✅ client pod client-9f579495f-b2pcq was able to communicate with echo pod echo-same-node-7f877bbf9-p2xg8 (10.0.0.166)-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to outside of cluster...-------------------------------------------------------------------------------------------❌ Found RST in pod cilium-test/client-9f579495f-b2pcq❌ FIN not found in pod cilium-test/client-9f579495f-b2pcq📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:Jan  6 13:41:22.025: 10.0.0.11:55334 -> 10.0.0.243:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.025: 10.0.0.11:55334 -> 10.0.0.243:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.027: 10.0.0.243:53 -> 10.0.0.11:55334 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.028: 10.0.0.243:53 -> 10.0.0.11:55334 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.028: 10.0.0.11:56466 -> 10.0.0.104:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.028: 10.0.0.11:56466 -> 10.0.0.104:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.029: 10.0.0.104:53 -> 10.0.0.11:56466 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.029: 10.0.0.104:53 -> 10.0.0.11:56466 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.030: 10.0.0.11:57691 -> 10.0.0.243:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.030: 10.0.0.243:53 -> 10.0.0.11:57691 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.030: 10.0.0.11:57691 -> 10.0.0.243:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.031: 10.0.0.243:53 -> 10.0.0.11:57691 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.031: 10.0.0.11:52849 -> 10.0.0.104:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.032: 10.0.0.104:53 -> 10.0.0.11:52849 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.033: 10.0.0.11:52849 -> 10.0.0.104:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.037: 10.0.0.104:53 -> 10.0.0.11:52849 to-endpoint FORWARDED (UDP)Jan  6 13:41:22.038: 10.0.0.11:45040 -> 172.217.168.46:443 to-stack FORWARDED (TCP Flags: SYN)Jan  6 13:41:22.041: 172.217.168.46:443 -> 10.0.0.11:45040 to-endpoint FORWARDED (TCP Flags: SYN, ACK)Jan  6 13:41:22.041: 10.0.0.11:45040 -> 172.217.168.46:443 to-stack FORWARDED (TCP Flags: ACK)Jan  6 13:41:22.059: 10.0.0.11:45040 -> 172.217.168.46:443 to-stack FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:22.073: 172.217.168.46:443 -> 10.0.0.11:45040 to-endpoint FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:22.096: 10.0.0.11:45040 -> 172.217.168.46:443 to-stack FORWARDED (TCP Flags: ACK, RST)Jan  6 13:41:22.097: 172.217.168.46:443 -> 10.0.0.11:45040 to-endpoint FORWARDED (TCP Flags: ACK, FIN)Jan  6 13:41:22.097: 10.0.0.11:45040 -> 172.217.168.46:443 to-stack FORWARDED (TCP Flags: RST)✅ client pod client-9f579495f-b2pcq was able to communicate with cilium.io-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to local host...-------------------------------------------------------------------------------------------📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:Jan  6 13:41:25.305: 10.0.0.11 -> 192.168.64.25 to-stack FORWARDED (ICMPv4 EchoRequest)Jan  6 13:41:25.305: 192.168.64.25 -> 10.0.0.11 to-endpoint FORWARDED (ICMPv4 EchoReply)✅ client pod client-9f579495f-b2pcq was able to communicate with local host-------------------------------------------------------------------------------------------🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to service echo-same-node...-------------------------------------------------------------------------------------------📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:Jan  6 13:41:30.499: 10.0.0.11:39559 -> 10.0.0.104:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:30.499: 10.0.0.11:39559 -> 10.0.0.104:53 to-endpoint FORWARDED (UDP)Jan  6 13:41:30.500: 10.0.0.104:53 -> 10.0.0.11:39559 to-endpoint FORWARDED (UDP)Jan  6 13:41:30.500: 10.0.0.104:53 -> 10.0.0.11:39559 to-endpoint FORWARDED (UDP)Jan  6 13:41:30.503: 10.0.0.11:59414 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: SYN)Jan  6 13:41:30.503: 10.0.0.166:8080 -> 10.0.0.11:59414 to-endpoint FORWARDED (TCP Flags: SYN, ACK)Jan  6 13:41:30.503: 10.0.0.11:59414 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)Jan  6 13:41:30.503: 10.0.0.11:59414 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:30.505: 10.0.0.166:8080 -> 10.0.0.11:59414 to-endpoint FORWARDED (TCP Flags: ACK, PSH)Jan  6 13:41:30.509: 10.0.0.11:59414 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, FIN)Jan  6 13:41:30.509: 10.0.0.166:8080 -> 10.0.0.11:59414 to-endpoint FORWARDED (TCP Flags: ACK, FIN)Jan  6 13:41:30.509: 10.0.0.11:59414 -> 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)✅ client pod client-9f579495f-b2pcq was able to communicate with service echo-same-node

Network Performance test

cilium connectivity perf🔥 Network Performance Test Summary:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------📋 Scenario        | Node       | Test            | Duration        | Min             | Mean            | Max             | P50             | P90             | P99             | Transaction rate OP/s--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------📋 pod-to-pod      | same-node  | TCP_RR          | 1s              | 16µs            | 32.39µs         | 1.567ms         | 20µs            | 52µs            | 97µs            | 30696.13📋 pod-to-pod      | same-node  | UDP_RR          | 1s              | 14µs            | 29.86µs         | 4.41ms          | 17µs            | 47µs            | 97µs            | 33251.51📋 pod-to-pod      | same-node  | TCP_CRR         | 1s              | 290µs           | 512.1µs         | 13.413ms        | 467µs           | 626µs           | 980µs           | 1949.69📋 pod-to-pod      | other-node | TCP_RR          | 1s              | 350µs           | 692.85µs        | 3.543ms         | 631µs           | 1.001ms         | 1.483ms         | 1438.69📋 pod-to-pod      | other-node | UDP_RR          | 1s              | 312µs           | 865.83µs        | 8.731ms         | 605µs           | 1.444ms         | 6ms             | 1150.79📋 pod-to-pod      | other-node | TCP_CRR         | 1s              | 959µs           | 2.15805ms       | 7.677ms         | 1.555ms         | 5.425ms         | 7.133ms         | 461.78---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------📋 Scenario        | Node       | Test            | Duration        | Throughput Mb/s-------------------------------------------------------------------------------------📋 pod-to-pod      | same-node  | TCP_STREAM      | 1s              | 631.58📋 pod-to-pod      | same-node  | UDP_STREAM      | 1s              | 458.66📋 pod-to-pod      | other-node | TCP_STREAM      | 1s              | 411.43📋 pod-to-pod      | other-node | UDP_STREAM      | 1s              | 144.44-------------------------------------------------------------------------------------

ClusterMesh

Install Cilium & enable ClusterMesh in Cluster 1

cilium install --set=cluster.id=1🔮 Auto-detected Kubernetes kind: GKEℹ️  Cilium version not set, using default version "v1.9.1"🔮 Auto-detected cluster name: gke-cilium-dev-us-west2-a-tgraf-cluster1✅ Detected GKE native routing CIDR: 10.52.0.0/14🚀 Creating resource quotas...🔑 Found existing CA in secret cilium-ca🔑 Generating certificates for Hubble...🚀 Creating service accounts...🚀 Creating cluster roles...🚀 Creating ConfigMap...🚀 Creating GKE Node Init DaemonSet...🚀 Creating agent DaemonSet...🚀 Creating operator Deployment...cilium clustermesh enable✨ Validating cluster configuration...✅ Valid cluster identification found: name="gke-cilium-dev-us-west2-a-tgraf-cluster1"🔑 Found existing CA in secret cilium-ca🔑 Generating certificates for ClusterMesh...✨ Deploying clustermesh-apiserver...🔮 Auto-exposing service within GCP VPC (cloud.google.com/load-balancer-type=internal)

Install Cilium in Cluster 2

cilium install --context gke_cilium-dev_us-west2-a_tgraf-cluster2 --set=cluster.id=2🔮 Auto-detected Kubernetes kind: GKEℹ️  Cilium version not set, using default version "v1.9.1"🔮 Auto-detected cluster name: gke-cilium-dev-us-west2-a-tgraf-cluster2✅ Detected GKE native routing CIDR: 10.4.0.0/14🚀 Creating resource quotas...🔑 Found existing CA in secret cilium-ca🔑 Generating certificates for Hubble...🚀 Creating service accounts...🚀 Creating cluster roles...🚀 Creating ConfigMap...🚀 Creating GKE Node Init DaemonSet...🚀 Creating agent DaemonSet...🚀 Creating operator Deployment...cilium clustermesh enable --context gke_cilium-dev_us-west2-a_tgraf-cluster2✨ Validating cluster configuration...✅ Valid cluster identification found: name="gke-cilium-dev-us-west2-a-tgraf-cluster2"🔑 Found existing CA in secret cilium-ca🔑 Generating certificates for ClusterMesh...✨ Deploying clustermesh-apiserver...🔮 Auto-exposing service within GCP VPC (cloud.google.com/load-balancer-type=internal)

Connect Clusters

cilium clustermesh connect --destination-context gke_cilium-dev_us-west2-a_tgraf-cluster2✨ Extracting access information of cluster gke-cilium-dev-us-west2-a-tgraf-cluster2...🔑 Extracting secrets from cluster gke-cilium-dev-us-west2-a-tgraf-cluster2...ℹ️  Found ClusterMesh service IPs: [10.168.15.209]✨ Extracting access information of cluster gke-cilium-dev-us-west2-a-tgraf-cluster1...🔑 Extracting secrets from cluster gke-cilium-dev-us-west2-a-tgraf-cluster1...ℹ️  Found ClusterMesh service IPs: [10.168.15.208]✨ Connecting cluster gke_cilium-dev_us-west2-a_tgraf-cluster1 -> gke_cilium-dev_us-west2-a_tgraf-cluster2...🔑 Patching existing secret cilium-clustermesh...✨ Patching DaemonSet with IP aliases cilium-clustermesh...✨ Connecting cluster gke_cilium-dev_us-west2-a_tgraf-cluster2 -> gke_cilium-dev_us-west2-a_tgraf-cluster1...🔑 Patching existing secret cilium-clustermesh...✨ Patching DaemonSet with IP aliases cilium-clustermesh...

Encryption

Install a Cilium in a cluster and enable encryption with IPsec

cilium install --encryption=ipsec🔮 Auto-detected Kubernetes kind: kind✨ Running "kind" validation checks✅ Detected kind version "0.9.0"ℹ️  Cilium version not set, using default version "v1.9.2"🔮 Auto-detected cluster name: kind-chart-testing🔮 Auto-detected IPAM mode: kubernetes🔑 Found existing CA in secret cilium-ca🔑 Generating certificates for Hubble...🚀 Creating Service accounts...🚀 Creating Cluster roles...🔑 Generated encryption secret cilium-ipsec-keys🚀 Creating ConfigMap...🚀 Creating Agent DaemonSet...🚀 Creating Operator Deployment...⌛ Waiting for Cilium to be installed...

Examples

`install` examples

To install the default version of Cilium:

cilium install

To see the Helm release that got deployed:

helm list -n kube-system --filter "cilium"

To see non-default Helm values thatcilium-cli used for this Cilium installation:

helm get values -n kube-system cilium

To see all the Cilium-related resources without installing them to your cluster:

cilium install --dry-run

To see all the non-default Helm values without actually performing the installation:

cilium install --dry-run-helm-values

To install using Cilium'sOCI dev chart repository:

cilium install --repository oci://quay.io/cilium-charts-dev/cilium --version 1.14.0-dev-dev.4-main-797347707c

`upgrade` examples

To upgrade to a specific version of Cilium:

cilium upgrade --version v1.13.3

To upgrade using a local Helm chart:

cilium upgrade --chart-directory ./install/kubernetes/cilium

To upgrade using Cilium'sOCI dev chart repository:

cilium upgrade --repository oci://quay.io/cilium-charts-dev/cilium --version 1.14.0-dev-dev.4-main-797347707c

Note thatupgrade does not mean you can only upgrade to a newer version than what iscurrently installed. Similar tohelm upgrade,cilium upgrade can be used to downgradeto a previous version. For example:

 cilium install --version 1.13.3 cilium upgrade --version 1.12.10

Please readthe upgrade guidecarefully before upgrading Cilium to understand all the necessary steps. In particular,please note thatcilium-cli does not automatically modify non-default Helm values duringupgrade. You can use--dry-run and--dry-run-helm-values flags to review Kubernetesresources and non-default Helm values without actually performing an upgrade:

To see the difference between the current Kubernetes resources in a live cluster and what wouldbe applied:

cilium upgrade --version v1.13.3 --dry-run | kubectl diff -f -

To see the non-default Helm values that would be used during upgrade:

cilium upgrade --version v1.13.3 --dry-run-helm-values

NoteYou can use external diff tools such asdyff to makekubectl diff output more readable.

It is strongly recommended that you use Cilium'sOCI dev chart repositoryif you need to deploy Cilium with a specific commit SHA. Alternatively, you can useimage.overrideHelm value if you need to override the cilium-agent container image. For example:

cilium upgrade --set image.override=quay.io/cilium/cilium-ci:103e277f78ce95e922bfac98f1e74138a411778a --reuse-values

Please see Cilium'sHelm Reference for thecomplete list of Helm values.

About

CLI to install, manage & troubleshoot Kubernetes clusters running Cilium

cilium.io

Code of conduct

Security policy

Activity

Custom properties

Stars

465 stars

Watchers

26 watching

Forks

211 forks

Report repository

Releases117

Release v0.18.2 Latest

Mar 7, 2025

+ 116 releases

Contributors123

+ 109 contributors

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

License

Folders and files

Latest commit

History

Repository files navigation

Cilium CLI

Installation

Releases

Capabilities

Install Cilium

Supported Environments

Cluster Context Management

Hubble

Status

Connectivity Check

With Flow Validation

Network Performance test

ClusterMesh

Encryption

Examples

`install` examples

`upgrade` examples

About

Topics

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Releases117

Contributors123

Languages

Movatterモバイル変換

License

cilium/cilium-cli

Folders and files

Latest commit

History

Repository files navigation

Cilium CLI

Installation

Releases

Capabilities

Install Cilium

Supported Environments

Cluster Context Management

Hubble

Status

Connectivity Check

With Flow Validation

Network Performance test

ClusterMesh

Encryption

Examples

install examples

upgrade examples

About

Topics

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Releases117

Contributors123

Languages

`install` examples

`upgrade` examples