Kubernetes tls 主机与入口主机不同
目前正在 kubernetes 集群中处理一些入口,入口中有 2 台主机。我想知道为什么 tls-host 与 Rules:host 不同?
spec:
rules:
- host: test1.something.se
http:
paths:
- pathType: Prefix
path: /
backend:
service:
name: my-service
port:
number: 5000
tls:
- hosts:
- test2.something.se
secretName: tls-secret
Currently working on some ingress in kubernetes cluster, in ingress there are 2 hosts. I am wondering why is tls-host different from rules:host?
spec:
rules:
- host: test1.something.se
http:
paths:
- pathType: Prefix
path: /
backend:
service:
name: my-service
port:
number: 5000
tls:
- hosts:
- test2.something.se
secretName: tls-secret
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
这表明主机
test2.something.se
启用了 https 流量,并且证书存储在tls-secret
密钥中,因为我没有看到指定的规则host,或后备默认规则,test2 的流量将为 404。
test1.something.se
的流量将不会启用 https,因为其主机名不在tls.hosts
列表That indicates that the host
test2.something.se
has https traffic enabled, and the certificate is stored in thetls-secret
secretSince I don't see a rule specifying that host, or a fallback default rule, traffic for test2 will 404.
Traffic for
test1.something.se
will not be https enabled because its hostname isn't under thetls.hosts
list