Backport of Update existing docs from Consul API Gateway -> API Gateway for Kubernetes into release/1.15.x #16367
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-consul-core
force-pushed
the
backport/rename-apigw/jolly-communal-grizzly
branch
2 times, most recently
from
bc8237f to
b5d7e4b
Compare
github-actions
bot
added
the
type/docs
github-team-consul-core-pr-approver
approved these changes
Feb 22, 2023
hc-github-team-consul-core
deleted the
backport/rename-apigw/jolly-communal-grizzly
branch
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #16360 to be assessed for backporting due to the inclusion of the label type/docs-cherrypick.
The below text is copied from the body of the original PR.
Description
As we begin adding in documentation for API Gateway on VMs, the existing documentation will remain for API Gateway on Kubernetes. To avoid confusion, we want to rename the existing docs to reflect the environment that it's intended for.
Testing & Reproduction steps
Links
PR Checklist
Overview of commits