60f6948b0a
Apply suggestions from code review
...
Co-authored-by: David Yu <dyu@hashicorp.com>
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2022-06-21 16:13:39 -07:00
23e4884779
Merge pull request #13448 from hashicorp/docs-cluster-peering-k8s-technical-preview
...
docs: Cluster Peering for Kubernetes Technical Preview
2022-06-21 10:18:13 -07:00
3ded4522fb
Apply suggestions from code review
...
Co-authored-by: Freddy <freddygv@users.noreply.github.com>
2022-06-20 15:28:50 -05:00
902e76d304
Additional service mesh docs updates for peering ( #13464 )
...
This PR covers two sets of changes:
- Documenting the new `destination_peer` for proxy upstream definitions.
- Updating the exported-services config entry documentation.
Updates to the `exported-services` config entry include:
- As of 1.13.0 it is no longer only for Consul Enterprise
- A `PeerName` is now a possible consumer for an exported service.
- Added examples for OSS and Enterprise
- Linked to peering docs
2022-06-17 18:40:38 -06:00
1e6ddc8f82
Apply suggestions from code review
2022-06-17 13:36:20 -05:00
4c520323a5
Update website/content/docs/connect/cluster-peering/create-manage-peering.mdx
2022-06-17 12:35:35 -05:00
85463445b4
Apply suggestions from code review
...
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2022-06-17 12:31:11 -05:00
42f7d6a403
Update docs with peer query parameter ( #13462 )
...
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
2022-06-16 16:25:44 -04:00
4b0ffb227a
Update docs with Source.Peer field ( #13463 )
2022-06-16 09:30:05 -04:00
93a50d5b12
Additional consistency edits
2022-06-15 16:25:57 -05:00
8bd57c75fe
Apply suggestions from code review
...
Co-authored-by: Nitya Dhanushkodi <nitya@hashicorp.com>
Co-authored-by: Blake Covarrubias <blake@covarrubi.as>
2022-06-15 16:15:03 -05:00
082bc3632b
Add peering endpoint API docs ( #13454 )
2022-06-15 14:18:14 -06:00
3b85a9dda2
Update website/data/docs-nav-data.json
...
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2022-06-15 14:26:54 -05:00
627173110b
Update website/content/docs/connect/cluster-peering/index.mdx
2022-06-15 14:26:40 -05:00
1a6eea4fc3
Apply suggestions from code review
...
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2022-06-15 14:23:18 -05:00
b00262381b
Limitations -> Constraints
2022-06-15 14:21:58 -05:00
08716c5279
Apply suggestions from code review
...
Co-authored-by: Freddy <freddygv@users.noreply.github.com>
2022-06-15 14:19:03 -05:00
37acf49357
typo fix
2022-06-15 14:08:34 -05:00
80f779a528
Switch fronend-service and backend-service
2022-06-15 14:07:56 -05:00
e8d34bab68
Apply suggestions from code review
2022-06-15 14:04:52 -05:00
c23ab4259e
Apply suggestions from code review
...
Co-authored-by: Blake Covarrubias <blake@covarrubi.as>
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2022-06-15 14:01:34 -05:00
199e9a900a
Apply suggestions from code review
...
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
Co-authored-by: Blake Covarrubias <blake@covarrubi.as>
2022-06-15 13:56:55 -05:00
1c7d51f9d9
peering_token.json addition
2022-06-15 13:55:53 -05:00
caa2dc5bfb
Apply suggestions from code review
...
Co-authored-by: Freddy <freddygv@users.noreply.github.com>
2022-06-14 17:34:21 -05:00
687c16b9e0
Update website/content/docs/connect/cluster-peering/create-manage-peering.mdx
...
Co-authored-by: Freddy <freddygv@users.noreply.github.com>
2022-06-14 17:29:30 -05:00
9a8235993a
Update website/content/docs/connect/cluster-peering/create-manage-peering.mdx
2022-06-14 17:28:06 -05:00
fe0a5491d2
Update website/content/docs/connect/cluster-peering/create-manage-peering.mdx
...
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
2022-06-14 17:27:03 -05:00
24409fa40b
Update website/content/docs/connect/cluster-peering/index.mdx
...
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
2022-06-14 17:23:07 -05:00
e22171cdbf
Cluster Peering on Kubernetes page creation
2022-06-14 17:15:14 -05:00
72b91c3481
Nav.json updates
2022-06-14 17:14:34 -05:00
703ce412c7
Removing k8s updates on this branch
2022-06-14 17:12:45 -05:00
b9a4ff73ce
Updated nav.json
2022-06-14 17:01:48 -05:00
8687f1511e
<CodeBlockConfig> fixes
2022-06-14 16:58:07 -05:00
0b60e6b539
Code Block fixes
2022-06-14 16:55:25 -05:00
c901667dd4
Cluster Peering on Kubernetes initial draft
2022-06-14 16:33:29 -05:00
0bffbc429c
Cluster Peering on Kubernetes page creation
2022-06-14 16:15:57 -05:00
2e5163dfdc
Fixing double-ticks `
2022-06-14 10:00:22 -05:00
3097f4d00f
Added nav data
2022-06-13 17:27:11 -05:00
0c1b6d77d8
Removing Kubernetes page - will submit separate PR for timing reason
2022-06-13 16:47:47 -05:00
ad4712334d
Typo fix
2022-06-13 16:42:29 -05:00
00e648ab89
Create and Manage Peering Connections additional fixes
2022-06-13 16:38:44 -05:00
ecdb4cda96
What is Cluster Peering? additional fixes
2022-06-13 16:06:29 -05:00
fb573f7801
Create and Manage Peering Connections page
2022-06-13 14:24:02 -05:00
4b306efd94
What is Cluster Peering? additional fixes
2022-06-13 13:41:57 -05:00
d3fd58ad8e
What is Cluster Peering? page
2022-06-13 13:31:13 -05:00
b8b9be4d56
Initial page creation
2022-06-13 12:58:16 -05:00
6cb05666e6
Merge pull request #13357 from hashicorp/ma/add-build-date-oss
...
Add build date (oss)
2022-06-13 08:43:20 -07:00
a7a21abe47
Fix infinite recursion in bash_env
...
Signed-off-by: Mark Anderson <manderson@hashicorp.com>
2022-06-10 20:24:15 -07:00
4cb251497f
Update RBAC to handle imported services ( #13404 )
...
When converting from Consul intentions to xds RBAC rules, services imported from other peers must encode additional data like partition (from the remote cluster) and trust domain.
This PR updates the PeeringTrustBundle to hold the sending side's local partition as ExportedPartition. It also updates RBAC code to encode SpiffeIDs of imported services with the ExportedPartition and TrustDomain.
2022-06-10 17:15:22 -04:00
4626b65124
xds: allow for peered upstreams to use tagged addresses that are hostnames ( #13422 )
...
Mesh gateways can use hostnames in their tagged addresses (#7999 ). This is useful
if you were to expose a mesh gateway using a cloud networking load balancer appliance
that gives you a DNS name but no reliable static IPs.
Envoy cannot accept hostnames via EDS and those must be configured using CDS.
There was already logic when configuring gateways in other locations in the code, but
given the illusions in play for peering the downstream of a peered service wasn't aware
that it should be doing that.
Also:
- ensuring that we always try to use wan-like addresses to cross peer boundaries.
2022-06-10 16:11:40 -05:00
Tu Nguyen