From ac04a1251f146f09c4512e04b9178fe5d0aeb2a6 Mon Sep 17 00:00:00 2001 From: trujillo-adam Date: Wed, 27 Apr 2022 11:34:44 -0700 Subject: [PATCH] hid copy fn for codeblocks that don't need it --- .../content/docs/api-gateway/upgrade-specific-versions.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/content/docs/api-gateway/upgrade-specific-versions.mdx b/website/content/docs/api-gateway/upgrade-specific-versions.mdx index be8be51b36..338604f5f4 100644 --- a/website/content/docs/api-gateway/upgrade-specific-versions.mdx +++ b/website/content/docs/api-gateway/upgrade-specific-versions.mdx @@ -98,6 +98,8 @@ Ensure that the following requirements are met prior to upgrading: If a `namespace` field is not defined in the `backendRef` or if the namespace matches the namespace of the route, then no additional action is required for the `backendRef`. Otherwise, note the `group`, `kind`, `name`, and `namespace` field values for `backendRef` configurations that have a `namespace` defined that do not match the namespace of the parent route. You must also note the `kind` and `namespace` of the parent route. You will need these to create a `ReferencePolicy` that explicitly allows each cross-namespace route-to-service pair to prevent the route from breaking (see [step 5](#create-reference-policy)). After completing this step, you will have a list of all routes similar to the following: + + ```yaml example-http-route: @@ -118,6 +120,7 @@ Ensure that the following requirements are met prior to upgrading: name: web-backend namespace: gateway-namespace ``` + Skip to [step 8](#step-8) if your list is empty. @@ -132,6 +135,8 @@ Ensure that the following requirements are met prior to upgrading: The output will resemble the following response if routes that require a new `ReferencePolicy` are returned: + + ```log { "name": "example-http-route", @@ -160,6 +165,7 @@ Ensure that the following requirements are met prior to upgrading: } } ``` + If your output is empty, skip to [step 8](#step-8).