You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I want to add new ENV to the KFO helm charts for INSTANCE_ID and I did not see a way to configure that via values.yaml.
I cannot add it like secrets as the instance_id will be dynamic based on the n number of nodes.
@Cryptophobia@javiercri any suggestions for this issue? Is there a way to add INSTANCE_ID to ENV for pods same like K8S_NODE_NAME via values.yaml .
spec.providerID gives the output as aws:///eu-west-3c/i-0a79903e0d1904f4 and I thought using some hacks I can extract the instanceid and use it further to pass to the fluentd pod but did not have a success that route :(
Is your feature request related to a problem? Please describe.
I want to add new ENV to the KFO helm charts for INSTANCE_ID and I did not see a way to configure that via values.yaml.
I cannot add it like secrets as the instance_id will be dynamic based on the n number of nodes.
Tried like below under fluentd -
fluentd:
extraEnv:
- name: INSTANCE_ID
valueFrom:
fieldRef:
fieldPath: spec.providerID
or
fluentd:
extraEnv:
INSTANCE_ID: "spec.providerID | cut -d '/' -f 5"
Is there any other way I can add the ENV in the helm chart? Please suggest if there is an alternative.
Describe the solution you'd like
There should be a way to introduce new env like - https://github.com/vmware/kube-fluentd-operator/blob/main/charts/log-router/templates/daemonset.yaml#L48
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: