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
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.