Skip to content

Update single-dc-multi-k8s to require flat network#17126

Merged
david-yu merged 1 commit into
mainfrom
docs/address-multicluster-singledc-docs
Apr 25, 2023
Merged

Update single-dc-multi-k8s to require flat network#17126
david-yu merged 1 commit into
mainfrom
docs/address-multicluster-singledc-docs

Conversation

@david-yu
Copy link
Copy Markdown
Contributor

Description

Addresses the following issue: #16849

Testing & Reproduction steps

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

@david-yu david-yu requested a review from a team as a code owner April 25, 2023 16:24
@github-actions github-actions Bot added the type/docs Documentation needs to be created/updated/clarified label Apr 25, 2023
@david-yu david-yu added backport/1.12 pr/no-changelog PR does not need a corresponding .changelog entry and removed backport/1.12 labels Apr 25, 2023
Copy link
Copy Markdown
Contributor

@jkirschner-hashicorp jkirschner-hashicorp left a comment

Choose a reason for hiding this comment

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

@david-yu : Approving with one thing to consider --- should we mention that if connecting multiple Kubernetes clusters with a non-flat network, they should consider Consul Enterprise admin partitions (and link to a relevant page)?

@david-yu
Copy link
Copy Markdown
Contributor Author

Approving with one thing to consider --- should we mention that if connecting multiple Kubernetes clusters with a non-flat network, they should consider Consul Enterprise admin partitions (and link to a relevant page)?

Yes that is already at the top of the page with a warning/hot tip.

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

Labels

pr/no-changelog PR does not need a corresponding .changelog entry type/docs Documentation needs to be created/updated/clarified

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consul Service Mesh not working in Single Consul Datacenter Across Multiple Kubernetes Clusters

2 participants