Oh, and Let's Encrypt of course.
I think now you lost the purpose of it. If you put it on 4 different nodes, then you don't need Ingress at all. The entire point of Ingress is routing traffic to services, no? No need for Ingress if you're just doing DNS round-robin to all nodes of the cluster. But with all the drawbacks of having to have all those nodes be online 100% of the time.
I think I read about it here: https://www.doxsey.net/blog/kubernetes--the-surprisingly-affordable-platform-for-personal-projects
I assume this is a very long-winded way of saying "yes, a load balancer is indeed necessary in front of nginx-ingress"?
If we don't need one for normal Ingress (without SSH), then we only need for Gitea, which leaves us with the same one load balancer that we have without setting up Ingress for it.
The entire point of using Ingress on GKE is so we don't have to pay for load balancers. So if it's just more complex, but incurring the same cost, then what's the benefit of Ingress for Gitea?
Next step is testing with a fresh Gitea on GKE then?
Thinking about this again, and I can't help but wonder why we should use a private pin orchestration mechanism, when our IPFS hashes are all published on the public Ethereum ledger to begin with.
They were gone after a reboot. Then I looked at the docs and it seemed like they were indeed only stored in memory until I changed it. That's all I know, and it was definitely broken when I created the issue.
What's the status of this since introducing the ejabberd cookbook?
It would seem that poise-javascript is dead now.
This is still an issue. It was reset at some point on andromeda, and never added on barnard.