
Conditionals: since the developer flag is no longer used by the glance chart, it's no longer a good example. However, we want to keep the flag around for future use if needed. So, replaced with a foo/bar example. gen-oslo-openstack-helm README: it referred to "this directory", which doesn't make sense when the README is sourced into the overall ops guide. Specified the directory explicitly. Change-Id: I2ba02bd3efd87e58fcb701c8b7c2bb6af05994ba
39 lines
1.0 KiB
ReStructuredText
39 lines
1.0 KiB
ReStructuredText
Common Conditionals
|
|
-------------------
|
|
|
|
The OpenStack-Helm charts make the following conditions available across
|
|
all charts, which can be set at install or upgrade time with Helm below.
|
|
|
|
Developer Mode
|
|
~~~~~~~~~~~~~~
|
|
|
|
::
|
|
|
|
helm install local/chart --set development.enabled=true
|
|
|
|
The development mode flag should be used by any charts that should
|
|
behave differently on a developer's laptop than in a production-like deployment,
|
|
or have resources that would be difficult to spin up in a small environment.
|
|
|
|
A chart could for instance define the following ``development:``
|
|
override to set ``foo`` to ``bar`` in a dev environment, which
|
|
would be triggered by setting the ``enabled`` flag to ``true``.
|
|
|
|
::
|
|
|
|
development:
|
|
enabled: false
|
|
foo: bar
|
|
|
|
|
|
Resources
|
|
~~~~~~~~~
|
|
|
|
::
|
|
|
|
helm install local/chart --set resources.enabled=true
|
|
|
|
Resource limits/requirements can be turned on and off. By default, they
|
|
are off. Setting this enabled to ``true`` will deploy Kubernetes
|
|
resources with resource requirements and limits.
|