Azure AKS 上的 Istio 多集群主远程

发布于 2025-01-20 14:08:52 字数 4360 浏览 2 评论 0原文

我正在尝试创建多群集ISTIO主示例。

首先创建了两个集群Azure Aks。用于网络配置的Azurecni和以下是集群的设置。

第一个群集

vnet istioclusterone - 10.10.0.0/20
subnet default - 10.10.0.0/20
k8s service address range 10.100.0.0/16
DNS service ip - 10.100.0.10
Docker Bridge address - 172.17.0.1/16
DNS-prefix - app-cluster-dns

第二个群集

vnet istioclusterone - 10.11.0.0/20
subnet default - 10.11.0.0/20
k8s service address range 10.101.0.0/16
DNS service ip - 10.101.0.10
Docker Bridge address - 172.18.0.1/16
DNS-prefix - processing-cluster-dns

除此之外,

除了默认设置而消失。接下来的下面是文章以设置多ISTIO群集。

priendar-remote

第二个文章中的最后一步设置了cluster2,因为远程失败了。

在Istio-ingressgateway Pod的日志中找到以下错误。


2022-04-11T07:51:00.352057Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 431s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")"
2022-04-11T07:51:08.514428Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 439s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")"
2022-04-11T07:51:12.462140Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 443s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")"
2022-04-11T07:51:39.950935Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 471s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")" 

有没有人尝试过这种情况,请分享您的见解。

谢谢。

更新:

已经解决了两个簇的自定义证书。

然后在两个簇中创建了一个网关。

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: cluster-aware-gateway
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway
  servers:
  - port:
      number: 443
      name: tls
      protocol: TLS
    tls:
      mode: AUTO_PASSTHROUGH
    hosts:
    - "*.local"

现在有新的错误。在下面查看cluster2的Pod istio-ingressgateway-575ccb4d79的日志。

2022-04-13T09:14:04.650502Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 60s ago: 14, connection error: desc = "transport: Error while dialing dial tcp <publicIPofEastWestgateway>:15012: i/o timeout"
2022-04-13T09:14:27.026016Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 83s ago: 14, connection error: desc = "transport: Error while dialing dial tcp <publicIPofEastWestgateway:15012: i/o timeout"

我在这里承担的措施,我在cluster1中安装了EastWestgateway,如文档 linktodoc

cluster2试图访问cluster1。使用失败的港口15012上的East West-Gateway的Publicip。

打开检查的安全组端口。从群集内的测试吊舱中尝试了telnet进行检查。它的失败。

任何人都可以在这里帮助我。

谢谢

I am trying to create multi cluster istio primary-remote.

First created two clusters AZURE AKS. Used AzureCNI for Network Configuaration and following are the settings of the cluster.

First cluster

vnet istioclusterone - 10.10.0.0/20
subnet default - 10.10.0.0/20
k8s service address range 10.100.0.0/16
DNS service ip - 10.100.0.10
Docker Bridge address - 172.17.0.1/16
DNS-prefix - app-cluster-dns

Second cluster

vnet istioclusterone - 10.11.0.0/20
subnet default - 10.11.0.0/20
k8s service address range 10.101.0.0/16
DNS service ip - 10.101.0.10
Docker Bridge address - 172.18.0.1/16
DNS-prefix - processing-cluster-dns

Other than this gone with default settings.

Next Followed below articles to setup multi Istio cluster.

Before you begin

Primary-remote

last step in second article to setup cluster2 as remote is failed.

enter image description here

Found below errors in logs of istio-ingressgateway pod.


2022-04-11T07:51:00.352057Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 431s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")"
2022-04-11T07:51:08.514428Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 439s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")"
2022-04-11T07:51:12.462140Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 443s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")"
2022-04-11T07:51:39.950935Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 471s ago: 14, connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"cluster.local\")" 

Has anyone tried this scenario please share your insights.

Thanks.

Update:

Have used custom certs for both the clusters previous error was solved.

then created a gateway in both the clusters.

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: cluster-aware-gateway
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway
  servers:
  - port:
      number: 443
      name: tls
      protocol: TLS
    tls:
      mode: AUTO_PASSTHROUGH
    hosts:
    - "*.local"

Now getting new error. check below logs of pod istio-ingressgateway-575ccb4d79 of cluster2.

2022-04-13T09:14:04.650502Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 60s ago: 14, connection error: desc = "transport: Error while dialing dial tcp <publicIPofEastWestgateway>:15012: i/o timeout"
2022-04-13T09:14:27.026016Z     warning envoy config    StreamAggregatedResources gRPC config stream closed since 83s ago: 14, connection error: desc = "transport: Error while dialing dial tcp <publicIPofEastWestgateway:15012: i/o timeout"

what I undertood here, I have an eastwestgateway installed in cluster1 as in the documentation linkToDoc

cluster2 is trying to access cluster1. using publicIp of eastwest-gateway on port 15012 which is failing.

checked security groups port is opened. Tried telnet from a test pod from within the cluster to check. its failing.

enter image description here

can anyone help me here.

Thanks

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

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

发布评论

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

评论(1

过期以后 2025-01-27 14:08:52

这看起来像是防火墙问题。不确定它是否有帮助,但尝试在远程集群的出站上打开端口 15012 和 15443 到 eastwestgateway elb ip(主集群)

It looks like a firewall issue. not sure if it'll help, but try opening the ports 15012 and 15443 on the remote cluster's outbound, to the eastwestgateway elb ip (primary cluster)

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