consul

Tree: 610038ce67

Author	SHA1	Message	Date
Luke Kysow	27dbb3e87d	Update index.mdx (#13476 )	2 years ago
Sam Salisbury	ceb1fdd80f	Merge pull request #13469 from hashicorp/correct-redhat-tags Correct redhat tags	2 years ago
Chris S. Kim	c66edb8af5	Update docs with Source.Peer field (#13463 )	2 years ago
Eric Haberkorn	130151bdf1	Lambda documentation tweaks (#13459 ) Lambda documentation tweaks	2 years ago
Sam Salisbury	2070d41fe9	correct redgat_tag ospid	2 years ago
Sam Salisbury	49a89e2b5a	strip trailing whitespace	2 years ago
John Cowen	7761d0abe4	ui: Fix intl keys in order to render correct messages for empty states (#13409 ) * ui: Fix intl keys in order to render correct messages for empty states * Add a debug only debug log to warn about missing keys	2 years ago
Tu Nguyen	2460925566	Fix broken link in lambda docs	2 years ago
Jeff Boruszak	da72911ba7	Additional consistency edits	2 years ago
Jeff Boruszak	b9917285ea	Apply suggestions from code review Co-authored-by: Nitya Dhanushkodi <nitya@hashicorp.com> Co-authored-by: Blake Covarrubias <blake@covarrubi.as>	2 years ago
Freddy	7e30357c17	Add peering endpoint API docs (#13454 )	2 years ago
R.B. Boyer	da8cea58c9	xds: begin refactor to always pass test snapshots through all xDS types (#13461 )	2 years ago
Nathan Coleman	f42f0fbe5f	Add note about expected status for invalid CertificateRef	2 years ago
R.B. Boyer	201d1458c3	xds: mesh gateways now have their own leaf certificate when involved in a peering (#13460 ) This is only configured in xDS when a service with an L7 protocol is exported. They also load any relevant trust bundles for the peered services to eventually use for L7 SPIFFE validation during mTLS termination.	2 years ago
Jeff Boruszak	343586e847	Update website/data/docs-nav-data.json Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
Jeff Boruszak	611ad5016e	Update website/content/docs/connect/cluster-peering/index.mdx	2 years ago
Jeff Boruszak	40e5d8b0ae	Apply suggestions from code review Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
boruszak	3e21f554ef	Limitations -> Constraints	2 years ago
Jeff Boruszak	e79aa5474f	Apply suggestions from code review Co-authored-by: Freddy <freddygv@users.noreply.github.com>	2 years ago
boruszak	2bc2f08d1d	typo fix	2 years ago
boruszak	ef4d603972	Switch fronend-service and backend-service	2 years ago
Jeff Boruszak	96fb08ef61	Apply suggestions from code review	2 years ago
Jeff Boruszak	e1277973aa	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>	2 years ago
Jeff Boruszak	fd81c4a412	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>	2 years ago
boruszak	e1b3cfc9a9	peering_token.json addition	2 years ago
Daniel Upton	72cdb203dc	docs: instructions for interacting with the private gRPC server locally	2 years ago
Riddhi Shah	411edc876b	[OSS] Support merge-central-config option in node services list API (#13450 ) Adds the merge-central-config query param option to the /catalog/node-services/:node-name API, to get a service definition in the response that is merged with central defaults (proxy-defaults/service-defaults). Updated the consul connect envoy command to use this option when retrieving the proxy service details so as to render the bootstrap configuration correctly.	2 years ago
Eric Haberkorn	0a9c1c0649	Lambda Beta Documentation (#13426 ) * Document the `enable_serverless_plugin` Agent Configuration Option (#13372) * Initial AWS Lambda documentation (#13245)	2 years ago
cskh	76855e20a0	Load test, upgrade packer version, fix k6s installation (#13382 ) - fix sg: need remote access to test server - Give the load generator a name - Update loadtest hcl filename in readme - Add terraform init - Disable access to the server machine by default	2 years ago
Jared Kirschner	226d089894	Merge pull request #13353 from hashicorp/jkirschner-hashicorp-patch-1 docs: show HCP Consul supports CTS enterprise	2 years ago
Jeff Boruszak	993cd2f3bc	Apply suggestions from code review Co-authored-by: Freddy <freddygv@users.noreply.github.com>	2 years ago
Evan Culver	7f8c650d61	connect: Use Envoy 1.22.2 instead of 1.22.1 (#13444 )	2 years ago
Jeff Boruszak	034861119a	Update website/content/docs/connect/cluster-peering/create-manage-peering.mdx Co-authored-by: Freddy <freddygv@users.noreply.github.com>	2 years ago
Jeff Boruszak	811674d526	Update website/content/docs/connect/cluster-peering/create-manage-peering.mdx	2 years ago
Jeff Boruszak	92d655e83d	Update website/content/docs/connect/cluster-peering/create-manage-peering.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	2 years ago
Jeff Boruszak	f0737c97dd	Update website/content/docs/connect/cluster-peering/index.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	2 years ago
boruszak	3141469ef7	Cluster Peering on Kubernetes page creation	2 years ago
boruszak	d2f0ddf8f6	Nav.json updates	2 years ago
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

... 3 4 5 6 7 ...

17788 Commits (610038ce670213055da323ecfc4f9cf06f4f430b) All Branches Search

17788 Commits (610038ce670213055da323ecfc4f9cf06f4f430b)

All Branches