From 6bf3a405ee7d306d2fdbf69d0e72676f7e865feb Mon Sep 17 00:00:00 2001 From: Sarah Alsmiller Date: Fri, 5 Aug 2022 10:16:41 -0500 Subject: [PATCH] render issue --- website/content/docs/api-gateway/usage.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/content/docs/api-gateway/usage.mdx b/website/content/docs/api-gateway/usage.mdx index 7f4c3631a..83779a188 100644 --- a/website/content/docs/api-gateway/usage.mdx +++ b/website/content/docs/api-gateway/usage.mdx @@ -14,21 +14,21 @@ This topic describes the basic workflow for implementing Consul API Gateway conf 1. Verify that the Consul API Gateway CRDs and controller have been installed and applied (see [Installation](/docs/api-gateway/consul-api-gateway-install)). 1. Configure your [`Gateway`](/docs/api-gateway/configuration/gateway) and [`Routes`](/docs/api-gateway/configuration/routes) . as describe in the [Configuration](/docs/api-gateway/configuration) section. - + - ```yaml - apiGateway: - enabled: true - managedGatewayClass: - ``` + ```yaml + apiGateway: + enabled: true + managedGatewayClass: + ``` - + 1. Issue the `kubectl apply` command to implement the configurations, e.g.: -```shell-session -$ kubectl apply -f gateway.yaml routes.yaml -``` + ```shell-session + $ kubectl apply -f gateway.yaml routes.yaml + ```