Azure Logic App在内部触发AKS服务 [英] Azure Logic App triggering AKS service internally

问题描述

是否可以触发在
AKS 来自
LogicApps ，
有什么东西暴露私有云内部的服务？

推荐答案

如果该服务已经通过外部公开LoadBalancer或Ingress，你可以直接调用它。如果仅从您的逻辑应用程序调用该服务，您可能希望保护它像

If that service is already exposed externally via LoadBalancer or Ingress, you can directly call it. If that service is to be called only from your Logic App, you might want to secure it like

- 仅允许Logic Apps传出IP为您的Ingress调用它（如果使用nginx-ingress ，这个

注释）或  LoadBalancer

- 可以作为查询参数或标题传递的基于令牌的身份验证

- 基本，客户端证书或逻辑应用程序中的HTTP操作支持的AAD OAuth

- Allow only Logic Apps Outgoing IPs to call it for your Ingress (if using nginx-ingress, this annotation) or LoadBalancer
- Token-based authentication that could be passed as a query parameter or header
- Basic, Client Certificates or AAD OAuth which are supported by the HTTP Action in Logic Apps

此外，根据您的要求，您可以
AKS部署到现有的VNET 中，您可以部署集成服务环境到同一个VNET
并且有您的Logic App部署在那里。从那里，您可以使用其Pod IP直接调用pod（如果pod重新启动但是只是想指出它会改变）或将其暴露为NodePort。

Also, depending on your requirement, you could have AKS deployed into an existing VNET wherein you could deploy an Integration Service Environment into the same VNET and have your Logic App deployed there. From there, you could either call the pod directly using its Pod IP (This would change if the pod restarts but just wanted to point it out) or expose it as NodePort.

这篇关于Azure Logic App在内部触发AKS服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！