Skip to content

Commit

Permalink
Merge pull request #265 from solo-io/automation
Browse files Browse the repository at this point in the history
[bot] Merge automation
  • Loading branch information
djannot authored Oct 31, 2024
2 parents 2e9fdbb + d449d1f commit 4af65b7
Show file tree
Hide file tree
Showing 35 changed files with 3,621 additions and 155 deletions.
2 changes: 2 additions & 0 deletions gloo-gateway/1-17/enterprise-istio-ambient/default/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -925,6 +925,8 @@ global:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
2 changes: 2 additions & 0 deletions gloo-gateway/1-17/enterprise-istio-sidecar/default/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -875,6 +875,8 @@ global:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,8 @@ settings:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down Expand Up @@ -1384,6 +1386,8 @@ settings:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
2 changes: 2 additions & 0 deletions gloo-gateway/1-17/enterprise/default/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -817,6 +817,8 @@ global:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
2 changes: 2 additions & 0 deletions gloo-gateway/1-17/gloo-edge/default/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2699,6 +2699,8 @@ global:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
2 changes: 2 additions & 0 deletions gloo-gateway/1-17/gloo-mesh/default/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3495,6 +3495,8 @@ global:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
10 changes: 10 additions & 0 deletions gloo-gateway/1-17/openshift/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1021,6 +1021,8 @@ global:
extensions:
caching:
enabled: true
deployment:
floatingUserId: true
istioSDS:
enabled: true
istioIntegration:
Expand All @@ -1029,6 +1031,14 @@ global:
EOF
```


Let's completly disable Redis persistence to avoid providing more permissions on Openshift

```bash
kubectl --context $CLUSTER1 patch deployment redis -n gloo-system --type=json -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--save \"\""}]'
```


Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
44 changes: 38 additions & 6 deletions gloo-gateway/1-18/enterprise-istio-ambient/default/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -895,7 +895,7 @@ helm repo update
helm upgrade -i -n gloo-system \
gloo-gateway gloo-ee-test-helm/gloo-ee \
--create-namespace \
--version 1.18.0-beta2-bmain-1203aed \
--version 1.18.0-beta2-bmain-bc445a4 \
--kube-context $CLUSTER1 \
--set-string license_key=$LICENSE_KEY \
-f -<<EOF
Expand Down Expand Up @@ -945,6 +945,8 @@ global:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down Expand Up @@ -6680,6 +6682,7 @@ export API_KEY=<the value displayed in the UI>
```
</details>


<details>
<summary>Using curl</summary>
Create the user:
Expand Down Expand Up @@ -6932,6 +6935,7 @@ You should get the following response:
```
</details>


Try to access the API without authentication:

```shell
Expand Down Expand Up @@ -7104,7 +7108,7 @@ We can now configure the Gloo Gateway portal backend to use it:
helm upgrade -i -n gloo-system \
gloo-gateway gloo-ee-test-helm/gloo-ee \
--create-namespace \
--version 1.18.0-beta2-bmain-1203aed \
--version 1.18.0-beta2-bmain-bc445a4 \
--kube-context ${CLUSTER1} \
--reuse-values \
-f -<<EOF
Expand Down Expand Up @@ -7144,10 +7148,6 @@ spec:
EOF
```

<!--bash
sleep 5
-->

<details open>
<summary>Using the portal frontend UI</summary>

Expand All @@ -7164,17 +7164,49 @@ export CLIENT_SECRET=<the value displayed in the UI>

</details>


<details>
<summary>Using curl</summary>
You can now get your oauth client id and secret:

```bash
export USER1_COOKIE=$(node tests/keycloak-token.js "https://portal.example.com/v1/login" user1)
read -r CLIENT_ID CLIENT_SECRET <<<$(curl -k -H "Cookie: ${USER1_COOKIE}" -X POST "https://portal.example.com/v1/apps/${APP_ID}/oauth-credentials" | jq -r '.idpClientId + " "+ .idpClientSecret')
echo export CLIENT_ID=$CLIENT_ID
echo export CLIENT_SECRET=$CLIENT_SECRET
```

<!--bash
if [ -n "$CLIENT_ID" ] && [ -n "$CLIENT_SECRET" ]; then
echo "Variables are already set"
else
attempt=1
max_attempts=10

while [ $attempt -le $max_attempts ]; do
export USER1_COOKIE=$(node tests/keycloak-token.js "https://portal.example.com/v1/login" user1)
read -r CLIENT_ID CLIENT_SECRET <<<$(curl -k -H "Cookie: ${USER1_COOKIE}" -X POST "https://portal.example.com/v1/apps/${APP_ID}/oauth-credentials" | jq -r '.idpClientId + " "+ .idpClientSecret')

if [ -n "$CLIENT_ID" ] && [ -n "$CLIENT_SECRET" ]; then
echo "export CLIENT_ID=$CLIENT_ID"
echo "export CLIENT_SECRET=$CLIENT_SECRET"
break
fi

echo "Attempt $attempt of $max_attempts: Variables empty, retrying in 5 seconds..."
sleep 5
((attempt++))
done

if [ $attempt -gt $max_attempts ]; then
echo "Failed to get non-empty variables after $max_attempts attempts"
exit 1
fi
fi
-->
</details>


Generate an access token using your client id and secret:

```bash
Expand Down
44 changes: 38 additions & 6 deletions gloo-gateway/1-18/enterprise-istio-sidecar/default/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -840,7 +840,7 @@ helm repo update
helm upgrade -i -n gloo-system \
gloo-gateway gloo-ee-test-helm/gloo-ee \
--create-namespace \
--version 1.18.0-beta2-bmain-1203aed \
--version 1.18.0-beta2-bmain-bc445a4 \
--kube-context $CLUSTER1 \
--set-string license_key=$LICENSE_KEY \
-f -<<EOF
Expand Down Expand Up @@ -895,6 +895,8 @@ global:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down Expand Up @@ -6605,6 +6607,7 @@ export API_KEY=<the value displayed in the UI>
```
</details>


<details>
<summary>Using curl</summary>
Create the user:
Expand Down Expand Up @@ -6857,6 +6860,7 @@ You should get the following response:
```
</details>


