Till!

Just for the record, I didn't have k8s enabled, so not sure how "related". Also, Docker's IP range did not "conflict" with the VPN I was connected to. The only...

IMO, shortening the distro name would be good. I know various tools like Ansible use the names to guess the environment. Maybe that requires coordination?

I am running lago `https://billing.example.org` and its API with `https://api.billing.example.org`. Cors still does not work?

I added the following annoations for haproxy-ingress which seem to work: ```yaml haproxy-ingress.github.io/cors-enable: "true" haproxy-ingress.github.io/cors-allow-credentials: "true" haproxy-ingress.github.io/cors-allow-origin: "https://billing.example.org" haproxy-ingress.github.io/cors-allow-headers: "DNT,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization,apollographql-client-name,apollographql-client-version,x-lago-organization,customer-portal-token" ```

I hope I am tagging this on the the correct issue, so here we go: - I am using Docker Desktop - I had "Use containerd for pulling and storing...

Is it possible that homebrew still uses your old one? ``` ==> Purging files for version 3.0.5 of Cask putio-adder Error: putio-adder: SHA256 mismatch Expected: 58a772804ea8509e302376838c9ed71f8b3820263843cb65421ec8bfebd5092e Actual: 0a95a144a2ff43dc8d3bd34229235c6efcc194b20812ce1c1dd2987d709c83a5 File: /Users/foo/Library/Caches/Homebrew/downloads/2c68843b57f1b306940695c46c0807186476795bccae61f3b9d13fb93ee4dc99--put.io-adder-v3.0.5.zip...

I am currently not using the manifest deployer, but the helm one supports an "order" key to ensure charts get installed in the correct order. Helm charts are not amazing,...

@fenio yeah, I understand. I found the manifests too unpredictable. Btw, artifacts.hub has a chart, maybe you don't need to maintain it yourself: https://artifacthub.io/packages/helm/prometheus-community/prometheus-operator-crds Otherwise, need to dive into the...

I think I have an issue related to this: "the server has asked for the client to provide credentials" The obvious thing (`~/.kube/config`) is fine, and I can still access...

I forgot to: the fix is to restart k0s.