You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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
..
health_snapshot.go	peering: accept replication stream of discovery chain information at the importing side (#13151)	3 years ago
health_snapshot_test.go	peering: accept replication stream of discovery chain information at the importing side (#13151)	3 years ago
replication.go	Clean up imported nodes/services/checks as needed (#13367)	2 years ago
service.go	Fixup stream tear-down steps.	2 years ago
service_oss_test.go	peering: allow protobuf requests to populate the default partition or namespace (#13398)	3 years ago
service_test.go	Add leader routine to clean up peerings	2 years ago
stream_test.go	Clean up imported nodes/services/checks as needed (#13367)	2 years ago
stream_tracker.go	…
stream_tracker_test.go	add general runstep test helper instead of copying it all over the place (#13013)	3 years ago
subscription_blocking.go	peering: replicate discovery chains information to importing peers	3 years ago
subscription_manager.go	Update RBAC to handle imported services (#13404)	2 years ago
subscription_manager_test.go	peering: mesh gateways are required for cross-peer service mesh communication (#13410)	3 years ago
subscription_state.go	peering: mesh gateways are required for cross-peer service mesh communication (#13410)	3 years ago
subscription_state_test.go	peering: replicate expected SNI, SPIFFE, and service protocol to peers (#13218)	3 years ago
subscription_view.go	peering: mesh gateways are required for cross-peer service mesh communication (#13410)	3 years ago
subscription_view_test.go	peering: replicate discovery chains information to importing peers	3 years ago
testing.go	peering: accept replication stream of discovery chain information at the importing side (#13151)	3 years ago
testutil_oss_test.go	…
validate.go	peering: accept replication stream of discovery chain information at the importing side (#13151)	3 years ago
validate_test.go	Patches to peering initiation for POC demo (#13076)	3 years ago