Update Cilium installation steps

This commit removes the `cilium install` output and adds a proper
explanation of the Cilium installation.

Signed-off-by: Divine Odazie <dodazie@gmail.com>
pull/36775/head
kikiodazie 2022-11-17 13:06:33 +01:00
parent 62dcee861a
commit a794cc6469
1 changed files with 26 additions and 30 deletions

View File

@ -41,43 +41,39 @@ minikube version: v1.5.2
minikube start --network-plugin=cni minikube start --network-plugin=cni
``` ```
For minikube you can install Cilium using its CLI tool. Cilium will For minikube you can install Cilium using its CLI tool. To do so, first download the latest
automatically detect the cluster configuration and will install the appropriate version of the CLI with the following command:
components for a successful installation:
```shell ```shell
curl -LO https://github.com/cilium/cilium-cli/releases/latest/download/cilium-linux-amd64.tar.gz curl -LO https://github.com/cilium/cilium-cli/releases/latest/download/cilium-linux-amd64.tar.gz
```
Then extract the downloaded file to your `/usr/local/bin` directory with the following command:
```shell
sudo tar xzvfC cilium-linux-amd64.tar.gz /usr/local/bin sudo tar xzvfC cilium-linux-amd64.tar.gz /usr/local/bin
rm cilium-linux-amd64.tar.gz rm cilium-linux-amd64.tar.gz
```
After running the above commands, you can now install Cilium with the following command:
```shell
cilium install cilium install
``` ```
```
🔮 Auto-detected Kubernetes kind: minikube Cilium will then automatically detect the cluster configuration and create and
✨ Running "minikube" validation checks install the appropriate components for a successful installation.
✅ Detected minikube version "1.20.0" The components are:
Cilium version not set, using default version "v1.10.0"
🔮 Auto-detected cluster name: minikube - Certificate Authority (CA) in Secret `cilium-ca` and certificates for Hubble (Cilium's observability layer).
🔮 Auto-detected IPAM mode: cluster-pool - Service accounts.
🔮 Auto-detected datapath mode: tunnel - Cluster roles.
🔑 Generating CA... - ConfigMap.
2021/05/27 02:54:44 [INFO] generate received request - Agent DaemonSet and an Operator Deployment.
2021/05/27 02:54:44 [INFO] received CSR
2021/05/27 02:54:44 [INFO] generating key: ecdsa-256 After the installation, you can view the overall status of the Cilium deployment with the `cilium status` command.
2021/05/27 02:54:44 [INFO] encoded CSR See the expected output of the `status` command
2021/05/27 02:54:44 [INFO] signed certificate with serial number 48713764918856674401136471229482703021230538642 [here](https://docs.cilium.io/en/stable/gettingstarted/k8s-install-default/#validate-the-installation).
🔑 Generating certificates for Hubble...
2021/05/27 02:54:44 [INFO] generate received request
2021/05/27 02:54:44 [INFO] received CSR
2021/05/27 02:54:44 [INFO] generating key: ecdsa-256
2021/05/27 02:54:44 [INFO] encoded CSR
2021/05/27 02:54:44 [INFO] signed certificate with serial number 3514109734025784310086389188421560613333279574
🚀 Creating Service accounts...
🚀 Creating Cluster roles...
🚀 Creating ConfigMap...
🚀 Creating Agent DaemonSet...
🚀 Creating Operator Deployment...
⌛ Waiting for Cilium to be installed...
```
The remainder of the Getting Started Guide explains how to enforce both L3/L4 The remainder of the Getting Started Guide explains how to enforce both L3/L4
(i.e., IP address + port) security policies, as well as L7 (e.g., HTTP) security (i.e., IP address + port) security policies, as well as L7 (e.g., HTTP) security