Update docu for 4.6.0 release (#681)

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:4.5.0 .
+docker buildx build --platform linux/amd64,linux/arm64 -t quay.io/gogatekeeper/gatekeeper:4.6.0 .
 ```
 
 or you can use already existing Docker image by running:
 
 ```bash
-docker run -it --rm quay.io/gogatekeeper/gatekeeper:4.5.0 \
+docker run -it --rm quay.io/gogatekeeper/gatekeeper:4.6.0 \
       --listen 127.0.0.1:8080 \
       --upstream-url http://127.0.0.1:80 \
       --discovery-url https://keycloak.example.com/realms/<REALM_NAME> \
@@ -44,16 +44,16 @@ Beside links to archives of binaries we provide also checksum file containing ch
 for archives. You can download file gatekeeper-checksum.txt, it contains sha512 checksums e.g.:
 
 ```
-324b34ece86b6214f835ba9fd79e185864a9005f514458796c22c053de63f428235d2d2a04864065a49c090ad81d2daeb45546544fdd9531a8dea1a43145b8f0  gatekeeper_4.5.0_windows_amd64.zip
-38759e75a94d130758cd26958bd9a66b261be8d58a6c7a0fc04845157649aaf628d22a115c95285b405f8e4d6afa8bd78ca8677d1304faf06db93a0cbbc831a6  gatekeeper_4.5.0_linux_amd64.tar.gz
-f5322e41b3d78017191246bdd54f99e9b3dd8d5ff9d224e7e81b678a952c1d5aae125ea4c251928969b0a0ea0dc59724308c918993c8227f384f61896f58cbd0  gatekeeper_4.5.0_macOS_amd64.tar.gz
+324b34ece86b6214f835ba9fd79e185864a9005f514458796c22c053de63f428235d2d2a04864065a49c090ad81d2daeb45546544fdd9531a8dea1a43145b8f0  gatekeeper_4.6.0_windows_amd64.zip
+38759e75a94d130758cd26958bd9a66b261be8d58a6c7a0fc04845157649aaf628d22a115c95285b405f8e4d6afa8bd78ca8677d1304faf06db93a0cbbc831a6  gatekeeper_4.6.0_linux_amd64.tar.gz
+f5322e41b3d78017191246bdd54f99e9b3dd8d5ff9d224e7e81b678a952c1d5aae125ea4c251928969b0a0ea0dc59724308c918993c8227f384f61896f58cbd0  gatekeeper_4.6.0_macOS_amd64.tar.gz
 ```
 
 After you download archive of binary you can calculate it's checksum by using e.g. sha512sum Linux utility:
 
 ```
-sha512sum /my/path/gatekeeper_4.5.0_linux_amd64.tar.gz
-38759e75a94d130758cd26958bd9a66b261be8d58a6c7a0fc04845157649aaf628d22a115c95285b405f8e4d6afa8bd78ca8677d1304faf06db93a0cbbc831a6  gatekeeper_4.5.0_linux_amd64.tar.gz
+sha512sum /my/path/gatekeeper_4.6.0_linux_amd64.tar.gz
+38759e75a94d130758cd26958bd9a66b261be8d58a6c7a0fc04845157649aaf628d22a115c95285b405f8e4d6afa8bd78ca8677d1304faf06db93a0cbbc831a6  gatekeeper_4.6.0_linux_amd64.tar.gz
 ```
 
 As you can see output of command is checksum, you can compare it with the one in gatekeeper-checksum.txt.

docs/content/_index.md

@@ -532,7 +532,7 @@ in Keycloak, providing granular role controls over issue tokens.
 
 ``` yaml
 - name: gatekeeper
-  image: quay.io/gogatekeeper/gatekeeper:4.5.0
+  image: quay.io/gogatekeeper/gatekeeper:4.6.0
   args:
   - --enable-forwarding=true
   - --forwarding-username=projecta
@@ -559,7 +559,7 @@ Example setup client credentials grant:
 
 ``` yaml
 - name: gatekeeper
-  image: quay.io/gogatekeeper/gatekeeper:4.5.0
+  image: quay.io/gogatekeeper/gatekeeper:4.6.0
   args:
   - --enable-forwarding=true
   - --forwarding-domains=projecta.svc.cluster.local

docs/content/configuration/_index.md

@@ -158,7 +158,7 @@ weight: 2
 |    \--enable-request-upstream-compression    | enables asking upstream for compression, by adding Accept-Encoding: gzip header and decompressing response from upstream | true | PROXY_ENABLE_REQUEST_UPSTREAM_COMPRESSION
 |    \--enable-accept-encoding-header          | pass Accept-Encoding header from client to upstream | false | PROXY_ENABLE_ACCEPT_ENCODING_HEADER
 |    \--enable-id-token-claims                 | extract claims also from ID token, you can then use --add-claims option to specify claims from ID token | false | PROXY_ENABLE_ID_TOKEN_CLAIMS
-|    \--enable-userinfo-claims                 | extract claims also from userinfo, you can then use --add-claims option to specify claims | false | PROXY_ENABLE_USER_INFO_CLAIMS
+|    \--enable-user-info-claims                 | extract claims also from userinfo, you can then use --add-claims option to specify claims | false | PROXY_ENABLE_USER_INFO_CLAIMS
 |    \--enable-loa                             | enable level of authentication            | false |
 |    \--enable-store-ha                        | enable RedisCluster HA client             | false | PROXY_ENABLE_STORE_HA
 |    \--disable-all-logging                    | disables all logging to stdout and stderr | false | PROXY_DISABLE_ALL_LOGGING

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:4.3.0
+          image: quay.io/gogatekeeper/gatekeeper:4.6.0
           imagePullPolicy: Never
           args:
             - --client-id=test-client

kube/forward.yml

@@ -13,7 +13,7 @@ spec:
     spec:
       containers:
       - name: proxy
-        image: quay.io/gogatekeeper/gatekeeper:1.6.0
+        image: quay.io/gogatekeeper/gatekeeper:4.6.0
         imagePullPolicy: Always
         args:
           - --config /etc/secrets/forwarding.yml

kube/reverse.yml

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