openstack/openstack-helm
Code Issues Proposed changes

Merge "Remove misleading section from upgrade docs"

Browse Source
This commit is contained in:
Zuul 2021-05-24 22:05:13 +00:00 committed by Gerrit Code Review
commit 0792d0469e
1 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/devref/upgrades.rst
View File

@ -11,15 +11,12 @@ rolling updates of containers, replacing them with the updating image.
As Helm stands today, several issues exist when you update images within As Helm stands today, several issues exist when you update images within
charts that might have been used by jobs that already ran to completion charts that might have been used by jobs that already ran to completion
or are still in flight. OpenStack-Helm developers will continue to work or are still in flight. An example of where this behavior would be
with the Helm community or develop charts that will support job removal desirable is when an updated db\_sync image has updated to point from
prior to an upgrade, which will recreate services with updated images. one openstack release to another. In this case, the operator will likely
An example of where this behavior would be desirable is when an updated want a db\_sync job, which was already run and completed during site
db\_sync image has updated to point from a Mitaka image to a Newton installation, to run again with the updated image to bring the schema
image. In this case, the operator will likely want a db\_sync job, which inline with the Newton release.
was already run and completed during site installation, to run again
with the updated image to bring the schema inline with the Newton
release.
The OpenStack-Helm project also implements annotations across all chart The OpenStack-Helm project also implements annotations across all chart
configmaps so that changing resources inside containers, such as configmaps so that changing resources inside containers, such as