I am migrating a large preexisting configuration (1 server, 200+ environments, 100+ agents) into an handful of Kubernetes clusters.

To ease the migration burden I'd like to start with static agents, replicating my setup above, because moving to Elastic would necessitate a big refactoring.

This chart has been of great help, but now I've hit an issue, whenever I restart an agent container the content of /godata/config is regenerated, therefore the agent is seen as "new" and I lose the environment association.
This cannot be readily solved by agentAutoRegisterEnvironments because I'd need to deploy dozens of different combinations.

Would you be open to a PR that:

• turns the static agent Deployment into a StatefulSet
• adds an optional PVC template to it, mounted under /godata

This would let each agent keep its identity after a restart, and also let me expand the storage space where repos are pulled, which right now is forced into the kubernetes node.

I'm a big user of this project and I can effectively contribute (e.g. gocd/gocd-vault-secret-plugin#160 ), lemme know.