aboutsummaryrefslogtreecommitdiff
path: root/content/blog/kubernetes/wireguard-endpoint-on-kubernetes-part-2.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/blog/kubernetes/wireguard-endpoint-on-kubernetes-part-2.md')
-rw-r--r--content/blog/kubernetes/wireguard-endpoint-on-kubernetes-part-2.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/blog/kubernetes/wireguard-endpoint-on-kubernetes-part-2.md b/content/blog/kubernetes/wireguard-endpoint-on-kubernetes-part-2.md
index e8835a9..cd92e58 100644
--- a/content/blog/kubernetes/wireguard-endpoint-on-kubernetes-part-2.md
+++ b/content/blog/kubernetes/wireguard-endpoint-on-kubernetes-part-2.md
@@ -378,7 +378,7 @@ resource "kubernetes_network_policy" "wireguard-postgresql" {
}
```
-If you are not using network policies (you really should) in a namespace, DO NOT create these objects or you will lose connectivity to these namespaces. Kubernetes behaviour when there are no network policies in place in to allow everything, but as soon as the a network policy is created and selects a pod then only traffic that matches it will be allowed. You have been warned!
+If you are not using network policies (you really should) in a namespace, DO NOT create these objects or you will lose connectivity to these namespaces. Kubernetes behaviour when there are no network policies in place in to allow everything, but as soon as a network policy is created then only traffic that matches it will be allowed. You have been warned!
## Exporting the connection information