Skip to content

Commit

Permalink
Updates the Calico installation page (#7094)
Browse files Browse the repository at this point in the history
  • Loading branch information
emanic authored and k8s-ci-robot committed Jan 29, 2018
1 parent bddc6c0 commit 197a375
Showing 1 changed file with 23 additions and 32 deletions.
55 changes: 23 additions & 32 deletions docs/tasks/administer-cluster/calico-network-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,57 +5,48 @@ title: Use Calico for NetworkPolicy
---

{% capture overview %}
This page shows how to use Calico for NetworkPolicy.
This page shows a couple of quick ways to create a Calico cluster on Kubernetes.
{% endcapture %}

{% capture prerequisites %}
* [Install Calico for Kubernetes](https://docs.projectcalico.org/latest/getting-started/kubernetes/installation/).
Decide whether you want to deploy a [cloud](#creating-a-calico-cluster-with-google-kubernetes-engine-gke) or [local](#creating-a-local-calico-cluster-with-kubeadm) cluster.
{% endcapture %}

{% capture steps %}
## Deploying a cluster using Calico
## Creating a Calico cluster with Google Kubernetes Engine (GKE)

You can deploy a cluster using Calico for network policy in the default [GCE deployment](/docs/getting-started-guides/gce/) using the following set of commands:
**Prerequisite**: [gcloud](https://cloud.google.com/sdk/docs/quickstarts).

```shell
export NETWORK_POLICY_PROVIDER=calico
export KUBE_NODE_OS_DISTRIBUTION=debian
curl -sS https://get.k8s.io | bash
```
1. To launch a GKE cluster with Calico, just include the `--enable-network-policy` flag.

See the [Calico documentation](http://docs.projectcalico.org/) for more options to deploy Calico with Kubernetes.
{% endcapture %}

{% capture discussion %}
## Understanding Calico components
**Syntax**
```shell
gcloud container clusters create [CLUSTER_NAME] --enable-network-policy
```

Deploying a cluster with Calico adds Pods that support Kubernetes NetworkPolicy. These Pods run in the `kube-system` Namespace.
**Example**
```shell
gcloud container clusters create my-calico-cluster --enable-network-policy
```

To see this list of Pods run:
1. To verify the deployment, use the following command.

```shell
kubectl get pods --namespace=kube-system
```
```shell
kubectl get pods --namespace=kube-system
```

You'll see a list of Pods similar to this:
The Calico pods begin with `calico`. Check to make sure each one has a status of `Running`.

```console
NAME READY STATUS RESTARTS AGE
calico-node-kubernetes-minion-group-jck6 1/1 Running 0 46m
calico-node-kubernetes-minion-group-k9jy 1/1 Running 0 46m
calico-node-kubernetes-minion-group-szgr 1/1 Running 0 46m
calico-policy-controller-65rw1 1/1 Running 0 46m
...
```
## Creating a local Calico cluster with kubeadm

There are two main components to be aware of:
To get a local single-host Calico cluster in fifteen minutes using kubeadm, refer to the
[Calico Quickstart](https://docs.projectcalico.org/latest/getting-started/kubernetes/).

- One `calico-node` Pod runs on each node in your cluster and enforces network policy on the traffic to/from Pods on that machine by configuring iptables.
- The `calico-policy-controller` Pod reads the policy and label information from the Kubernetes API and configures Calico appropriately.
{% 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.
{% endcapture %}

{% include templates/task.md %}
{% include templates/task.md %}

0 comments on commit 197a375

Please sign in to comment.