iStio workloadentry sidecar a要求?

发布于 2025-01-27 07:10:19 字数 330 浏览 4 评论 0 原文

我有兴趣在我的ISTIO网关后面放置在AWS EC2实例中提供的应用程序。听起来,理想的情况是使用WorkloadEntry来定义端点,并使我可以轻松地将其放入群集等,等等。

在我阅读的文档中,提到在VM中使用Sidecar为此启用。我找不到的是如何在VM中使用边锋。吊舱中有很多关于边车的好东西,但是我不确定在VM上实施什么以及我将如何实现。也许边车所需的集成是要在第三方应用程序中实施复杂?也许没有边车,我可以做得更好?

我如何找到有关VM Sidecars的详细信息并将它们集成到网格中?

您什么时候决定将其作为WorkLoadEntry与仅仅是MESH_EXTERNAL SERVICENTRY?

I'm interested in putting a vendor provided application running in an AWS EC2 Instance behind my Istio gateway. It sounds like the ideal scenario is to use a WorkloadEntry to define the endpoint and make it easy to flex should I ever get this into the cluster, etc.

In the documentation I've read, there is mention of using a sidecar in the VM to enable this. What I've failed to find is how to use a sidecar in a VM. There's lots of good stuff about sidecars in a pod, but I'm not sure what it takes to implement on the VM and how I would even go about doing that. Maybe the integration needed for the sidecar would be to complex to implement in a 3rd party app? Maybe I can do this better without a Sidecar?

How do I find details on VM Sidecars and getting them integrated into the mesh?

When do you decide between implementing this as a WorkloadEntry vs simply a MESH_EXTERNAL ServiceEntry?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

a√萤火虫的光℡ 2025-02-03 07:10:19

如果要将VM集成到K8S ISTIO环境中,则需要在VM上设置ISTIO:

If you want to integrate a VM into your k8s Istio environment, you need to setup Istio on your VM :
https://istio.io/latest/docs/ops/deployment/vm-architecture/

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文