kubernetes可以使用https的桥梁外部名称服务
我需要将EKS部署连接到AWS Opensearch(Akka Elasticsearch)。连接很好,但是由于我的OpenSearch实例需要HTTPS连接,因此应用程序未将连接视为安全。
apiVersion: v1
kind: Service
metadata:
name: opensearch-service
namespace: development
status:
loadBalancer: {}
spec:
ports:
- protocol: TCP
port: 443
targetPort: 443
type: ExternalName
sessionAffinity: None
externalName: my_internal_aws_url_for_elasticsearch.es.amazonaws.com
internalTrafficPolicy: Cluster
连接很好,如果我尝试连接忽略证书的连接,则连接很好:
curl -k https://opensearch-service
因此,是否有一种方法可以使HTTPS使用服务正常工作以连接到外部名称?
I need to connect an EKS deployment to Aws OpenSearch(akka Elasticsearch). The connection is fine, however since my Opensearch instance requires Https connection the application is not considering the connection as secure.
apiVersion: v1
kind: Service
metadata:
name: opensearch-service
namespace: development
status:
loadBalancer: {}
spec:
ports:
- protocol: TCP
port: 443
targetPort: 443
type: ExternalName
sessionAffinity: None
externalName: my_internal_aws_url_for_elasticsearch.es.amazonaws.com
internalTrafficPolicy: Cluster
The connection is fine, if I try to connect ignoring the certificate the connection is fine:
curl -k https://opensearch-service
So, Is there a way to keep the Https working properly using a Service to connect to external name?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论