17850 Commits (243519c8efe1382cda5b4851570ee38fa895b940)

 

All Branches   

Search

Author	SHA1	Message	Date
boruszak	b8ad96b516	Removing k8s updates on this branch	2 years ago
boruszak	62d1f949e5	Updated nav.json	2 years ago
Freddy	039cfec840	Merge pull request #13445 from hashicorp/peering/finalize-deletions	2 years ago
boruszak	740246797b	<CodeBlockConfig> fixes	2 years ago
boruszak	c5b5a6ee76	Code Block fixes	2 years ago
freddygv	f3843809da	Avoid deleting peerings marked as terminated. ... When our peer deletes the peering it is locally marked as terminated. This termination should kick off deleting all imported data, but should not delete the peering object itself. Keeping peerings marked as terminated acts as a signal that the action took place.	2 years ago
freddygv	6453375ab2	Add leader routine to clean up peerings ... Once a peering is marked for deletion a new leader routine will now clean up all imported resources and then the peering itself. A lot of the logic was grabbed from the namespace/partitions deferred deletions but with a handful of simplifications: - The rate limiting is not configurable. - Deleting imported nodes/services/checks is done by deleting nodes with the Txn API. The services and checks are deleted as a side-effect. - There is no "round rate limiter" like with namespaces and partitions. This is because peerings are purely local, and deleting a peering in the datacenter does not depend on deleting data from other DCs like with WAN-federated namespaces. All rate limiting is handled by the Raft rate limiter.	2 years ago
boruszak	923b7d0db6	Cluster Peering on Kubernetes initial draft	2 years ago
Nathan Coleman	5e9e1fb70f	Indent points specific to xRoute backend references	2 years ago
boruszak	be152b25c4	Cluster Peering on Kubernetes page creation	2 years ago
Evan Culver	ba6136eb42	connect: Update Envoy support matrix to latest patch releases (#13431)	2 years ago
Nathan Coleman	975a5e4b1f	Add docs for ReferencePolicy as it applies to Gateways	2 years ago
alex	a0a49ce2a6	peering: intentions list test (#13435)	2 years ago
Kyle Schochenmaier	765eb0453f	[docs] update terminating gateway docs for trust store path (#13432) ... * update terminating gateway docs for trust store * Update website/content/docs/k8s/connect/terminating-gateways.mdx Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
Jeff Boruszak	fb916e999b	Fixing double-ticks `	2 years ago
Jeff Boruszak	c39bf49eab	Added nav data	2 years ago
boruszak	084dc1c6e5	Removing Kubernetes page - will submit separate PR for timing reason	2 years ago
boruszak	b0430df680	Typo fix	2 years ago
boruszak	61f60ceb4f	Create and Manage Peering Connections additional fixes	2 years ago
Sarah Alsmiller	a9c25eb417	light restructureing/fixed some copypasta	2 years ago
boruszak	ebe0f5408d	What is Cluster Peering? additional fixes	2 years ago
Sarah Alsmiller	ba7115a1df	updated referencepolicy to referencegrant, added v0.3.0 upgrade instructions	2 years ago
boruszak	0ddcd78ec1	Create and Manage Peering Connections page	2 years ago
Freddy	9890dfac95	Merge pull request #13430 from hashicorp/peering/deletion	2 years ago
boruszak	de4f9bcf4a	What is Cluster Peering? additional fixes	2 years ago
boruszak	4fd06dff17	What is Cluster Peering? page	2 years ago
freddygv	20955742a7	Fixup api test	2 years ago
freddygv	6c8ab1bbac	Fixup stream tear-down steps. ... 1. Fix a bug where the peering leader routine would not track all active peerings in the "stored" reconciliation map. This could lead to tearing down streams where the token was generated, since the ConnectedStreams() method used for reconciliation returns all streams and not just the ones initiated by this leader routine. 2. Fix a race where stream contexts were being canceled before termination messages were being processed by a peer. Previously the leader routine would tear down streams by canceling their context right after the termination message was sent. This context cancelation could be propagated to the server side faster than the termination message. Now there is a change where the dialing peer uses CloseSend() to signal when no more messages will be sent. Eventually the server peer will read an EOF after receiving and processing the preceding termination message. Using CloseSend() is actually not enough to address the issue mentioned, since it doesn't wait for the server peer to finish processing messages. Because of this now the dialing peer also reads from the stream until an error signals that there are no more messages. Receiving an EOF from our peer indicates that they processed the termination message and have no additional work to do. Given that the stream is being closed, all the messages received by Recv are discarded. We only check for errors to avoid importing new data.	2 years ago
freddygv	cc921a9c78	Update peering state and RPC for deferred deletion ... When deleting a peering we do not want to delete the peering and all imported data in a single operation, since deleting a large amount of data at once could overload Consul. Instead we defer deletion of peerings so that: 1. When a peering deletion request is received via gRPC the peering is marked for deletion by setting the DeletedAt field. 2. A leader routine will monitor for peerings that are marked for deletion and kick off a throttled deletion of all imported resources before deleting the peering itself. This commit mostly addresses point #1 by modifying the peering service to mark peerings for deletion. Another key change is to add a PeeringListDeleted state store function which can return all peerings marked for deletion. This function is what will be watched by the deferred deletion leader routine.	2 years ago
boruszak	bb972974cb	Initial page creation	2 years ago
Freddy	71b254522e	Clean up imported nodes/services/checks as needed (#13367) ... Previously, imported data would never be deleted. As nodes/services/checks were registered and deregistered, resources deleted from the exporting cluster would accumulate in the imported cluster. This commit makes updates to replication so that whenever an update is received for a service name we reconcile what was present in the catalog against what was received. This handleUpdateService method can handle both updates and deletions.	2 years ago
Nathan Coleman	ce3d49237d	Merge pull request #13333 from hashicorp/docs/capig-instances-config ... docs: Consul API Gateway scaling config	2 years ago
Mark Anderson	edbf19f4e8	Merge pull request #13357 from hashicorp/ma/add-build-date-oss ... Add build date (oss)	2 years ago
Mark Anderson	a5efa461dd	Fix infinite recursion in bash_env ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Chris S. Kim	a02e9abcc1	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.	3 years ago
R.B. Boyer	f557509e58	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.	3 years ago
Kyle Havlovitz	3f0de89a28	Merge pull request #13421 from hashicorp/dns-node-query-partitions ... OSS: Add dns node lookup support in partitions	3 years ago
Kyle Havlovitz	14119d372d	Add changelog note	3 years ago
Kyle Havlovitz	7f62571419	Add dns node lookup support in partitions	3 years ago
Mark Anderson	9e27cc02d9	Merge pull request #13316 from hashicorp/ma/vault-docs-report-backport ... Update website/content/docs/connect/ca/vault.mdx	3 years ago
R.B. Boyer	7001e1151c	peering: rename initiate to establish in the context of the APIs (#13419)	3 years ago
Mark Anderson	175728b292	Minor cleanup for build-date script ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	dd22ceccd1	Change default dates ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	45190d355b	Add changelog ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	f65093f1c6	Fixup some more tests ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	61a8995847	Fix issue with consul version tests ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	6eecb7cf80	Set default for build date ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	9343e05498	Fix build-date to use UTC ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	19c87be3a6	Add build date to self endpoint ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago
Mark Anderson	ec060e5e37	Build date in config file ... Signed-off-by: Mark Anderson <manderson@hashicorp.com>	3 years ago