openstack-helm/doc/source/devref/getting-started/replicas.rst
Michał Dulko e6c7298baf Convert guides-developer to RST
This commit compiles guides-developer pages into multiple .rst files and
adds them to rst docs index.

Change-Id: I6b62473f67482c9c17d7fda1ec7bbc4072b66aa8
Partial-Implements: blueprint docs-to-rst
2017-04-27 17:04:17 +02:00

1010 B

Replicas

All charts must provide replica definitions and leverage those in the Kubernetes manifests. This allows site operators to tune the replica counts at install or when upgrading. Each chart should deploy with multiple replicas by default to ensure that production deployments are treated as first class citizens, and that services are tested with multiple replicas more frequently during development and testing. Developers wishing to deploy minimal environments can enable the development mode override, which should enforce only one replica per component.

The convention today in OpenStack-Helm is to define a replicas: section for the chart, where each component being deployed has its own tunable value.

For example, the glance chart provides the following replicas in values.yaml

replicas:
  api: 2
  registry: 2

An operator can override these on install or upgrade:

$ helm install local/glance --set replicas.api=3,replicas.registry=3