Backport of [NET-11256] Add gateway list
command to consul-k8s CLI into release/1.6.x
#4439
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 #4433 to be assessed for backporting due to the inclusion of the label backport/1.6.x.
The below text is copied from the body of the original PR.
Note
This PR is blocked by the bug fix in #4434 which is preventing tests from passing
Changes proposed in this PR
This PR adds a new command,
consul-k8s gateway list
, which collects the various components of configuration for all Gateways in a given K8s cluster or namespace –Gateway
, attachedHTTPRoutes
, attachedTCPRoutes
, etc. – into a single zip file containing one yaml file per Gateway.It can output an archive named
gateways.zip
into the current directory, or it can output JSON to the terminal.How I've tested this PR
Create one or more Gateways in your Kube cluster. Example for this config is available here.
Run the commands above to inspect the various forms of output, making sure to use both the implicit namespace on your kubecontext and an explicit
--namespace <my-namespace>
arg.How I expect reviewers to test this PR
See above
Checklist
Overview of commits