openstack/openstack-helm
Code Issues Proposed changes

Merge "Update developer references 'upgrade' section"

Browse Source
This commit is contained in:
Zuul 2018-06-10 13:14:14 +00:00 committed by Gerrit Code Review
commit d76591d974
1 changed files with 14 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -30,7 +30,7 @@ image change.
Note: Rolling update values can conflict with values defined in each Note: Rolling update values can conflict with values defined in each
service's PodDisruptionBudget. See service's PodDisruptionBudget. See
`here <../../../html/operator/kubernetes.html#pod-disruption-budgets>`_ `here <https://docs.openstack.org/openstack-helm/latest/devref/pod-disruption-budgets.html>`_
for more information. for more information.
This is accomplished with the following annotation: This is accomplished with the following annotation:
@ -47,21 +47,15 @@ any change to any file referenced by configmap-bin.yaml or
configmap-etc.yaml results in a new hash, which will then trigger a configmap-etc.yaml results in a new hash, which will then trigger a
rolling update. rolling update.
All chart components (except ``DaemonSets``) are outfitted by default All ``Deployment`` chart components are outfitted by default
with rolling update strategies: with rolling update strategies:
:: ::
# Source: keystone/templates/deployment-api.yaml
spec: spec:
replicas: {{ .Values.replicas }} replicas: {{ .Values.pod.replicas.api }}
revisionHistoryLimit: {{ .Values.upgrades.revision_history }} {{ tuple $envAll | include "helm-toolkit.snippets.kubernetes_upgrades_deployment" | indent 2 }
strategy:
type: {{ .Values.upgrades.pod_replacement_strategy }}
{{ if eq .Values.upgrades.pod_replacement_strategy "RollingUpdate" }}
rollingUpdate:
maxUnavailable: {{ .Values.upgrades.rolling_update.max_unavailable }}
maxSurge: {{ .Values.upgrades.rolling_update.max_surge }}
{{ end }}
In ``values.yaml`` in each chart, the same defaults are supplied in every In ``values.yaml`` in each chart, the same defaults are supplied in every
chart, which allows the operator to override at upgrade or deployment chart, which allows the operator to override at upgrade or deployment
@ -69,9 +63,12 @@ time.
:: ::
upgrades: pod:
revision_history: 3 lifecycle:
pod_replacement_strategy: RollingUpdate upgrades:
rolling_update: deployments:
max_unavailable: 1 revision_history: 3
max_surge: 3 pod_replacement_strategy: RollingUpdate
rolling_update:
max_unavailable: 1
max_surge: 3