-
Notifications
You must be signed in to change notification settings - Fork 173
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
Scuttle Logging cannot be disabled #179
Comments
Hi @cogren1, thank you for reporting this! I've added the fix for it here: #182. I think this matter with logging was a bug since scutlle was added and just wasn't noticed before 😞 To avoid confusion with what this option means, I've renamed the setting itself to |
Is there any news about this issue? :) The pull requests seem to be stuck at the moment.. I would love to use k6 in combination with Istio! |
Fixed by #182 |
Brief summary
Scuttle enables logging by default. This is problem because its logs end up in the initializer logs, causing the operator to be unable to unmarshal it into JSON. Adding
scuttleLogging: false
does not work though because the controller does not insert environment variables into the pod spec when their value evaluates to false. This applies to all boolean Scuttle parameters, but it's only a problem for scuttleLogging because default value in Scuttle is true.Here is the offending line: https://github.com/grafana/k6-operator/blob/main/pkg/resources/jobs/helpers.go#L87
You can see that it checks for a value that evaluates to false instead of checking for the presence of the parameter. I've tested this with scuttleLogging and neverKillIstioOnFailure. When true, the environment variable is present. When false, they are not present. These, and other scuttle values, are defined as boolean in the CRD, which seems unnecessary since the values get converted to strings when inserted as pod environment variables and is one of the reasons this bug occurs.
k6-operator version or image
v0.0.9rc1, v0.0.8, v0.0.8rc3, v0.0.8rc2, v0.0.8rc1, v0.0.7, v0.0.7rc4, v0.0.7rc3, v0.0.7rc2, v0.0.7rc
K6 YAML
Other environment details (if applicable)
Istio is installed.
Steps to reproduce the problem
On a cluster with Istio installed:
Expected behaviour
SCUTTLE_LOGGING
appears in the initializer pod spec underenv
with value"false"
.Actual behaviour
SCUTTLE_LOGGING
does not appear in the initializer pod spec.The text was updated successfully, but these errors were encountered: