6ca136bae4
When the ingress pod (in routed mode, using a managed vip) moves from one host to another, it is sometimes observed that: 1. the vip interface is not removed on the original host, and 2. in some network topologies, the switch fabric is unable to find the new pod. This change updates the ingress deployment as follows: Adds a 5s sleep before the shutdown of the ingress container in order to allow the preStop action of the ingress-vip container to run completely. Updates the start action of the ingress-vip-init container to check if the vip is part of an existing connected subnet, and if so, sends a few gratuitous ARP messages to let the switch fabric to build its ARP cache. Change-Id: I784906865358566f42157dc2133569e4cb270cfa |
||
---|---|---|
.. | ||
bin | ||
configmap-bin.yaml | ||
configmap-conf.yaml | ||
configmap-services-tcp.yaml | ||
configmap-services-udp.yaml | ||
deployment-error.yaml | ||
deployment-ingress.yaml | ||
endpoints-ingress.yaml | ||
ingress.yaml | ||
job-image-repo-sync.yaml | ||
network_policy.yaml | ||
service-error.yaml | ||
service-ingress-metrics-exporter.yaml | ||
service-ingress.yaml |