Custom KEDA Docker Image with Log Redirection (stdout/stderr to file) – Best Practice?

[rockingcubes]

Hi KEDA team! 👋

I’m building a custom Docker image for the KEDA operator (v2.15.1) based on your official image. I’d like to redirect logs to files (e.g., /logs/stdout.log, /logs/stderr.log) for Splunk ingestion using a sidecar forwarder.
We tried wrapping the KEDA binary with an entrypoint.sh like this:

#!/bin/bash
exec > >(tee -a /logs/stdout.log)
exec 2> >(tee -a /logs/stderr.log >&2)
exec /keda --zap-log-level=info --zap-encoder=console "$@"

And our Dockerfile:

FROM ghcr.io/kedacore/keda:2.15.1 AS base

FROM debian:bullseye-slim
RUN apt-get update && apt-get install -y bash moreutils ca-certificates && rm -rf /var/lib/apt/lists/*
COPY --from=base /keda /keda
COPY entrypoint.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh
ENTRYPOINT ["/entrypoint.sh"]

✅ The operator works fine, but:
/logs/stdout.log is always empty
No ps or ls binaries exist in /keda’s distroless base

📌 My question is:
Is there a better or supported way to redirect logs to a volume/file from KEDA?
Do you recommend sticking with ENTRYPOINT ["/keda", ...] and capturing container logs via stdout instead?

Appreciate your help and amazing work on KEDA 🙏