From 74598b4ee036a387013a657469e24f8f01cd37b8 Mon Sep 17 00:00:00 2001 From: Markus Pesch Date: Sun, 12 Oct 2025 19:19:09 +0200 Subject: [PATCH] docs(README): mention upstream https://proxy.golang.org --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 19f2a31..5487deb 100644 --- a/README.md +++ b/README.md @@ -98,8 +98,8 @@ network policy implementation of CNI plugins. It's support only the official API The example below is an excerpt of the `values.yaml` file. The network policy contains ingress rules to allow incoming traffic from an ingress controller. Additionally two egress rules are defined. The first one to allow the application -outgoing access to the internal running DNS server `core-dns`. The second rule to be able to access the Apache Maven -Central repository via HTTPS. +outgoing access to the internal running DNS server `core-dns`. The second rule to be able to access the upstream Go +proxy `https://proxy.golang.org` via HTTPS. > [!IMPORTANT] > Please keep in mind, that the namespace and pod selector labels can be different from environment to environment. For