Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
In the pulumi-operator v1, logs weren't great but at least they were structured. In V2 we cant configure the --zap anymore to change the logging format and is using "console" what is terrible for parsing and sending to log backend (e.g. opensearch).
The pulumi operator itself does have the option to chose json in the helm char values. The workspace should have the same option and not just the log level.
In addition, it would be good to be able to change everything via ENV_VAR if there is no option in the stack (I think this is not a stack option but a more generic "always use structured logging"
Affected area/feature
Pulumi kubernetes operator V2
Hello!
Issue details
In the pulumi-operator v1, logs weren't great but at least they were structured. In V2 we cant configure the
--zapanymore to change the logging format and is using "console" what is terrible for parsing and sending to log backend (e.g. opensearch).The pulumi operator itself does have the option to chose
jsonin the helm char values. The workspace should have the same option and not just the log level.In addition, it would be good to be able to change everything via ENV_VAR if there is no option in the stack (I think this is not a stack option but a more generic "always use structured logging"
Affected area/feature
Pulumi kubernetes operator V2