[英]kubernetes loadbalancer service - unable to set ingress ip
I updated my k8 cluster to 1.18 recently.我最近将我的 k8 集群更新到 1.18。 Afterwards I had to recreate a (previously functional) loadBalancer service.
之后我不得不重新创建一个(以前的功能)loadBalancer 服务。 It seemed to come up properly but I was unable to access the external ip afterwards.
它似乎正常出现,但之后我无法访问外部 ip。 Looking at the dump from
kubectl describe service
I don't see a field for "loadbalancer ingress" that I see on other services that didn't get restarted.查看来自
kubectl describe service
的转储,我没有看到在其他未重新启动的服务上看到的“负载均衡器入口”字段。
apiVersion: v1
kind: Service
metadata:
name: search-master
labels:
app: search
role: master
spec:
selector:
app: search
role: master
ports:
- protocol: TCP
port: 9200
targetPort: 9200
name: serviceport
- port: 9300
targetPort: 9300
name: dataport
type: LoadBalancer
loadBalancerIP: 10.95.96.43
I tried adding this (to no avail):我尝试添加这个(无济于事):
status:
loadBalancer:
ingress:
- ip: 10.95.96.43
What have I missed here?我在这里错过了什么?
Another odd thing: when I dump the service as yaml I get this entry at the top:另一个奇怪的事情:当我将服务转储为 yaml 时,我在顶部看到了这个条目:
apiVersion: v1
items:
- apiVersion: v1
kind: Service
...
spec:
clusterIP: <internal address>
...
type: LoadBalancer
status:
loadBalancer: {}
kind: List
metadata:
resourceVersion: ""
selfLink: ""
Something wrong with my yml?我的 yml 有问题吗?
For a distant observer - this is likely due to metallb version conflict.对于遥远的观察者 - 这可能是由于 metallb 版本冲突。 Note that 1.17-> 1.18 introduces some breaking changes.
请注意,1.17-> 1.18 引入了一些重大更改。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.