Consider adding user-supplied sidecars for SGCluster pods
Some applications might want to access Postgres, or its filesystem, or part of other components, directly (i.e. not through the Postgres wire protocol). For this cases, highly user dependent, we might want to add the possibility to "inject" a user sidecar into the SGCluster pods.
This could potentially imply many options like:
- Container image.
- Environment variables, config maps?
- Inject some additional env vars to the container, like the postgres superuser and password.
- Potentially access the Postgres filesystem (PGDATA) and/or the logs, etc.
- Resource limits for the user-added sidecar, to control its potential impact.
Subject to further Discussion.