I got all the Bitcoin/Lightning software running again. Have to finish the bitcoin cookbook I have on my machine, and also write code for all the Lightning stuff.
I think those are explained sufficiently clear in the software list under the diagram. There's not much space to work with, as it's pretty large and hardly legible in smaller sizes already.
I only changed it so that the documented default isn't wrong. It's easy enough for anyone to type a line of text when they create a cookbook. Spending a ton of time on this is not really useful IMO.
I think if it would fit right now, we wouldn't have had the upgrade issues, due to pods being scheduled on a different node.
There's one other solution that could make sense, which is using larger nodes and force-scheduling all gitea-server pods/replicas on the same node. This way, at least the rolling updates should work, and it would cost much less than the Filestore solution.
@gregkare So what this basically means is that Kubernetes is not a great place to run something like Gitea, which has to store files on disk and cannot use an object storage instead. Unless the project is big enough to justify the $0.30/GB cost of Google Filestore and the minimum purchase of 1TB storage/month.
OK, so I spent quite some time trying out all kinds of different configs until finally learning that GCE persistent disks simply don't support ReadWriteMany to begin with.
@bumi Could you please give me your feedback, so we can either improve the diagram, or close the issue?
I tried specifying the volume ID for the new claims explicitly, but that also didn't work. So I posted a question on StackOverflow, which Google apparently uses as the official support site for GKE: