3.7 KiB
title, menu_order
| title | menu_order |
|---|---|
| Integrating Kubernetes via the Addon | 63 |
The following topics are discussed:
- Installation
- Network Policy Controller
- Upgrading the Daemon Sets
- Network Policy Controller
- Troubleshooting Blocked Connections
- Changing Configuration Options
In versions of Kubernetes that are 1.4 or greater and that is also configured to use CNI, Weave Net can be installed onto your cluster with a single command:
kubectl apply -f https://git.io/weave-kube
After a few seconds, a Weave Net pod should be running on each Node and any further pods you create will be automatically attached to the Weave network.
If you do not already have a CNI-enabled cluster, you can bootstrap one easily with kubeadm. Alternatively if you are using the older cluster set-up scripts from the Kubernetes repo, then use:
NETWORK_PROVIDER=cni cluster/kube-up.sh
Note: If using the Weave CNI Plugin from a prior full install of Weave Net with your cluster, you must first uninstall it before applying the Weave-kube addon. Shut down Kubernetes, and on all nodes perform the following:
weave reset- Remove any separate provisions you may have made to run Weave at
boot-time, e.g.
systemdunits rm /opt/cni/bin/weave-*
Then relaunch Kubernetes and install the addon as described above.
The URL https://git.io/weave-kube points to the YAML file for the latest release of the Weave Net addon. Historic versions are archived on our GitHub release page.
Kubernetes does not currently support rolling upgrades of daemon sets, and so you will need to perform the procedure manually:
- Apply the updated addon manifest
kubectl apply -f https://git.io/weave-kube - Kill each Weave Net pod with
kubectl deleteand then wait for it to reboot before moving on to the next pod.
The addon also supports the Kubernetes policy API so that you can securely isolate pods from each other based on namespaces and labels. For more information on configuring network policies in Kubernetes see the walkthrough and the NetworkPolicy API object definition.
### Troubleshooting Blocked Connections
If you suspect that legitimate traffic is being blocked by the Weave Network Policy Controller, check the weave-npc container's logs:
$ kubectl logs $(kubectl get pods --all-namespaces | grep weave-net | awk '{print $2}') -n kube-system weave-npc
When the Weave Network Policy Controller blocks a connection, it logs the following details about it:
- protocol used,
- source IP and port,
- destination IP and port,
as per the below example:
TCP connection from 10.32.0.7:56648 to 10.32.0.11:80 blocked by Weave NPC.
UDP connection from 10.32.0.7:56648 to 10.32.0.11:80 blocked by Weave NPC.
### Changing Configuration Options
The default configuration settings can be changed by saving and editing the
addon YAML before running kubectl apply. Additional arguments may be
supplied to the Weave router process by adding them to the command:
array in the YAML file.