Newer versions of python (3.11) & Debian (bookworm) discourage using pip to install packages into system site-packages.
Our WMF built Flink base image installs Flink by pip installing apache-flink into the system site-packages. When it was upgraded to Debian bookworm, this failed, so the --break-system-packages CLI opt was added.
PyFlink application images (like mediawiki-event-enrichment) base on the production Flink image, and use blubber to manage python dependencies and execution. Newer versions of Blubber respect Debian's preference to not install in system site-packages, and create a venv (in /opt/lib/venv). This causes blubber built pyflink apps to break, unless they explicitly set use-system-site-packages.
While this works, the Flink base image should do the right thing and also install into venv (the same one used by blubber built application images).
See also T406872
Done is
- Flink base image no longer uses --break-system-packages
- PyFlink Application images updated to remove use-system-site-packages from blubber config.