Skip to content

Commit

Permalink
spelling and grammer
Browse files Browse the repository at this point in the history
Signed-off-by: R-Lawton <[email protected]>
  • Loading branch information
R-Lawton committed Dec 3, 2024
1 parent c7cae10 commit 000e216
Showing 1 changed file with 5 additions and 5 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,7 @@ Check that the `TLSpolicy` has an Accepted and Enforced status:
kubectl get tlspolicy ${KUADRANT_GATEWAY_NAME}-tls -n ${KUADRANT_GATEWAY_NS} -o=jsonpath='{.status.conditions[?(@.type=="Accepted")].message}{"\n"}{.status.conditions[?(@.type=="Enforced")].message}'
```

### Secure and protect the Gateway with Auth, Rate limit, and DNS policies.
### Secure and protect the Gateway with Auth, Rate Limit, and DNS policies.

While the `Gateway` is now deployed, it currently has exposed endpoints. The next steps will be defining an `AuthPolicy` to set up a default `403` response for any unprotected endpoints, as well as a `RateLimitPolicy` to set up a default unrealistic low global limit to further protect any exposed endpoints.

Expand Down Expand Up @@ -261,7 +261,7 @@ kubectl get authpolicy ${KUADRANT_GATEWAY_NAME}-auth -n ${KUADRANT_GATEWAY_NS} -

```

### Deploy the `low limit` Gateway RateLimitPolicy
### Deploy the `low-limit` Gateway RateLimitPolicy

```bash
kubectl apply -f - <<EOF
Expand Down Expand Up @@ -319,15 +319,15 @@ Check that the `DNSPolicy` has been Accepted and Enforced:
kubectl get dnspolicy ${KUADRANT_GATEWAY_NAME}-dnspolicy -n ${KUADRANT_GATEWAY_NS} -o=jsonpath='{.status.conditions[?(@.type=="Accepted")].message}{"\n"}{.status.conditions[?(@.type=="Enforced")].message}'
```

### Test the `low limit` and deny all policies
### Test the `low-limit` and deny all policies

```bash
while :; do curl -k --write-out '%{http_code}\n' --silent --output /dev/null "https://api.$KUADRANT_ZONE_ROOT_DOMAIN/cars" | grep -E --color "\b(429)\b|$"; sleep 1; done
```

### (Optional) Configure metrics to be scraped from the Gateway instance

If Prometheus is installed on the cluster, set up a PodMonitor to configure it to scrape metrics directly from the Gateway pod.
If Prometheus is installed on the cluster, set up a `PodMonitor` to configure it to scrape metrics directly from the Gateway pod.
This must be done in the namespace where the Gateway is running. For a list of the metrics you'll get see the Kuadrant [docs](https://docs.kuadrant.io/0.11.0/kuadrant-operator/doc/observability/metrics/)

```bash
Expand Down Expand Up @@ -439,7 +439,7 @@ spec:
EOF
```

### Override `low limit` RateLimitPolicy for specific users
### Override `low-limit` RateLimitPolicy for specific users

Create a new `RateLimitPolicy` in a different namespace to override the default `RateLimitPolicy` created earlier:

Expand Down

0 comments on commit 000e216

Please sign in to comment.