Closed chrisseto closed 1 month ago
Ah! Good catch. I thought that logic was handled by the config watcher 🤔
Also isn't the syntax for {PASSWORD}
incorrect?
I've removed the referenced part of the prestart hook and confirmed that SASL still works in either a freshly created cluster or an upgraded one.
Prior to this commit debugging issues with our lifecycle hooks was next to impossible. This is primarily due to Kubernetes providing little to no output about them except in the case of failure. Our hooks are wrapped with ; true to ensure failure never happens making the entire issue worse.
This commit adds a more complex wrapper around the PostStart and PreStop hooks which causes all output from the hooks to be output to stdout of the redpanda process so it appears in
kubectl logs
with a timestamp and prefix indicating which hook it is.Example output from
kubectl logs -f
on a terminating node: