{"id":13470498,"url":"https://github.com/cilium/cilium-cli","last_synced_at":"2025-04-13T01:59:44.618Z","repository":{"id":36957058,"uuid":"323610158","full_name":"cilium/cilium-cli","owner":"cilium","description":"CLI to install, manage \u0026 troubleshoot Kubernetes clusters running Cilium","archived":false,"fork":false,"pushed_at":"2025-04-12T19:04:20.000Z","size":91186,"stargazers_count":472,"open_issues_count":19,"forks_count":210,"subscribers_count":26,"default_branch":"main","last_synced_at":"2025-04-13T01:59:20.508Z","etag":null,"topics":["cilium","ebpf","kubernetes","networking","observability","security"],"latest_commit_sha":null,"homepage":"https://cilium.io","language":"Makefile","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/cilium.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-12-22T11:44:54.000Z","updated_at":"2025-04-12T07:34:53.000Z","dependencies_parsed_at":"2024-03-10T04:25:18.688Z","dependency_job_id":"1bc3c4ba-97fd-444d-9312-7b28dd63dda4","html_url":"https://github.com/cilium/cilium-cli","commit_stats":{"total_commits":2761,"total_committers":129,"mean_commits":21.4031007751938,"dds":0.8420862006519377,"last_synced_commit":"6aa596fe2abf7277e0137c6c1c379b0637ff45a8"},"previous_names":[],"tags_count":117,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cilium%2Fcilium-cli","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cilium%2Fcilium-cli/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cilium%2Fcilium-cli/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cilium%2Fcilium-cli/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/cilium","download_url":"https://codeload.github.com/cilium/cilium-cli/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248654046,"owners_count":21140235,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cilium","ebpf","kubernetes","networking","observability","security"],"created_at":"2024-07-31T16:00:31.327Z","updated_at":"2025-04-13T01:59:39.609Z","avatar_url":"https://github.com/cilium.png","language":"Makefile","funding_links":[],"categories":["Makefile","Uncategorized"],"sub_categories":["Uncategorized"],"readme":"# Cilium CLI\n\n[![Go](https://github.com/cilium/cilium-cli/workflows/Go/badge.svg)](https://github.com/cilium/cilium-cli/actions?query=workflow%3AGo)\n[![Kind](https://github.com/cilium/cilium-cli/workflows/Kind/badge.svg)](https://github.com/cilium/cilium-cli/actions?query=workflow%3AKind)\n[![EKS (ENI)](https://github.com/cilium/cilium-cli/actions/workflows/eks.yaml/badge.svg)](https://github.com/cilium/cilium-cli/actions/workflows/eks.yaml)\n[![EKS (tunnel)](https://github.com/cilium/cilium-cli/actions/workflows/eks-tunnel.yaml/badge.svg)](https://github.com/cilium/cilium-cli/actions/workflows/eks-tunnel.yaml)\n[![GKE](https://github.com/cilium/cilium-cli/workflows/GKE/badge.svg)](https://github.com/cilium/cilium-cli/actions?query=workflow%3AGKE)\n[![AKS (BYOCNI)](https://github.com/cilium/cilium-cli/actions/workflows/aks-byocni.yaml/badge.svg)](https://github.com/cilium/cilium-cli/actions/workflows/aks-byocni.yaml)\n[![Multicluster](https://github.com/cilium/cilium-cli/workflows/Multicluster/badge.svg)](https://github.com/cilium/cilium-cli/actions?query=workflow%3AMulticluster)\n\n## Installation\n\nTo build and install, use the `install` target:\n\n```console\nmake install\n```\n\nYou may set the `BINDIR` environment variable to install the binary in a\nspecific location instead of `/usr/local/bin`, e.g.\n\n```\nBINDIR=~/.local/bin make install\n```\n\nAlternatively, to install the latest binary release:\n\n```\nCILIUM_CLI_VERSION=$(curl -s https://raw.githubusercontent.com/cilium/cilium-cli/main/stable.txt)\nGOOS=$(go env GOOS)\nGOARCH=$(go env GOARCH)\ncurl -L --remote-name-all https://github.com/cilium/cilium-cli/releases/download/${CILIUM_CLI_VERSION}/cilium-${GOOS}-${GOARCH}.tar.gz{,.sha256sum}\nsha256sum --check cilium-${GOOS}-${GOARCH}.tar.gz.sha256sum\nsudo tar -C /usr/local/bin -xzvf cilium-${GOOS}-${GOARCH}.tar.gz\nrm cilium-${GOOS}-${GOARCH}.tar.gz{,.sha256sum}\n```\n\nSee https://github.com/cilium/cilium-cli/releases for supported `GOOS`/`GOARCH`\nbinary releases.\n\n## Releases\n\n| Release                                                                | Maintained | Compatible Cilium Versions |\n|------------------------------------------------------------------------|------------|----------------------------|\n| [v0.18.2](https://github.com/cilium/cilium-cli/releases/tag/v0.18.2)   | Yes        | Cilium 1.15 and newer      |\n\n## Capabilities\n\n### Install Cilium\n\nTo install Cilium while automatically detected:\n\n    cilium install\n    🔮 Auto-detected Kubernetes kind: minikube\n    ✨ Running \"minikube\" validation checks\n    ✅ Detected minikube version \"1.5.2\"\n    ℹ️  Cilium version not set, using default version \"v1.9.1\"\n    🔮 Auto-detected cluster name: minikube\n    🔑 Found existing CA in secret cilium-ca\n    🔑 Generating certificates for Hubble...\n    🚀 Creating service accounts...\n    🚀 Creating cluster roles...\n    🚀 Creating ConfigMap...\n    🚀 Creating agent DaemonSet...\n    🚀 Creating operator Deployment...\n\n#### Supported Environments\n\n - [x] minikube\n - [x] kind\n - [x] EKS\n - [x] self-managed\n - [x] GKE\n - [x] AKS BYOCNI\n - [x] k3s\n - [ ] Rancher\n\n### Cluster Context Management\n\n    cilium context\n    Context: minikube\n    Cluster: minikube\n    Auth: minikube\n    Host: https://192.168.64.25:8443\n    TLS server name:\n    CA path: /Users/tgraf/.minikube/ca.crt\n\n### Hubble\n\n    cilium hubble enable\n    🔑 Generating certificates for Relay...\n    ✨ Deploying Relay...\n\n### Status\n\n    cilium status\n        /¯¯\\\n     /¯¯\\__/¯¯\\    Cilium:             OK\n     \\__/¯¯\\__/    Operator:           OK\n     /¯¯\\__/¯¯\\    Envoy DaemonSet:    OK\n     \\__/¯¯\\__/    Hubble Relay:       OK\n        \\__/       ClusterMesh:        disabled\n\n    DaemonSet         cilium             Desired: 1, Ready: 1/1, Available: 1/1\n    DaemonSet         cilium-envoy       Desired: 1, Ready: 1/1, Available: 1/1\n    Deployment        cilium-operator    Desired: 1, Ready: 1/1, Available: 1/1\n    Deployment        hubble-relay       Desired: 1, Ready: 1/1, Available: 1/1\n    Containers:       cilium             Running: 1\n                      cilium-envoy       Running: 1\n                      cilium-operator    Running: 1\n                      hubble-relay       Running: 1\n    Image versions    cilium             quay.io/cilium/cilium:v1.9.1: 1\n                      cilium-envoy       quay.io/cilium/cilium-envoy:v1.25.5-37a98693f069413c82bef1724dd75dcf1b564fd9@sha256:d10841c9cc5b0822eeca4e3654929418b6424c978fd818868b429023f6cc215d: 1\n                      cilium-operator    quay.io/cilium/operator-generic:v1.9.1: 1\n                      hubble-relay       quay.io/cilium/hubble-relay:v1.9.1: 1\n\n### Connectivity Check\n\n    cilium connectivity test --single-node\n    ⌛ Waiting for deployments to become ready\n    🔭 Enabling Hubble telescope...\n    ⚠️  Unable to contact Hubble Relay: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp [::1]:4245: connect: connection refused\"\n    ⚠️  Did you enable and expose Hubble + Relay?\n    ℹ️  You can export Relay with a port-forward: kubectl port-forward -n kube-system deployment/hubble-relay 4245:4245\n    ℹ️  Disabling Hubble telescope and flow validation...\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to pod cilium-test/echo-same-node-7f877bbf9-p2xg8...\n    -------------------------------------------------------------------------------------------\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with echo pod echo-same-node-7f877bbf9-p2xg8 (10.0.0.166)\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to outside of cluster...\n    -------------------------------------------------------------------------------------------\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with cilium.io\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to local host...\n    -------------------------------------------------------------------------------------------\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with local host\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to service echo-same-node...\n    -------------------------------------------------------------------------------------------\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with service echo-same-node\n\n#### With Flow Validation\n\n    cilium hubble port-forward\u0026\n    cilium connectivity test --single-node\n    ⌛ Waiting for deployments to become ready\n    🔭 Enabling Hubble telescope...\n    Handling connection for 4245\n    ℹ️  Hubble is OK, flows: 405/4096\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to pod cilium-test/echo-same-node-7f877bbf9-p2xg8...\n    -------------------------------------------------------------------------------------------\n    📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:\n    Jan  6 13:41:17.739: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: SYN)\n    Jan  6 13:41:17.739: 10.0.0.166:8080 -\u003e 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: SYN, ACK)\n    Jan  6 13:41:17.739: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)\n    Jan  6 13:41:17.739: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:17.755: 10.0.0.166:8080 -\u003e 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:17.756: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, FIN)\n    Jan  6 13:41:17.757: 10.0.0.166:8080 -\u003e 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, FIN)\n    Jan  6 13:41:17.757: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)\n    📄 Flow logs of pod cilium-test/echo-same-node-7f877bbf9-p2xg8:\n    Jan  6 13:41:17.739: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: SYN)\n    Jan  6 13:41:17.739: 10.0.0.166:8080 -\u003e 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: SYN, ACK)\n    Jan  6 13:41:17.739: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)\n    Jan  6 13:41:17.739: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:17.755: 10.0.0.166:8080 -\u003e 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:17.756: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, FIN)\n    Jan  6 13:41:17.757: 10.0.0.166:8080 -\u003e 10.0.0.11:43876 to-endpoint FORWARDED (TCP Flags: ACK, FIN)\n    Jan  6 13:41:17.757: 10.0.0.11:43876 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with echo pod echo-same-node-7f877bbf9-p2xg8 (10.0.0.166)\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to outside of cluster...\n    -------------------------------------------------------------------------------------------\n    ❌ Found RST in pod cilium-test/client-9f579495f-b2pcq\n    ❌ FIN not found in pod cilium-test/client-9f579495f-b2pcq\n    📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:\n    Jan  6 13:41:22.025: 10.0.0.11:55334 -\u003e 10.0.0.243:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.025: 10.0.0.11:55334 -\u003e 10.0.0.243:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.027: 10.0.0.243:53 -\u003e 10.0.0.11:55334 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.028: 10.0.0.243:53 -\u003e 10.0.0.11:55334 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.028: 10.0.0.11:56466 -\u003e 10.0.0.104:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.028: 10.0.0.11:56466 -\u003e 10.0.0.104:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.029: 10.0.0.104:53 -\u003e 10.0.0.11:56466 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.029: 10.0.0.104:53 -\u003e 10.0.0.11:56466 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.030: 10.0.0.11:57691 -\u003e 10.0.0.243:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.030: 10.0.0.243:53 -\u003e 10.0.0.11:57691 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.030: 10.0.0.11:57691 -\u003e 10.0.0.243:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.031: 10.0.0.243:53 -\u003e 10.0.0.11:57691 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.031: 10.0.0.11:52849 -\u003e 10.0.0.104:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.032: 10.0.0.104:53 -\u003e 10.0.0.11:52849 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.033: 10.0.0.11:52849 -\u003e 10.0.0.104:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.037: 10.0.0.104:53 -\u003e 10.0.0.11:52849 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:22.038: 10.0.0.11:45040 -\u003e 172.217.168.46:443 to-stack FORWARDED (TCP Flags: SYN)\n    Jan  6 13:41:22.041: 172.217.168.46:443 -\u003e 10.0.0.11:45040 to-endpoint FORWARDED (TCP Flags: SYN, ACK)\n    Jan  6 13:41:22.041: 10.0.0.11:45040 -\u003e 172.217.168.46:443 to-stack FORWARDED (TCP Flags: ACK)\n    Jan  6 13:41:22.059: 10.0.0.11:45040 -\u003e 172.217.168.46:443 to-stack FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:22.073: 172.217.168.46:443 -\u003e 10.0.0.11:45040 to-endpoint FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:22.096: 10.0.0.11:45040 -\u003e 172.217.168.46:443 to-stack FORWARDED (TCP Flags: ACK, RST)\n    Jan  6 13:41:22.097: 172.217.168.46:443 -\u003e 10.0.0.11:45040 to-endpoint FORWARDED (TCP Flags: ACK, FIN)\n    Jan  6 13:41:22.097: 10.0.0.11:45040 -\u003e 172.217.168.46:443 to-stack FORWARDED (TCP Flags: RST)\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with cilium.io\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to local host...\n    -------------------------------------------------------------------------------------------\n    📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:\n    Jan  6 13:41:25.305: 10.0.0.11 -\u003e 192.168.64.25 to-stack FORWARDED (ICMPv4 EchoRequest)\n    Jan  6 13:41:25.305: 192.168.64.25 -\u003e 10.0.0.11 to-endpoint FORWARDED (ICMPv4 EchoReply)\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with local host\n    -------------------------------------------------------------------------------------------\n    🔌 Validating from pod cilium-test/client-9f579495f-b2pcq to service echo-same-node...\n    -------------------------------------------------------------------------------------------\n    📄 Flow logs of pod cilium-test/client-9f579495f-b2pcq:\n    Jan  6 13:41:30.499: 10.0.0.11:39559 -\u003e 10.0.0.104:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:30.499: 10.0.0.11:39559 -\u003e 10.0.0.104:53 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:30.500: 10.0.0.104:53 -\u003e 10.0.0.11:39559 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:30.500: 10.0.0.104:53 -\u003e 10.0.0.11:39559 to-endpoint FORWARDED (UDP)\n    Jan  6 13:41:30.503: 10.0.0.11:59414 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: SYN)\n    Jan  6 13:41:30.503: 10.0.0.166:8080 -\u003e 10.0.0.11:59414 to-endpoint FORWARDED (TCP Flags: SYN, ACK)\n    Jan  6 13:41:30.503: 10.0.0.11:59414 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)\n    Jan  6 13:41:30.503: 10.0.0.11:59414 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:30.505: 10.0.0.166:8080 -\u003e 10.0.0.11:59414 to-endpoint FORWARDED (TCP Flags: ACK, PSH)\n    Jan  6 13:41:30.509: 10.0.0.11:59414 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK, FIN)\n    Jan  6 13:41:30.509: 10.0.0.166:8080 -\u003e 10.0.0.11:59414 to-endpoint FORWARDED (TCP Flags: ACK, FIN)\n    Jan  6 13:41:30.509: 10.0.0.11:59414 -\u003e 10.0.0.166:8080 to-endpoint FORWARDED (TCP Flags: ACK)\n    ✅ client pod client-9f579495f-b2pcq was able to communicate with service echo-same-node\n\n#### Network Performance test\n\n    cilium connectivity perf\n    🔥 Network Performance Test Summary:\n    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n    📋 Scenario        | Node       | Test            | Duration        | Min             | Mean            | Max             | P50             | P90             | P99             | Transaction rate OP/s\n    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n    📋 pod-to-pod      | same-node  | TCP_RR          | 1s              | 16µs            | 32.39µs         | 1.567ms         | 20µs            | 52µs            | 97µs            | 30696.13\n    📋 pod-to-pod      | same-node  | UDP_RR          | 1s              | 14µs            | 29.86µs         | 4.41ms          | 17µs            | 47µs            | 97µs            | 33251.51\n    📋 pod-to-pod      | same-node  | TCP_CRR         | 1s              | 290µs           | 512.1µs         | 13.413ms        | 467µs           | 626µs           | 980µs           | 1949.69\n    📋 pod-to-pod      | other-node | TCP_RR          | 1s              | 350µs           | 692.85µs        | 3.543ms         | 631µs           | 1.001ms         | 1.483ms         | 1438.69\n    📋 pod-to-pod      | other-node | UDP_RR          | 1s              | 312µs           | 865.83µs        | 8.731ms         | 605µs           | 1.444ms         | 6ms             | 1150.79\n    📋 pod-to-pod      | other-node | TCP_CRR         | 1s              | 959µs           | 2.15805ms       | 7.677ms         | 1.555ms         | 5.425ms         | 7.133ms         | 461.78\n    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n    -------------------------------------------------------------------------------------\n    📋 Scenario        | Node       | Test            | Duration        | Throughput Mb/s\n    -------------------------------------------------------------------------------------\n    📋 pod-to-pod      | same-node  | TCP_STREAM      | 1s              | 631.58\n    📋 pod-to-pod      | same-node  | UDP_STREAM      | 1s              | 458.66\n    📋 pod-to-pod      | other-node | TCP_STREAM      | 1s              | 411.43\n    📋 pod-to-pod      | other-node | UDP_STREAM      | 1s              | 144.44\n    -------------------------------------------------------------------------------------\n\n\n### ClusterMesh\n\nInstall Cilium \u0026 enable ClusterMesh in Cluster 1\n\n    cilium install --set=cluster.id=1\n    🔮 Auto-detected Kubernetes kind: GKE\n    ℹ️  Cilium version not set, using default version \"v1.9.1\"\n    🔮 Auto-detected cluster name: gke-cilium-dev-us-west2-a-tgraf-cluster1\n    ✅ Detected GKE native routing CIDR: 10.52.0.0/14\n    🚀 Creating resource quotas...\n    🔑 Found existing CA in secret cilium-ca\n    🔑 Generating certificates for Hubble...\n    🚀 Creating service accounts...\n    🚀 Creating cluster roles...\n    🚀 Creating ConfigMap...\n    🚀 Creating GKE Node Init DaemonSet...\n    🚀 Creating agent DaemonSet...\n    🚀 Creating operator Deployment...\n\n    cilium clustermesh enable\n    ✨ Validating cluster configuration...\n    ✅ Valid cluster identification found: name=\"gke-cilium-dev-us-west2-a-tgraf-cluster1\" id=\"1\"\n    🔑 Found existing CA in secret cilium-ca\n    🔑 Generating certificates for ClusterMesh...\n    ✨ Deploying clustermesh-apiserver...\n    🔮 Auto-exposing service within GCP VPC (cloud.google.com/load-balancer-type=internal)\n\n\nInstall Cilium in Cluster 2\n\n    cilium install --context gke_cilium-dev_us-west2-a_tgraf-cluster2 --set=cluster.id=2\n    🔮 Auto-detected Kubernetes kind: GKE\n    ℹ️  Cilium version not set, using default version \"v1.9.1\"\n    🔮 Auto-detected cluster name: gke-cilium-dev-us-west2-a-tgraf-cluster2\n    ✅ Detected GKE native routing CIDR: 10.4.0.0/14\n    🚀 Creating resource quotas...\n    🔑 Found existing CA in secret cilium-ca\n    🔑 Generating certificates for Hubble...\n    🚀 Creating service accounts...\n    🚀 Creating cluster roles...\n    🚀 Creating ConfigMap...\n    🚀 Creating GKE Node Init DaemonSet...\n    🚀 Creating agent DaemonSet...\n    🚀 Creating operator Deployment...\n\n    cilium clustermesh enable --context gke_cilium-dev_us-west2-a_tgraf-cluster2\n    ✨ Validating cluster configuration...\n    ✅ Valid cluster identification found: name=\"gke-cilium-dev-us-west2-a-tgraf-cluster2\" id=\"2\"\n    🔑 Found existing CA in secret cilium-ca\n    🔑 Generating certificates for ClusterMesh...\n    ✨ Deploying clustermesh-apiserver...\n    🔮 Auto-exposing service within GCP VPC (cloud.google.com/load-balancer-type=internal)\n\nConnect Clusters\n\n    cilium clustermesh connect --destination-context gke_cilium-dev_us-west2-a_tgraf-cluster2\n    ✨ Extracting access information of cluster gke-cilium-dev-us-west2-a-tgraf-cluster2...\n    🔑 Extracting secrets from cluster gke-cilium-dev-us-west2-a-tgraf-cluster2...\n    ℹ️  Found ClusterMesh service IPs: [10.168.15.209]\n    ✨ Extracting access information of cluster gke-cilium-dev-us-west2-a-tgraf-cluster1...\n    🔑 Extracting secrets from cluster gke-cilium-dev-us-west2-a-tgraf-cluster1...\n    ℹ️  Found ClusterMesh service IPs: [10.168.15.208]\n    ✨ Connecting cluster gke_cilium-dev_us-west2-a_tgraf-cluster1 -\u003e gke_cilium-dev_us-west2-a_tgraf-cluster2...\n    🔑 Patching existing secret cilium-clustermesh...\n    ✨ Patching DaemonSet with IP aliases cilium-clustermesh...\n    ✨ Connecting cluster gke_cilium-dev_us-west2-a_tgraf-cluster2 -\u003e gke_cilium-dev_us-west2-a_tgraf-cluster1...\n    🔑 Patching existing secret cilium-clustermesh...\n    ✨ Patching DaemonSet with IP aliases cilium-clustermesh...\n\n### Encryption\n\nInstall a Cilium in a cluster and enable encryption with IPsec\n\n    cilium install --encryption=ipsec\n    🔮 Auto-detected Kubernetes kind: kind\n    ✨ Running \"kind\" validation checks\n    ✅ Detected kind version \"0.9.0\"\n    ℹ️  Cilium version not set, using default version \"v1.9.2\"\n    🔮 Auto-detected cluster name: kind-chart-testing\n    🔮 Auto-detected IPAM mode: kubernetes\n    🔑 Found existing CA in secret cilium-ca\n    🔑 Generating certificates for Hubble...\n    🚀 Creating Service accounts...\n    🚀 Creating Cluster roles...\n    🔑 Generated encryption secret cilium-ipsec-keys\n    🚀 Creating ConfigMap...\n    🚀 Creating Agent DaemonSet...\n    🚀 Creating Operator Deployment...\n    ⌛ Waiting for Cilium to be installed...\n\n### Examples\n\n#### `install` examples\n\nTo install the default version of Cilium:\n\n    cilium install\n\nTo see the Helm release that got deployed:\n\n    helm list -n kube-system --filter \"cilium\"\n\nTo see non-default Helm values that `cilium-cli` used for this Cilium installation:\n\n    helm get values -n kube-system cilium\n\nTo see all the Cilium-related resources without installing them to your cluster:\n\n    cilium install --dry-run\n\nTo see all the non-default Helm values without actually performing the installation:\n\n    cilium install --dry-run-helm-values\n\nTo install using Cilium's [OCI dev chart repository](https://quay.io/repository/cilium-charts-dev/cilium):\n\n    cilium install --repository oci://quay.io/cilium-charts-dev/cilium --version 1.14.0-dev-dev.4-main-797347707c\n\n#### `upgrade` examples\n\nTo upgrade to a specific version of Cilium:\n\n    cilium upgrade --version v1.13.3\n\nTo upgrade using a local Helm chart:\n\n    cilium upgrade --chart-directory ./install/kubernetes/cilium\n\nTo upgrade using Cilium's [OCI dev chart repository](https://quay.io/repository/cilium-charts-dev/cilium):\n\n    cilium upgrade --repository oci://quay.io/cilium-charts-dev/cilium --version 1.14.0-dev-dev.4-main-797347707c\n\nNote that `upgrade` does not mean you can only upgrade to a newer version than what is\ncurrently installed. Similar to `helm upgrade`, `cilium upgrade` can be used to downgrade\nto a previous version. For example:\n\n     cilium install --version 1.13.3\n     cilium upgrade --version 1.12.10\n\nPlease read [the upgrade guide](https://docs.cilium.io/en/stable/operations/upgrade/)\ncarefully before upgrading Cilium to understand all the necessary steps. In particular,\nplease note that `cilium-cli` does not automatically modify non-default Helm values during\nupgrade. You can use `--dry-run` and `--dry-run-helm-values` flags to review Kubernetes\nresources and non-default Helm values without actually performing an upgrade:\n\nTo see the difference between the current Kubernetes resources in a live cluster and what would\nbe applied:\n\n    cilium upgrade --version v1.13.3 --dry-run | kubectl diff -f -\n\nTo see the non-default Helm values that would be used during upgrade:\n\n    cilium upgrade --version v1.13.3 --dry-run-helm-values\n\n\u003e **Note**\n\u003e You can use external diff tools such as [dyff](https://github.com/homeport/dyff) to make\n\u003e `kubectl diff` output more readable.\n\nIt is strongly recommended that you use Cilium's [OCI dev chart repository](https://quay.io/repository/cilium-charts-dev/cilium)\nif you need to deploy Cilium with a specific commit SHA. Alternatively, you can use `image.override`\nHelm value if you need to override the cilium-agent container image. For example:\n\n    cilium upgrade --set image.override=quay.io/cilium/cilium-ci:103e277f78ce95e922bfac98f1e74138a411778a --reuse-values\n\nPlease see Cilium's [Helm Reference](https://docs.cilium.io/en/stable/helm-reference/) for the\ncomplete list of Helm values.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcilium%2Fcilium-cli","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcilium%2Fcilium-cli","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcilium%2Fcilium-cli/lists"}