-
Story
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
False
-
Documentation (Ref Guide, User Guide, etc.)
-
-
Undefined
There are complex uses cases that require external configuration files provided by configmaps or secrets.
If a reference to those existing configmap/secret resources is included in the CustomResource, the operator could mount them into the POD. Once mounted, they could be accessed by custom scripts during the initialization process of the broker, applying configuration changes or whatever may be needed.
Including confimaps or secrets in the custom resource should be optional. If they are not defined, the operator won't mount anything.
- account is impacted by
-
ENTMQBR-6382 Document the extraMounts usage
- New
- is cloned by
-
ENTMQBR-4735 Doc: [Operator] Provide optional secret/cofigmap in the Custom Resource
- Closed
- is related to
-
ENTMQBR-5402 Operator option for post-config.sh ConfigMap in the initContainer
- Closed
- mentioned in
-
Page Loading...