Make sure to read the warnings on that page about how this can fail. Also be aware that the community provided guidance on that page for a Python service is incomplete. The uwsgi container must be restarted for source code changes to take effect. The missing step would be to call the Kubernetes API to kill the running container or otherwise affect the termination of the active pod and creation of a new one. PHP reads files from disk again for each requests which makes that workflow simpler.

T321919: Figure out and document how to call the Kubernetes API as your tool user from inside a pod has some information on possible ways for to interact with the Toolforge Kubernetes API from inside the Kubernetes cluster.