Cross-posting: Hey <#C065944F9M2|pyflink> — I’ve ...
# troubleshooting
n
Cross-posting: Hey #pyflink — I’ve been looking into how Flink starts Python processes via
PythonEnvUtils.java
, and I noticed that it logs the entire environment variable map when launching PyFlink jobs. This seems like it could be a security issue, especially in Kubernetes setups using the Flink Kubernetes Operator — since secrets are commonly mounted as env vars in pods. That means things like
AWS_SECRET_ACCESS_KEY
,
DB_PASSWORD
, etc. could end up in plaintext JobManager or TaskManager logs. 📌 Here's an example of what’s being logged:
Copy code
Starting Python process with environment variables: AWS_SECRET_ACCESS_KEY=..., DB_PASSWORD=...
Has anyone else run into this? Curious if there's already been discussion or a fix proposed upstream. Would love thoughts from others who are deploying PyFlink in production or using secrets in K8s environments. I've created https://issues.apache.org/jira/browse/FLINK-38035 with all details