Repository navigation
Falco chart extra.initContainers usage #4023
Replies: 1 comment
|
The
Values for a subchart must be nested under the dependency name, or under its alias if Use: falco:
falcoctl:
artifact:
install:
envFrom:
- secretRef:
name: falco-oci-registry-auth
follow:
envFrom:
- secretRef:
name: falco-oci-registry-auth
extra:
initContainers:
- name: falcoctl-debug
image: _PRIVATE_REGISTRY_HERE_/busybox:1.38.0
imagePullPolicy: IfNotPresent
command: ["/bin/sh", "-c"]
args:
- 'test -n "${FALCOCTL_REGISTRY_AUTH_BASIC:-}" && echo "variable is set" || echo "variable is missing"'
envFrom:
- secretRef:
name: falco-oci-registry-authIf the dependency has an alias, replace the outer Avoid The value is defined here and consumed by the pod template. The outer-key requirement follows Helm's subchart value scoping. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I'd like to debug why my
falcoctl-installinitContainer seems not to findFALCOCTL_REGISTRY_AUTH_BASICvariable, although it was set using afalco-oci-registry-authsecret. InitContainer is probably trying to load an empty variableFALCOCTL_REGISTRY_AUTH_BASICcontent for an unknown reason i'll have to find next.As falco-install initContainer doesn't have any shell, i was thinking about spawning a debug pod using the
extra.initContainerssection of the falco chart (seefalco/chart/falco/values.yaml
Line 473 in e12b1d4
By doing so i would like to load the secret containing the content stored in
FALCOCTL_REGISTRY_AUTH_BASICvariable and output it....but it seems i'm mis-using it: it never renders my additional initContainer.The falco chart as been tailored a little to embeds some default values in the default values.yaml such as envFrom for falcoctl-follow container and falcoctl-install initContainer to load the FALCOCTL_REGISTRY_AUTH_BASIC variable from a secret:
$ grep -A2 -B3 envFrom charts/falco/values.yaml install: enabled: true env: [] envFrom: - secretRef: name: falco-oci-registry-auth -- follow: enabled: true env: [] envFrom: - secretRef: name: falco-oci-registry-authWhat is wrong with my custom value file used to override default one regarding the initContainers section ?
when i ran helm template it is never rendered:
pod-template.tpl seems not to have any condition to meet before loading extra.initContainers section:
Any clue ?
All reactions