Jeremy

I would also like to see this @voor good suggestion !

This fix is no longer working. Issue states: unable to translate from 2.x to 3.x config has duplicate unit name `kubeadm.service` ```yaml ignition: containerLinuxConfig: additionalConfig: | storage: links: - path:...

Also getting issues ```bash wget https://beta.release.flatcar-linux.net/amd64-usr/3346.1.0/flatcar_production_iso_image.iso --2022-10-08 22:08:27-- https://beta.release.flatcar-linux.net/amd64-usr/3346.1.0/flatcar_production_iso_image.iso Resolving beta.release.flatcar-linux.net (beta.release.flatcar-linux.net)... 136.144.58.113 Connecting to beta.release.flatcar-linux.net (beta.release.flatcar-linux.net)|136.144.58.113|:443... connected. HTTP request sent, awaiting response... No data received. Retrying. --2022-10-08 22:08:28-- (try:...

Adding chat from slack https://kubernetes.slack.com/archives/C03GQ8B5XNJ/p1665320134211289 Seems the issue is: I was able to connect via pulling the ip address from outside the united states and using that ip to then...

It seems like the issue is geo filtering from the United States it works via vpn. I'm using 1.1.1.1

Im actually in Texas. Ive spun up instances in the following aws regions to test aswell US West (Oregon) Region US West (Northern California) Region US East (Ohio) Region US...

Confirmed fixed (for now)! Also, I couldn't help notice that your nginx is replying with your nginx version when I was curling. You may want to consider removing the severname...

Thank you for this ! I'm using this currently its a lot better than the current implementation! Was driving me crazy, I was considering switching backends, thank you so much...

Shouldn't the version be v5.x ? No mention of 4.x public support . for example, when pulling v26.1 -> point to v5.26.1

I was able to fix this via, Also have muti tenancy. https://github.com/grafana/grafana/issues/22905#issuecomment-1644120475