We forgot to close this one. We merged https://github.com/67P/ipfs-cookbook/pull/4
The benefit is that you end up with only one load balancer instead of one for each service. And yes, the built-in ingress is perfect for everything that doesn't need SSH
OK, now I finally understand what I was missing. You need more moving parts than I thought when running your own ingress controller (that's needed for SSH, the GCE and nginx ingresses built into GKE are for HTTP(S)).
I fixed my RBAC troubles. I was missing the serviceAccountName in the deployment, https://github.com/jcmoraisjr/haproxy-ingress/tree/master/examples/rbac#usage.
Almost there, now I have a permission issue running this with a fresh Gitea on GKE inside its own namespace. Reading on RBAC to fix the error I'm getting on the ingress pod (service with name gitea-test/ingress-default-backend found: services "ingress-default-backend" is forbidden: User "system:serviceaccount:gitea-test:default" cannot get resource "services" in API group "" in the namespace "gitea-test")
All the application/poise projects are dead, the maintainer isn't working on them anymore. I'm currently taking a look at Chef's new app build/deployment/management system, Habitat, that looks very interesting: https://www.habitat.sh
I think we can close this, as the journald logs on barnard go back further than the last reboot (12 days ago)
I don't understand, the logs wouldn't be "empty" even if they were explicitly set to volatile, they would still be stored in memory
Closing this one, this was done as part of the 5apps migration to ejabberd and is included in the ejabberd cookbook