2
0
mirror of https://github.com/status-im/consul.git synced 2025-01-11 22:34:55 +00:00

fix formatting on upgrade and release note pages.

This commit is contained in:
Jeff-Apple 2022-06-21 16:24:19 -07:00
parent ee96f47d22
commit 24e3a3b3be
2 changed files with 3 additions and 5 deletions
website/content/docs
api-gateway
release-notes/consul-api-gateway

@ -47,7 +47,7 @@ Ensure that the following requirements are met prior to upgrading:
$ kubectl get Gateway --output json --all-namespaces
```
If you have any active `Gateways`, you will receive output similar to the following response. The output has been truncated to show only relevant fields:
If you have any active `Gateways`, you will receive output similar to the following response. The output has been truncated to show only relevant fields:
```yaml
apiVersion: gateway.networking.k8s.io/v1alpha2
@ -84,8 +84,8 @@ Ensure that the following requirements are met prior to upgrading:
example-certificate:
- namespace: certificate-namespace
parentNamespace: gateway-namespace
```
</CodeBlockConfig>
Proceed with the [standard-upgrade](#standard-upgrade) if your list is empty.
@ -183,7 +183,6 @@ Ensure that the following requirements are met prior to upgrading:
### Procedure
1. Verify the current version of the `consul-api-gateway-controller` `Deployment`:
```shell-session

@ -23,7 +23,7 @@ description: >-
per `gateway` to all `gateways` in that `gatewayClass`. The minimum and
maximum settings will override settings configured on any given `gateway`.
~> **Note:** There is a hard limit of eight (8) instances per `gateway` and it can
~> **Note:** There is a hard limit of eight (8) instances per `gateway` and it can
not be overridden. This hard limit will probably be increased in the future.
- **Cross Namespace Reference Policies for Certificates:**
@ -31,7 +31,6 @@ description: >-
this release, Reference Policies are now required for TLS certificates when a
`listener` has a `certificateRef` that is in a different `namespace`.
## Supported Software
- Consul 1.11.2+