多集群Kubernetes-跨集群通信 [英] Multi-Cluster Kubernetes - cross cluster communication
问题描述
不确定这是否是正确的地方，否则请指向其他论坛.
Not sure if this is the right place, please point me to a different forum if not.
在多集群kubernetes设置中，跨集群通信是有效的设计吗?特别地，一个群集中的容器依赖于另一群集中的容器.
In a multi-cluster kubernetes setup, is cross-cluster communication a valid design? In particular, a pod in one cluster relying on a pod in another cluster.
还是应该避免与此相关的限制或反模式? 如果没有，您将使用哪些工具来管理此部署并监视每个群集上的负载?
Or are there limitations or anti-patterns associated with this that we should avoid? If not, what tools do you use to manage this deployment and monitor load on each cluster?
推荐答案
多集群部署可为您提供更大程度的隔离和可用性，但会增加复杂性.如果您的系统具有高可用性要求，则可能需要跨多个区域和区域的集群.您可以在单个群集中进行金丝雀的配置更改或新的二进制发行版，其中配置更改只会影响少量的用户流量.此外，如果群集出现问题，您可以暂时将流量路由到附近的群集，直到解决该问题为止.
Multicluster deployments give you a greater degree of isolation and availability but increase complexity. If your systems have high availability requirements, you likely need clusters across multiple zones and regions. You can canary configuration changes or new binary releases in a single cluster, where the configuration changes only affect a small amount of user traffic. Additionally, if a cluster has a problem, you can temporarily route traffic to nearby clusters until you address the issue.
多个网格提供了以下功能单个网格:
Multiple meshes afford the following capabilities beyond that of a single mesh:
- 组织边界:业务范围
- 服务名称或名称空间重用:默认名称空间的多种不同用途
- 更强的隔离:将测试工作负载与生产工作负载隔离
我从KubeCon找到了非常不错的youtube视频，请检查一下，因为它确实说明了多集群的工作原理，特别是Matt Turner的第一个视频.
I have found a very good youtube videos from KubeCon, check it out because it really explains how multi-cluster works, specially the first one with Matt Turner.
- https://www.youtube.com/watch?v=FiMSr-fOFKU
- https://www.youtube.com/watch?v=-zsThiLvYos
查看海军上将，它可以为多集群Istio服务网格提供自动配置和服务发现
Check out Admiral which provides automatic configuration and service discovery for multicluster Istio service mesh
Istio具有非常强大的多集群功能.跨多个集群大规模管理此配置具有挑战性. Admiral对此配置持坚定态度，并提供跨群集的自动配置和同步.这消除了开发人员和网格操作员的复杂性，从而将这种复杂性推向了自动化.
Istio has a very robust set of multi-cluster capabilities. Managing this configuration across multiple clusters at scale is challenging. Admiral takes an opinionated view on this configuration and provides automatic provisioning and syncing across clusters. This removes the complexity from developers and mesh operators pushing this complexity into automation.
在多集群kubernetes设置中，跨集群通信是有效的设计吗?特别是，一个集群中的Pod依赖于另一个集群中的Pod.
In a multi-cluster kubernetes setup, is cross-cluster communication a valid design? In particular, a pod in one cluster relying on a pod in another cluster.
基于提供的链接和我的知识，一切都可以正常运行，pod可以依赖于另一个集群中的pod.
Based on provided links and my knowledge everything should work fine, pod can rely on a pod in another cluster.
更多有用的链接:
- https://istio.io/docs/ops/部署/部署模型/#multiple-clusters
- https://banzaicloud.com/blog/istio-multicluster-federation- 2/
- https://github.com/istio-ecosystem/coddiwomple
- https://github.com/istio-ecosystem/multi-mesh-examples
- https://istio.io/docs/ops/deployment/deployment-models/#multiple-clusters
- https://banzaicloud.com/blog/istio-multicluster-federation-2/
- https://github.com/istio-ecosystem/coddiwomple
- https://github.com/istio-ecosystem/multi-mesh-examples
Kubefed和Admiral的不同框架如何相互配合?我们可以同时使用还是仅使用其中之一?
how do the different frameworks of Kubefed and Admiral fit with each other? Can we use both or only use one?
就我所知，我不会使用kubefed，因为它确实处于alpha状态，除非您真的需要它.我不知道他们将如何一起工作，我只能假设他们都应该工作.
I would not use kubefed since it's in alpha as far as i know, unless you really need it. I dont know how both of them would work together, I can only assume that they should both work.
在决定不同的网格体系结构以促进跨集群通信时我们应该考虑什么?
what considerations should we have in deciding between different mesh architecture to facilitate cross-cluster communication?
上面有一个指向youtube视频的链接，介绍了istio Multi-Cluster Service Mesh Patterns，我想说由您决定要根据自己的需要使用哪个，最简单的一个是在视频，单个控制平面，单个网络. 有.
Above, there is a link to youtube video, istio Multi-Cluster Service Mesh Patterns Explained, I would say it's up to you to decide which one you want to use based on your needs, the simplest one is the first described in the video, single control plane, single network. More about it there.
这篇关于多集群Kubernetes-跨集群通信的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
