From eea08ccbdefa1cd261f8ae304a474234cb383f7e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Martins?= Date: Sun, 3 Dec 2017 18:25:59 +0100 Subject: [PATCH] updating cilium links MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: André Martins --- .../cilium-network-policy.md | 44 ++++++++++++------- 1 file changed, 29 insertions(+), 15 deletions(-) diff --git a/docs/tasks/administer-cluster/cilium-network-policy.md b/docs/tasks/administer-cluster/cilium-network-policy.md index 92cb6bf637..08abc7f519 100644 --- a/docs/tasks/administer-cluster/cilium-network-policy.md +++ b/docs/tasks/administer-cluster/cilium-network-policy.md @@ -7,7 +7,7 @@ title: Use Cilium for NetworkPolicy {% capture overview %} This page shows how to use Cilium for NetworkPolicy. -For background on Cilium, read the [Introduction to Cilium](http://cilium.readthedocs.io/en/latest/intro/). +For background on Cilium, read the [Introduction to Cilium](https://cilium.readthedocs.io/en/latest/intro). {% endcapture %} {% capture prerequisites %} @@ -20,37 +20,41 @@ For background on Cilium, read the [Introduction to Cilium](http://cilium.readth ## Deploying Cilium on Minikube for Basic Testing To get familiar with Cilium easily you can follow the -[Cilium Kubernetes Getting Started Guide](http://www.cilium.io/try) +[Cilium Kubernetes Getting Started Guide](https://docs.cilium.io/en/latest/gettingstarted/minikube/) to perform a basic DaemonSet installation of Cilium in minikube. Installation in a minikube setup uses a simple ''all-in-one'' YAML -file that includes DaemonSet configurations for Cilium and a key-value store -(consul) as well as appropriate RBAC settings: +file that includes DaemonSet configurations for Cilium, to connect +to the minikube's etcd instance as well as appropriate RBAC settings: ```shell -$ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/master/examples/minikube/cilium-ds.yaml -clusterrole "cilium" created +$ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/master/examples/kubernetes/cilium.yaml +configmap "cilium-config" created +secret "cilium-etcd-secrets" created serviceaccount "cilium" created clusterrolebinding "cilium" created -daemonset "cilium-consul" created daemonset "cilium" created +clusterrole "cilium" created ``` -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 policies using an example application. +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 +policies using an example application. ## Deploying Cilium for Production Use For detailed instructions around deploying Cilium for production, see: -[Cilium Administrator Guide](http://cilium.readthedocs.io/en/latest/admin/) This -documentation includes detailed requirements, instructions and example production DaemonSet files. +[Cilium Kubernetes Installation Guide](https://cilium.readthedocs.io/en/latest/kubernetes/install/) +This documentation includes detailed requirements, instructions and example +production DaemonSet files. {% endcapture %} {% capture discussion %} ## Understanding Cilium components -Deploying a cluster with Cilium adds Pods to the `kube-system` namespace. To see this list of Pods run: +Deploying a cluster with Cilium adds Pods to the `kube-system` namespace. To see +this list of Pods run: ```shell kubectl get pods --namespace=kube-system @@ -66,13 +70,23 @@ cilium 1 1 1 2m 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 the key-value store cluster (e.g., etcd) used by Kubernetes, which typically runs on the Kubernetes master nodes. The [Cilium Administrator Guide](http://cilium.readthedocs.io/en/latest/admin/) includes an example DaemonSet which can be customized to point to this key-value store cluster. The simple ''all-in-one'' DaemonSet for minikube requires no such configuration because it automatically deploys a `cilium-consul` Pod to provide a key-value store. +- 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 the key-value store cluster +(e.g., etcd) used by Kubernetes, which typically runs on the Kubernetes master nodes. +The [Cilium Kubernetes Installation Guide](https://cilium.readthedocs.io/en/latest/kubernetes/install/) +includes an example DaemonSet which can be customized to point to this key-value +store cluster. The simple ''all-in-one'' DaemonSet for minikube requires no such +configuration because it automatically connects to the minikube's etcd instance. {% endcapture %} {% capture whatsnext %} -Once your cluster is running, you can follow the [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) to try out Kubernetes NetworkPolicy with Cilium. Have fun, and if you have questions, contact us using the [Cilium Slack Channel](https://cilium.herokuapp.com/). +Once your cluster is running, you can follow the +[Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) +to try out Kubernetes NetworkPolicy with Cilium. +Have fun, and if you have questions, contact us using the +[Cilium Slack Channel](https://cilium.herokuapp.com/). {% endcapture %} {% include templates/task.md %}