f1e0981226
The helm-toolkit.utils.daemonset_overrides function have some limitations:
* it allows to override only conf values specifid in configmap-etc
* it doesn't allow to override values for daemonsets passed via env variables
or via damoenset definition. As result it is impossible to have mixed
deployment when one compute is configured with dpdk while other not.
* it is impossible to override interface names/other information stored in
<service>-bin configmap
* It allows to schedule on both hosts and labels, which adds some
uncertainty
This implementation is intended to handle those limitations:
* it allows to schedule only based on labels
* it creates <service>-bin per daemonset override
* it allows to override values when rendering daemonsets
It picks data from the following structure:
.Values:
overrides:
mychart_mydaemonset:
labels:
label::value:
values:
override_root_option: override_root_value
conf:
ovs_dpdk:
enabled: true
neutron:
DEFAULT:
foo: bar
Change-Id: I5ff0f5deb34c74ca95c141f2402f375f6d926533
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on IRC: #openstack-helm on oftc
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on oftc
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.