consul

Commit Graph

Author	SHA1	Message	Date
David Yu	cc5cbcba7c	Update single-dc-multi-k8s.mdx (#17126 )	2 years ago
Vipin John Wilson	c26b6bc037	First cluster grpc service should be NodePort for the second cluster to connect (#16430 ) * First cluster grpc service should be NodePort This is based on the issue opened here https://github.com/hashicorp/consul-k8s/issues/1903 If you follow the documentation https://developer.hashicorp.com/consul/docs/k8s/deployment-configurations/single-dc-multi-k8s exactly as it is, the first cluster will only create the consul UI service on NodePort but not the rest of the services (including for grpc). By default, from the helm chart, they are created as headless services by setting clusterIP None. This will cause an issue for the second cluster to discover consul server on the first cluster over gRPC as it cannot simply cannot through gRPC default port 8502 and it ends up in an error as shown in the issue https://github.com/hashicorp/consul-k8s/issues/1903 As a solution, the grpc service should be exposed using NodePort (or LoadBalancer). I added those changes required in both cluster1-values.yaml and cluster2-values.yaml, and also a description for those changes for the normal users to understand. Kindly review and I hope this PR will be accepted. * Update website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> * Update website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> * Update website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> --------- Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
Ashlee M Boyer	6e425f7428	docs: Migrate link formats (#15976 ) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>	2 years ago
Iryna Shustava	2be8b3326c	docs: remaining agentless docs updates (#15455 ) * Update servers-outside-kubernetes.mdx * Update single-dc-multi-k8s.mdx * update Vault data integration for snapshot agent * update k8s health checks page * remove all instances of controller.enabled in helm values examples * API Gateway update * Apply suggestions from code review Co-authored-by: Riddhi Shah <riddhi@hashicorp.com> * Apply suggestions from code review * Apply suggestions from code review * Cleaner diagram * added change around clients to workloads Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> Co-authored-by: boruszak <jeffrey.boruszak@hashicorp.com> Co-authored-by: Riddhi Shah <riddhi@hashicorp.com> Co-authored-by: David Yu <dyu@hashicorp.com>	2 years ago
boruszak	bcc227e285	/docs/k8s/deployment-configuration/	2 years ago
Kyle Schochenmaier	208dd1452a	[docs] use values.yaml instead of config.yaml everywhere for helm configurations (#14554 ) * use values.yaml instead of config.yaml everywhere for helm values * update docs	2 years ago
David Yu	7d580b3857	docs: small typos in single dc k8s clusters (#14484 ) * docs: small typos in single dc k8s clusters Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>	2 years ago
David Yu	97606d94a3	docs: Update single dc multiple k8s clusters doc (#14476 ) Co-authored-by: Jona Apelbaum <jona@hashicorp.com>	2 years ago
trujillo-adam	61291ef9c5	Docs cni plugin (#14009 ) Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>	2 years ago

9 Commits (a39760aeec8352edb7ba18e3de9365e4ede01f99)