chore: prepare v0.2.1 release

README.md

@@ -23,15 +23,15 @@ Wigglenet explicitely supports and encourages allocation of public IPv6 addresse
 To install Wigglenet on a dual-stack cluster with the default settings:
 
 ```shell
-kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.2.0/deploy/manifest.yaml
+kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.2.1/deploy/manifest.yaml
 ```
 
 The default configuration should work out of the box for a cluster created with kubeadm using [the official dual-stack tutorial](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/dual-stack-support/). It will enable masquerading for both IPv6 and IPv4 addresses. 
 
 Use the following manifest if the cluster is single-stack (IPv6 only):
 
 ```shell
-kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.2.0/deploy/ipv6_only.yaml
+kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.2.1/deploy/ipv6_only.yaml
 ```
 
 ## Configuration

deploy/ipv6_only.yaml

@@ -54,7 +54,7 @@ spec:
  serviceAccountName: wigglenet
  containers:
  - name: wigglenet
- image: tibordp/wigglenet:0.2.0
+ image: tibordp/wigglenet:0.2.1
  imagePullPolicy: Always
  env:
  # Masquerade outgoing IPv4 traffic not destined

deploy/manifest.yaml

@@ -54,7 +54,7 @@ spec:
  serviceAccountName: wigglenet
  containers:
  - name: wigglenet
- image: tibordp/wigglenet:0.2.0
+ image: tibordp/wigglenet:0.2.1
  imagePullPolicy: Always
  env:
  # Masquerade outgoing IPv4 traffic not destined
@@ -146,4 +146,4 @@ spec:
  type: FileOrCreate
  - name: lib-modules
  hostPath:
- path: /lib/modules
+ path: /lib/modules