9a28908d54
Currently, the OSH uses main uWSGI app to serve responses to the Kubernetes readiness and liveness probes. Unfortunately, this is not sustainable during load. When all of the uWSGI workers are occupied with work for longer than the probe timeout, the liveness probe fails as the request is queued up for too long. This change proposes alternative solution of running the liveness probes against an uWSGI stats endpoint which is a lightweight endpoint served by the master process and is not affected by the workers being busy. It enables the uWSGI stats server on port 1717 in each of the relevant pods and updates the deployments to use the port exposed by those endpoints. This change allows the deployment to use a liveness port that is different from the one dynamically looked up in service catalog. Readiness probes will remain unchanged as it makes sense to check actual application on start. Change-Id: Ie466aafeb4edef72ae1591d91a0f1583636a757c Signed-off-by: Marek Skrobacki <marek.skrobacki@rackspace.co.uk>
OpenStack-Helm
Mission
The goal of OpenStack-Helm is to provide a collection of Helm charts that simply, resiliently, and flexibly deploy OpenStack and related services on Kubernetes.
Versions supported
The table below shows the combinations of the Openstack/Platform/Kubernetes versions that are tested and proved to work.
| Openstack version | Host OS | Image OS | Kubernetes version |
|---|---|---|---|
| 2024.1 (Caracal) | Ubuntu Jammy | Ubuntu Jammy | >=1.29,<=1.31 |
| 2024.2 (Dalmatian) | Ubuntu Jammy | Ubuntu Jammy | >=1.29,<=1.31 |
| 2025.1 (Epoxy) | Ubuntu Jammy | Ubuntu Jammy | >=1.29,<=1.31 |
| 2025.1 (Epoxy) | Ubuntu Noble | Ubuntu Noble | >=1.29,<=1.31 |
Communication
- Join us on IRC:
#openstack-helmon oftc - Join us on Slack (this
is preferable way of communication):
#openstack-helm - Join us on Openstack-discuss
mailing list (use subject prefix
[openstack-helm])
The list of Openstack-Helm core team members is available here openstack-helm-core.
Storyboard
You found an issue and want to make sure we are aware of it? You can do so on our Storyboard.
Bugs should be filed as stories in Storyboard, not GitHub.
Please be as much specific as possible while describing an issue. Usually having more context in the bug description means less efforts for a developer to reproduce the bug and understand how to fix it.
Also before filing a bug to the Openstack-Helm Storyboard please try to identify if the issue is indeed related to the deployment process and not to the deployable software.
Other links
Our documentation is available here.
This project is under active development. We encourage anyone interested in OpenStack-Helm to review the code changes
Our repositories:
- OpenStack charts openstack-helm
- OpenStack-Helm plugin openstack-helm-plugin
- Build non-OpenStack images openstack-helm-images
- Build Openstack images loci
We welcome contributions in any form: code review, code changes, usage feedback, updating documentation.
Release notes
We use reno for managing release notes. If you update a chart, please add a release note using the following command:
reno new <chart_name>This will create a new release note file
releasenotes/notes/<chart_name>-<sha>.yaml.
Fill in the necessary information and commit the release note file.
If you update multiple charts in a single commit use the following command:
reno new commonThis will create a new release note file
releasenotes/notes/common-<sha>.yaml. In this case
you can add multiple chart specific sections in this release note
file.
When building tarballs, we will use the reno features to
combine release notes from all files and generate
<chart_name>/CHANGELOG.md files.