Try to access the API without authentication:

```shell
Expand Down Expand Up @@ -7029,7 +7033,7 @@ We can now configure the Gloo Gateway portal backend to use it:
helm upgrade -i -n gloo-system \
gloo-gateway gloo-ee-test-helm/gloo-ee \
--create-namespace \
--version 1.18.0-beta2-bmain-1203aed \
--version 1.18.0-beta2-bmain-bc445a4 \
--kube-context ${CLUSTER1} \
--reuse-values \
-f -<<EOF
Expand Down Expand Up @@ -7069,10 +7073,6 @@ spec:
EOF
```

<!--bash
sleep 5
-->

<details open>
<summary>Using the portal frontend UI</summary>

Expand All @@ -7089,17 +7089,49 @@ export CLIENT_SECRET=<the value displayed in the UI>

</details>


<details>
<summary>Using curl</summary>
You can now get your oauth client id and secret:

```bash
export USER1_COOKIE=$(node tests/keycloak-token.js "https://portal.example.com/v1/login" user1)
read -r CLIENT_ID CLIENT_SECRET <<<$(curl -k -H "Cookie: ${USER1_COOKIE}" -X POST "https://portal.example.com/v1/apps/${APP_ID}/oauth-credentials" | jq -r '.idpClientId + " "+ .idpClientSecret')
echo export CLIENT_ID=$CLIENT_ID
echo export CLIENT_SECRET=$CLIENT_SECRET
```

<!--bash
if [ -n "$CLIENT_ID" ] && [ -n "$CLIENT_SECRET" ]; then
echo "Variables are already set"
else
attempt=1
max_attempts=10

while [ $attempt -le $max_attempts ]; do
export USER1_COOKIE=$(node tests/keycloak-token.js "https://portal.example.com/v1/login" user1)
read -r CLIENT_ID CLIENT_SECRET <<<$(curl -k -H "Cookie: ${USER1_COOKIE}" -X POST "https://portal.example.com/v1/apps/${APP_ID}/oauth-credentials" | jq -r '.idpClientId + " "+ .idpClientSecret')

if [ -n "$CLIENT_ID" ] && [ -n "$CLIENT_SECRET" ]; then
echo "export CLIENT_ID=$CLIENT_ID"
echo "export CLIENT_SECRET=$CLIENT_SECRET"
break
fi

echo "Attempt $attempt of $max_attempts: Variables empty, retrying in 5 seconds..."
sleep 5
((attempt++))
done

if [ $attempt -gt $max_attempts ]; then
echo "Failed to get non-empty variables after $max_attempts attempts"
exit 1
fi
fi
-->
</details>


Generate an access token using your client id and secret:

```bash
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,7 @@ helm repo update
helm upgrade -i -n gloo-system \
gloo-gateway gloo-ee-test-helm/gloo-ee \
--create-namespace \
--version 1.18.0-beta2-bmain-1203aed \
--version 1.18.0-beta2-bmain-bc445a4 \
--kube-context $CLUSTER1 \
--set-string license_key=$LICENSE_KEY \
-f -<<EOF
Expand Down Expand Up @@ -197,6 +197,8 @@ settings:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down Expand Up @@ -1341,7 +1343,7 @@ helm repo update
helm upgrade -i -n gloo-system \
gloo-gateway gloo-ee-test-helm/gloo-ee \
--create-namespace \
--version 1.18.0-beta2-bmain-1203aed \
--version 1.18.0-beta2-bmain-bc445a4 \
--kube-context $CLUSTER2 \
--set-string license_key=$LICENSE_KEY \
-f -<<EOF
Expand Down Expand Up @@ -1384,6 +1386,8 @@ settings:
EOF
```



Run the following command to check that the Gloo Gateway pods are running:

<!--bash
Expand Down
Loading

0 comments on commit 4af65b7

Please sign in to comment.