Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Update docs for the release of Consul API Gateway v0.5 into release/1.13.x #15452

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #15015 to be assessed for backporting due to the inclusion of the label backport/1.13.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Description

This PR updates the Consul API Gateway documentation for 0.5. It covers added support for

  • routing traffic to services imported from a peered cluster
  • deploying the API gateway controller and gateways in a secondary federated datacenter
  • specifying Tolerations in the GatewayClassConfig
  • Kubernetes 1.24

It also breaks our single large usage page up into an extendable directory containing multiple use cases, one page for each.

PR Checklist

  • updated test coverage
  • external facing docs updated
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/docs/capigw-v0.5-peered-services-support/uniformly-trusted-bass branch from 73ca14e to 5044960 Compare November 17, 2022 23:43
@hashicorp-cla
Copy link

hashicorp-cla commented Nov 17, 2022

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


2 out of 3 committers have signed the CLA.

  • boruszak
  • trujillo-adam
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@trujillo-adam trujillo-adam added the type/docs Documentation needs to be created/updated/clarified label Nov 18, 2022
@trujillo-adam trujillo-adam merged commit e39cd16 into release/1.13.x Nov 18, 2022
@trujillo-adam trujillo-adam deleted the backport/docs/capigw-v0.5-peered-services-support/uniformly-trusted-bass branch November 18, 2022 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/docs Documentation needs to be created/updated/clarified
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants