network-policy-provider: updating cilium documentation for v1.4.0 (#12627)
Signed-off-by: André Martins <aanm90@gmail.com>
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
9fcf418680
commit
0a5ff4417d
+12
-10
@@ -26,20 +26,22 @@ To get familiar with Cilium easily you can follow the
|
||||
[Cilium Kubernetes Getting Started Guide](https://cilium.readthedocs.io/en/stable/gettingstarted/minikube/)
|
||||
to perform a basic DaemonSet installation of Cilium in minikube.
|
||||
|
||||
As Cilium requires a standalone etcd instance, for minikube you can deploy it
|
||||
by running:
|
||||
To start minikube, minimal version required is >= v0.33.1, run the with the
|
||||
following arguments:
|
||||
|
||||
```shell
|
||||
kubectl create -n kube-system -f https://raw.githubusercontent.com/cilium/cilium/v1.3/examples/kubernetes/addons/etcd/standalone-etcd.yaml
|
||||
$ minikube version
|
||||
minikube version: v0.33.1
|
||||
$
|
||||
$ minikube start --network-plugin=cni --memory=4096
|
||||
```
|
||||
|
||||
After etcd is up and running you can deploy Cilium Kubernetes descriptor which
|
||||
is a simple ''all-in-one'' YAML file that includes DaemonSet configurations for
|
||||
Cilium, to connect to the etcd instance previously deployed as well as
|
||||
appropriate RBAC settings:
|
||||
For minikube you can deploy this simple ''all-in-one'' YAML file that includes
|
||||
DaemonSet configurations for Cilium, and the necessary configurations to connect
|
||||
to the etcd instance deployed in minikube as well as appropriate RBAC settings:
|
||||
|
||||
```shell
|
||||
$ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.3/examples/kubernetes/1.12/cilium.yaml
|
||||
$ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.4/examples/kubernetes/1.13/cilium-minikube.yaml
|
||||
configmap/cilium-config created
|
||||
daemonset.apps/cilium created
|
||||
clusterrolebinding.rbac.authorization.k8s.io/cilium created
|
||||
@@ -54,7 +56,7 @@ policies using an example application.
|
||||
## Deploying Cilium for Production Use
|
||||
|
||||
For detailed instructions around deploying Cilium for production, see:
|
||||
[Cilium Kubernetes Installation Guide](https://cilium.readthedocs.io/en/latest/kubernetes/install/)
|
||||
[Cilium Kubernetes Installation Guide](https://cilium.readthedocs.io/en/stable/kubernetes/intro/)
|
||||
This documentation includes detailed requirements, instructions and example
|
||||
production DaemonSet files.
|
||||
|
||||
@@ -83,7 +85,7 @@ There are two main components to be aware of:
|
||||
- One `cilium` Pod runs on each node in your cluster and enforces network policy
|
||||
on the traffic to/from Pods on that node using Linux BPF.
|
||||
- For production deployments, Cilium should leverage a key-value store
|
||||
(e.g., etcd). The [Cilium Kubernetes Installation Guide](https://cilium.readthedocs.io/en/latest/kubernetes/install/)
|
||||
(e.g., etcd). The [Cilium Kubernetes Installation Guide](https://cilium.readthedocs.io/en/stable/kubernetes/intro/)
|
||||
will provide the necessary steps on how to install this required key-value
|
||||
store as well how to configure it in Cilium.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user