chore: Prepare v0.3.2 release

tibordp · May 22, 2022 · 2835b35 · 2835b35
1 parent f2ad28b
commit 2835b35
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/README.md b/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.3.1/deploy/manifest.yaml
+kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.3.2/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.3.1/deploy/ipv6_only.yaml
+kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.3.2/deploy/ipv6_only.yaml
 ```
 
 ## Configuration

diff --git a/deploy/ipv6_only.yaml b/deploy/ipv6_only.yaml
@@ -55,7 +55,7 @@ spec:
  priorityClassName: system-node-critical
  containers:
  - name: wigglenet
- image: tibordp/wigglenet:v0.3.1
+ image: tibordp/wigglenet:v0.3.2
  imagePullPolicy: Always
  env:
  # Masquerade outgoing IPv4 traffic not destined

diff --git a/deploy/manifest.yaml b/deploy/manifest.yaml
@@ -55,7 +55,7 @@ spec:
  priorityClassName: system-node-critical
  containers:
  - name: wigglenet
- image: tibordp/wigglenet:v0.3.1
+ image: tibordp/wigglenet:v0.3.2
  imagePullPolicy: Always
  env:
  # Masquerade outgoing IPv4 traffic not destined