chore: prepare v0.4.3 release

Author: tibordp

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.4.3/deploy/manifest.yaml
+kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.4.4/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.4.3/deploy/ipv6_only.yaml
+kubectl apply -f https://raw.githubusercontent.com/tibordp/wigglenet/v0.4.4/deploy/ipv6_only.yaml
 ```
 
 ## Configuration

deploy/ipv6_only.yaml

@@ -55,7 +55,7 @@ spec:
       priorityClassName: system-node-critical
       containers:
       - name: wigglenet
-        image: ghcr.io/tibordp/wigglenet:v0.4.3
+        image: ghcr.io/tibordp/wigglenet:v0.4.4
         imagePullPolicy: Always
         env:
           # Masquerade outgoing IPv4 traffic not destined

deploy/manifest.yaml

@@ -55,7 +55,7 @@ spec:
       priorityClassName: system-node-critical
       containers:
       - name: wigglenet
-        image: ghcr.io/tibordp/wigglenet:v0.4.3
+        image: ghcr.io/tibordp/wigglenet:v0.4.4
         imagePullPolicy: Always
         env:
           # Masquerade outgoing IPv4 traffic not destined