mirror of https://github.com/status-im/consul.git
Crosslink new microservices collection. (#9704)
This commit is contained in:
parent
17effdeb28
commit
0ea2cf33be
|
@ -57,6 +57,12 @@ There are several ways to try Consul with Kubernetes in different environments.
|
|||
chart, deploying services in the service mesh, and using intentions to secure service
|
||||
communications.
|
||||
|
||||
- The [Migrate to Microservices with Consul Service Mesh on Kubernetes](https://learn.hashicorp.com/collections/consul/microservices?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS)
|
||||
collection uses an example application written by a fictional company to illustrate why and how organizations can
|
||||
migrate from monolith to microservices using Consul service mesh on Kubernetes. The case study in this collection
|
||||
should provide information valuable for understanding how to develop services that leverage Consul during any stage
|
||||
of your microservices journey.
|
||||
|
||||
- The [Consul and Minikube guide](https://learn.hashicorp.com/tutorials/consul/kubernetes-minikube?utm_source=consul.io&utm_medium=docs) is a quick step-by-step guide for deploying Consul with the official Helm chart on a local instance of Minikube.
|
||||
|
||||
- Review production best practices and cloud-specific configurations for deploying Consul on managed Kubernetes runtimes.
|
||||
|
|
|
@ -318,3 +318,11 @@ catalog syncing feature with Services rather than pods.
|
|||
-> **Note:** Due to a limitation of anti-affinity rules with DaemonSets,
|
||||
a client-mode agent runs alongside server-mode agents in Kubernetes. This
|
||||
duplication wastes some resources, but otherwise functions perfectly fine.
|
||||
|
||||
## Next Steps
|
||||
|
||||
If you are still considering a move to Kubernetes, or to Consul on Kubernetes specifically, our [Migrate to Microservices with Consul Service Mesh on Kubernetes](https://learn.hashicorp.com/collections/consul/microservices?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS)
|
||||
collection uses an example application written by a fictional company to illustrate why and how organizations can
|
||||
migrate from monolith to microservices using Consul service mesh on Kubernetes. The case study in this collection
|
||||
should provide information valuable for understanding how to develop services that leverage Consul during any stage
|
||||
of your microservices journey.
|
||||
|
|
|
@ -392,3 +392,9 @@ With your Kubernetes clusters federated, try out using Consul service mesh to
|
|||
route between services deployed on each cluster by following our Learn tutorial: [Secure and Route Service Mesh Communication Across Kubernetes](https://learn.hashicorp.com/tutorials/consul/kubernetes-mesh-gateways#deploy-microservices).
|
||||
|
||||
You can also read our in-depth documentation on [Consul Service Mesh In Kubernetes](/docs/k8s/connect).
|
||||
|
||||
If you are still considering a move to Kubernetes, or to Consul on Kubernetes specifically, our [Migrate to Microservices with Consul Service Mesh on Kubernetes](https://learn.hashicorp.com/collections/consul/microservices?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS)
|
||||
collection uses an example application written by a fictional company to illustrate why and how organizations can
|
||||
migrate from monolith to microservices using Consul service mesh on Kubernetes. The case study in this collection
|
||||
should provide information valuable for understanding how to develop services that leverage Consul during any stage
|
||||
of your microservices journey.
|
||||
|
|
Loading…
Reference in New Issue