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
kind of follow-up of #465, after upgrading to SCDF 2.11.5, we've noticed that environment variables aren't translated into the initContainer. Our tasks are launched with
obtaining the same result, also using environmentVariables instead of environment-variables. The only way we are now able to pass environmentVariables is by setting the following property
(note that environmentVariables must be used, environment-variables isn't recognized; also, it's weird that deployer.TASK_NAME.kubernetes.init-container.environmentVariables:["FRAMEWORK_DIR=/shared-dir","CERTIFICATES_DIR=/certificates"] doesn't pick up the env vars)
The text was updated successfully, but these errors were encountered:
good news, as there seems to be a syntax that is compatible with 2.11.5 and earlier versions, json notation with environmentVariables being named exactly that way, but at least there's a workaround that allows our scripts to behave the same, no matter the version of SCDF used:
Hi,
kind of follow-up of #465, after upgrading to SCDF 2.11.5, we've noticed that environment variables aren't translated into the initContainer. Our tasks are launched with
Everything gets translated except the
environment-variables
bit. We've also tried withobtaining the same result, also using
environmentVariables
instead ofenvironment-variables
. The only way we are now able to pass environmentVariables is by setting the following property(note that
environmentVariables
must be used,environment-variables
isn't recognized; also, it's weird thatdeployer.TASK_NAME.kubernetes.init-container.environmentVariables:["FRAMEWORK_DIR=/shared-dir","CERTIFICATES_DIR=/certificates"]
doesn't pick up the env vars)The text was updated successfully, but these errors were encountered: