Skip to content

Remove ability to specify external addresses in GenerateToken endpoint#14930

Merged
ndhanushkodi merged 5 commits intomainfrom
nd/peering-remove-server-external-addr
Oct 19, 2022
Merged

Remove ability to specify external addresses in GenerateToken endpoint#14930
ndhanushkodi merged 5 commits intomainfrom
nd/peering-remove-server-external-addr

Conversation

@ndhanushkodi
Copy link
Copy Markdown
Contributor

@ndhanushkodi ndhanushkodi commented Oct 10, 2022

Description

In Consul 1.13, we allowed setting external addresses for the server in the generate token endpoint, so when external load balancers were configured in front of the servers, those LB addresses could be used to dial the servers. With support for mesh gateways for peering establishment between servers, this is no longer needed, since the mesh gateways can be given wan addresses.

Links

This is a subtask of https://hashicorp.atlassian.net/browse/NET-1050

PR Checklist

  • external facing docs updated -- removed this param from api doc
  • not a security concern

@github-actions github-actions bot added the theme/api Relating to the HTTP API interface label Oct 10, 2022
@ndhanushkodi ndhanushkodi force-pushed the nd/peering-remove-server-external-addr branch from 01f4514 to db04ff3 Compare October 10, 2022 23:16
@ndhanushkodi ndhanushkodi requested a review from freddygv October 11, 2022 00:03
@ndhanushkodi ndhanushkodi marked this pull request as ready for review October 11, 2022 00:04
@ndhanushkodi ndhanushkodi requested a review from a team as a code owner October 11, 2022 00:04
Copy link
Copy Markdown
Contributor

@freddygv freddygv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly LGTM, left one question about some additional docs that may need to be updated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there may be some additional docs to update, the ones from this PR:
https://github.com/hashicorp/consul/pull/14191/files

../cluster-peering/k8s.mdx and ../k8s/helm.mdx

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup! I was thinking to update those as a separate docs PR since the K8s side PR for making/testing mesh gateways work is not yet merged.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK then you can go ahead and merge this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

theme/api Relating to the HTTP API interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants