-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The initializer pod spec does not have envFrom #348
Comments
Hi @ghostx31, yes, it seems like a bug. Thanks for opening the issue. The initializer pod spec does have the IIRC, initially Btw, |
Thanks for your quick response! Yes, I realised that there is no real need to mess with the initializer spec but I had to because of the issue I was facing. I am passing secrets using Let me know in case I can assist you in any way, i'll be happy to help you resolve this.
Got it, I'll update my issue too! |
@ghostx31, would you like to create a PR? 🙂 This should be a simple "good first issue" fix, actually: just adding |
Sure, it seems like a single one liner fix. I'll send a PR once I'm back from work then. |
Brief summary
Hi,
I am pretty new to k6 and the operator usage. The
initializer
pod spec does not seem to have theenvFrom
option and just hasenv
option as can be seen from these lines compared to therunner
pod spec which does have it.The JSON spec for the
initializer
does seem to expose theenvFrom
though as can be inspected from runningkubectl explain TestRun.spec.initializer.envFrom
:I am curious to know if this has not yet been implemented or if this is a deliberate decision or if I am just missing something.
This issue arises from a recent issue that I faced which I have posted on Grafana k6-operator community forum
k6-operator version or image
3.2.0
K6 YAML
Other environment details (if applicable)
GKE v1.27
Steps to reproduce the problem
RATE
andDURATION
variables and a Kubernetes secret with values.Expected behaviour
The tests should run correctly and should pick the values from the ConfigMap.
Actual behaviour
The initializer pod fails with the error that variables are undefined because it cannot pick up any values from the ConfigMap.
The text was updated successfully, but these errors were encountered: