Enable setting broker env vars, configMaps, and volumes in Configuration Helm templates #478
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
closes #477
While Akri's OPC UA demo has support for mounting certificates as Kubernetes secrets via
opcua.configuration.mountCertificates=true
, there is currently not a flexible way to mount secrets andConfigMaps
in broker Pods via Akri's Configurations. Instead, currently, users have to use the Helm Chart to generate a Configuration and modify it as explained in this documentation.With these Helm chart modifications, secrets could be set like the following:
Special notes for your reviewer:
This was tested for each configuration type (opcua, onvif, udev, and custom) and broker type (brokerPod and brokerJob) with the following installation, modifying for each config and broker type:
The secrets also could have been set via an override values file called
more-values.yaml
:Then, this
more-values.yaml
file could be added to an installation like so:The charts are templated such that multiple volumes, volumeMounts, secretRefs, and configMapRefs can be added -- just continue to index i.e.
--set debugEcho.configuration.brokerJob.envFrom.secretRef[1]="db-user-pass2"
If applicable:
cargo test
)cargo doc
)./version.sh
)