mirror of
https://github.com/optim-enterprises-bv/openstack-helm-infra.git
synced 2026-01-13 02:35:05 +00:00
b482b57e6e
The mariadb container launches two threads in addition to the mysql daemon, one to mantain a configmap containing the Galera Cluster state, and the other to handle leader elections. These threads die if they suffer any exceptions talking to the kubernetes apiserver. This can happen sometimes, e.g. when a k8s control node reboots. This change logs and ignores the kubernetes.client.rest.ApiException, allowing the threads to retry and hopefully succeed once the k8s api becomes available. Change-Id: I5745a763bb07f719d83a41c1f27be2b76ce998e9
==================== 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_. .. _repository: https://github.com/openstack/openstack-helm Communication ------------- * Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - #openstack-helm * Join us on `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: #openstack-helm on freenode * Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode * Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-helm-meeting-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. * `Bugs <https://storyboard.openstack.org/#!/project/openstack/openstack-helm-infra>`_ * `Blueprints <https://blueprints.launchpad.net/openstack-helm>`_