Skip to content

Commit

Permalink
📖 Add Azure tab for deploy Calico CNI step in quickstart
Browse files Browse the repository at this point in the history
  • Loading branch information
Cecile Robert-Michon committed Apr 8, 2020
1 parent b1b3520 commit 4618535
Showing 1 changed file with 21 additions and 0 deletions.
21 changes: 21 additions & 0 deletions docs/book/src/user/quick-start.md
Original file line number Diff line number Diff line change
Expand Up @@ -484,6 +484,9 @@ kubectl --namespace=default get secret/capi-quickstart-kubeconfig -o jsonpath={.

Calico is used here as an example.

{{#tabs name:"tab-deploy-cni" tabs:"AWS|Docker|GCP|vSphere|OpenStack|Metal3,Azure"}}
{{#tab AWS|Docker|GCP|vSphere|OpenStack|Metal3}}

```bash
kubectl --kubeconfig=./capi-quickstart.kubeconfig \
apply -f https://docs.projectcalico.org/v3.12/manifests/calico.yaml
Expand All @@ -496,6 +499,24 @@ let's check the status using `kubectl get nodes`:
kubectl --kubeconfig=./capi-quickstart.kubeconfig get nodes
```

{{#/tab }}
{{#tab Azure}}

```bash
kubectl --kubeconfig=./capi-quickstart.kubeconfig \
apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/master/templates/addons/calico.yaml
```

After a short while, our nodes should be running and in `Ready` state,
let's check the status using `kubectl get nodes`:

```bash
kubectl --kubeconfig=./capi-quickstart.kubeconfig get nodes
```

{{#/tab }}
{{#/tabs }}

## Next steps

See the [clusterctl] documentation for more detail about clusterctl supported actions.
Expand Down

0 comments on commit 4618535

Please sign in to comment.