c92d14b4e3
The `/` path returns an HTTP redirect with 300 status code, which is not
valid in context of Kubernetes probes and results in thousands of
unnecessary events.
Change-Id: If719975a953025f3262da828f82e721566fa98e6
(cherry picked from commit
|
||
|---|---|---|
| aodh | ||
| barbican | ||
| ceilometer | ||
| cinder | ||
| cyborg | ||
| designate | ||
| doc | ||
| glance | ||
| heat | ||
| horizon | ||
| ironic | ||
| keystone | ||
| magnum | ||
| manila | ||
| masakari | ||
| mistral | ||
| monasca | ||
| neutron | ||
| nova | ||
| octavia | ||
| openstack | ||
| placement | ||
| rally | ||
| releasenotes | ||
| senlin | ||
| tacker | ||
| tempest | ||
| tests | ||
| tools | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| bindep.txt | ||
| LICENSE | ||
| Makefile | ||
| README.rst | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
| yamllint-templates.conf | ||
| yamllint.conf | ||
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 |
|---|---|---|---|
| Zed | Ubuntu Focal | Ubuntu Focal | >=1.26,<=1.28 |
| Zed | Ubuntu Jammy | Ubuntu Jammy | >=1.26,<=1.28 |
| 2023.1 (Antelope) | Ubuntu Focal | Ubuntu Focal | >=1.26,<=1.28 |
| 2023.1 (Antelope) | Ubuntu Jammy | Ubuntu Jammy | >=1.26,<=1.28 |
| 2023.2 (Bobcat) | Ubuntu Jammy | Ubuntu Jammy | >=1.26,<=1.28 |
| 2024.1 (Caracal) | Ubuntu Jammy | Ubuntu Jammy | >=1.26,<=1.28 |
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
- Infra charts openstack-helm-infra
- OpenStack-Helm plugin openstack-helm-plugin
- Building images openstack-helm-images
- Building Openstack images framework loci
We welcome contributions in any form: code review, code changes, usage feedback, updating documentation.