Update docu 3.3.0 (#568)

Author: p53

README.md

@@ -22,13 +22,13 @@ Please remember to provide a good summary, description as well as steps to repro
 To run Gatekeeper, you can build it using this command:
 
 ```bash
-docker buildx build --platform linux/amd64,linux/arm64 -t quay.io/gogatekeeper/gatekeeper:3.2.1 .
+docker buildx build --platform linux/amd64,linux/arm64 -t quay.io/gogatekeeper/gatekeeper:3.3.0 .
 ```
 
 or you can use aleady existing Docker image by running:
 
 ```bash
-docker run -it --rm quay.io/gogatekeeper/gatekeeper:3.2.1 \
+docker run -it --rm quay.io/gogatekeeper/gatekeeper:3.3.0 \
       --listen 127.0.0.1:8080 \
       --upstream-url http://127.0.0.1:80 \
       --discovery-url https://keycloak.example.com/realms/<REALM_NAME> \

docs/content/_index.md

@@ -515,7 +515,7 @@ in Keycloak, providing granular role controls over issue tokens.
 
 ``` yaml
 - name: gatekeeper
-  image: quay.io/gogatekeeper/gatekeeper:3.2.1
+  image: quay.io/gogatekeeper/gatekeeper:3.3.0
   args:
   - --enable-forwarding=true
   - --forwarding-username=projecta
@@ -542,7 +542,7 @@ Example setup client credentials grant:
 
 ``` yaml
 - name: gatekeeper
-  image: quay.io/gogatekeeper/gatekeeper:3.2.1
+  image: quay.io/gogatekeeper/gatekeeper:3.3.0
   args:
   - --enable-forwarding=true
   - --forwarding-domains=projecta.svc.cluster.local
@@ -1025,6 +1025,12 @@ Or on the command line
   --resources "uri=/admin*|roles=admin,superuser|methods=POST,DELETE"
 ```
 
+From version 3.3.0 there is new option in resources: `white-listed-anon`.
+This option enables to allow anonymous access on resource (means no access token/bearer token present in request)
+and also allows in same time authenticated access on same resource (means for requests containing token it will validate it and request will go through whole authentication/authorization stack).
+This feature might be usefull e.g. in case you have public and private pages, but you would
+like to return private pages list only in case request was authenticated.
+
 ## PKCE (Proof Key for Code Exchange)
 
 Gatekeeper supports PKCE with S256 code challenge method. It stores code verifier in cookie.

e2e/k8s/manifest_test_forwardauth.yml

@@ -2626,7 +2626,7 @@ spec:
             - -c
             - "while true;do sleep 10;done"
         - name: proxy
-          image: quay.io/gogatekeeper/gatekeeper:3.2.1
+          image: quay.io/gogatekeeper/gatekeeper:3.3.0
           imagePullPolicy: Never
           args:
             - --client-id=test-client

kube/reverse.yml

@@ -21,7 +21,7 @@ spec:
           secretName: tls
       containers:
         - name: proxy
-          image: quay.io/gogatekeeper/gatekeeper:3.2.1
+          image: quay.io/gogatekeeper/gatekeeper:3.3.0
           imagePullPolicy: Always
           args:
             - --client-id=broker