
This change allows creating a single ingress resource using the public fqdn of the service, instead of two (cluster and namespace) that is currently the case. Every openstack-helm chart can have a network.server.ingress.use_external_ingress_controller boolean field to choose the creation of a single ingress resource (ingressName-namespace-fqdn). Signed-off-by: Yanos Angelopoulos <yanos@admin.grnet.gr> Change-Id: I46da850fccc3fee76595a2e6c49d51197a282c3e
[MariaDB] Add liveness probe to restart a pod that got stuck in a transfer wsrep_local_state_comment
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 IRC: #openstack-helm on oftc
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on oftc
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.
Description
Languages
Smarty
82.3%
Shell
16%
Python
1.3%
Jinja
0.2%
Makefile
0.2%