Daniel Hrabovcak

I agree with this suggestion. My use case is this: I want to reuse a connection pool but serialize differently depending on the data structure, e.g. single Redis database but...

To explain it with an example, imagine class A is owned by third-party library so you're unable to add annotations to it because you're not the one who defines it....

> do we have to hit both? I'll double check this, but you're right. We do not. If they're replicas, there may be duplicate data in this current implementation. >...

> I imagine with very large clusters, there may be a significant delay (~1m) after applying the CR before the status is correct. To also clarify, in this case, it...

One recommendation I've seen the GKE Autopilot team make, which might be worth exploring in light of the issue you're seeing, is to set the request and limit memory amounts...

One difference managed collection and self-deployed collection will have is that GKE Autopilot should not change limits on the managed collection version. One thing you can try is changing the...

My 2-cents since we saw a customer report this issue recently: besides maybe rewording this error message, maybe we also shouldn't make it a hard error if they're using the...

Converted to a draft. There is still some value in this change but it's gonna be some effort to rebase.

> Is there any timeline for when managed prometheus will update to prometheus v 2.43 or later To answer this part of the question, we are currently deploying Prometheus v2.43...

Hi @xak2000! If you just want to test it, creating a brand new cluster on the latest GKE minor version using the Rapid release channel will always have the latest...