How manage applications with storage and state needs in GitOps with Flux?

[reisman234]

Hello,

I have a general question about how to manage applications in GitOps or FluxCD that need to access a persistent storage to store a certain state (database) or to hold additional artifacts (images). I think a wordpress can be an example here, but it can also be anything else.

I've been looking for something, but so far I haven't found anything really satisfying.

What interests me most are the following points.

• For example, how does the migration to Kubernetes work if you already have existing data?
• Who is responsible for managing the data (dev, ops)?
• How are updates to be handled if, for example, the database model changes (braking change) and no git revert is possible?

If there is a good guide on this, I would be very happy about it :)