Helm charts are a bit confusing

[dispalt]

Hi there, I was looking at using this and I have a couple questions, mostly on the helm charts, I figured I would ask here instead of the iac repo. Assuming i am naming the service ak

• ak-artifact-keeper-shared-config you bind this single claim to many containers, are you expecting an NFS type setup?
• NetworkPolicy is not really that customizable, but you already know that, I think disabling it in production might be the right move, I tried to hook it up to an aws lb and since its limited to nginx it didn't work. Or at least maybe calling that out.
• STORAGE_BACKEND does not seem to work, or at least isn't reflected in the admin ui, it looks like its updated in repositories table though, so I am not sure, Im still working on testing
• The persistent volume default size is too small I think most cloud providers set it to 10gb, you may just want to update it, its also really annoying to debug if you don't know what you're doing.
• the volume claims on backend need to be numbered, again back to the ak-artifact-keeper-shared-config point, Im not quite sure on the intention...
  • If they aren't meant to be shared you'll probably also have to change the strategy to recreate vs rolling, rolling doesn't work with volumes very well.
  • StatefulSet might be a better route?

Anyways, thanks for the project it looks great