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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
I would like to see consistent configuration parameters across aws provided eks add-ons.
Currently i want to configure all eks add-ons to use json logging, for which i either need to use the additionalArgs for a given sidecar container OR the loggingFormat properties for the affected container of a add-on (ebs-csi-driver).
For kube-proxy both options are missing and i want to see them, as it does indeed support json logging if you specify --logging-format=json.
Which service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
It is hard because there is no effective option, besides adjusting the deployment after the add-on rollout. However on each update i would need to adjust it again (and remember to do so).
Are you currently working around this issue?
Not
Additional context
Attachments
AWS Support case: 173589159400126
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
I would like to see consistent configuration parameters across aws provided eks add-ons.
Currently i want to configure all eks add-ons to use json logging, for which i either need to use the
additionalArgs
for a given sidecar container OR theloggingFormat
properties for the affected container of a add-on (ebs-csi-driver).For kube-proxy both options are missing and i want to see them, as it does indeed support json logging if you specify
--logging-format=json
.Which service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
It is hard because there is no effective option, besides adjusting the deployment after the add-on rollout. However on each update i would need to adjust it again (and remember to do so).
Are you currently working around this issue?
Not
Additional context
Attachments
AWS Support case: 173589159400126
The text was updated successfully, but these errors were encountered: