Adyanth Hosavalike

You can point your cloudflared to your service directly, or to the ingress. I am working on [an operator to automate it](https://github.com/adyanth/cloudflare-operator) which is currently in alpha.

Currently there are two types of tunnels, one managed on the client side and one with the API/UI. Both of them work in the same way. What are the issues...

Can we set the value to something like -1 when serving within the cache time, so that while querying, we can do something like `speedtest_download_bits_per_second > -1` ?

Instead of limiting options of auth providers, why not implement OAuth2/OIDC and let the user pick whatever provider they need? This would cover Keycloak, Authentik, SuperTokens, Ory Hydra, Auth0 itself...

It's always better to do OIDC than limit to any one provider. Many, many different IdPs (including cloud hosted ones) implement OIDC compared to just adding Keycloak.

A distributed install definitely makes sense for something that monitors uptime for other software. Would not want it to go down along with the other apps.

>All unsafe sysctls are disabled by default and must be allowed manually by the cluster admin on a per-node basis. Pods with disabled unsafe sysctls will be scheduled, but will...

I do not see the tailscaled running in your ps output. Try starting the service? To troubleshoot, you can just run `tailscaled` and see if it comes up just fine.

/remove-lifecycle stale This would be super helpful for me too pointing it to an existing entry rather than add n different A records for each.

Ohh, using the annotations for the fqdn-template is a brilliant idea! Yeah, would have to live with an empty override, but it should not cause any issue I think. Yes,...