community VS app

GKE is an abomination. Its reputation is completely undeserved. Sure there's some nice things out of the box, like authenticating to clusters with your Google/GCP account, but day 2 operations are a constant frustration.

What sucks?

1. The Kubernetes Pod garbage collector is configured to be abominally slow, keeping terminated pods in the API server for far too long. This interferes with cluster monitoring by making it seem like there's a consistently high number of OOMKilled etc. pods rather than blipping as it happens. GCP support claims this is working as intended and recommends manually running a script to clean up the API server if it bothers you (this is a managed service?!). See e.g. https://stackoverflow.com/questions/75374590/why-kubernetes-... .

2. The rest of the Kubernetes world moved on from kube-dns and on to CoreDNS. Not GKE! On GKE your two options are kube-dns and the GCP VPC-native Cloud DNS (i.e. Kubernetes service and pod records are listed in the private DNS zone for the VPC). Surprise surprise - if you pick Cloud DNS to help scale your cluster, because GCP isn't operating kube-dns well enough on its managed control plan, then you're on the hook for paying for the Cloud DNS zone as well, it's not included in the GKE cluster costs. See e.g. https://cloud.google.com/kubernetes-engine/docs/how-to/cloud... .

3. GKE clusters automatically log to GCP Cloud Logging, the first 50 GB of which is free. Fair enough. But the price afterwards is a truly mind-boggling $0.50/GB! (https://cloud.google.com/logging/#section-7). How do you turn off GCP Cloud Logging so that you can ship your logs to a cheaper vendor instead? Nope, there's no first-class managed setting; all you get is a community tutorial (https://cloud.google.com/community/tutorials/kubernetes-engi...) that links to this GitHub configuration (https://github.com/GoogleCloudPlatform/community/blob/master...) aaaaand good luck :)

4. No native IPv6. See e.g. https://stackoverflow.com/questions/64110542/has-anyone-iden... . AWS of course does support IPv6: https://docs.aws.amazon.com/eks/latest/userguide/cni-ipv6.ht...

Use beestat https://beestat.io and login with your ecobee credentials. It will provide lots of information about your system, including the unrounded actual temperature. In addition its charts are better than Ecobee’s.

no - not sure on the time exactly. I will look into the beestat.io site, never sw it before.

If your Aux furnace is running then the display on the Ecobee should say "Aux 1" or something like that. Another way is to go to Beestst, log in with your Ecobee credentials. This will give you all the data for how your system is running and you'll be able to see if and when your aux heat is running and for how long.

Hi I am new to this group. I bought a house three years ago with a geothermal closed loop system. I don't know what I don't know about this stuff, but I connected my ecobee thermostat to beestat.io for visualizing the outcome. Is anything weird? Obviously wrong here?

If you happen to have an ecobee thermostat, https://beestat.io/ is an amazing tool for figuring out how your system performs.

same problem here. very frustrating. i'm using https://beestat.io/ instead

You might find it helpful to check out https://beestat.io/ . It gives you a lot more detail and history, and, importantly, shows you temperatures with tenths of a degree accuracy instead of so much rounding.

Thanks. I just learned about beestat.io, so I'm going to see if I can use that additional data to point me in a definitive direction.

At http://beestat.io you can register your thermostat and see the data in better formats

I second using beestat.io! I don't even use the ecobee app anymore unless I need to change temps while away, outside of that all of my monitoring is done on beestat.