Romanas Sonkinas

I've got the same problem migration from flux v1 to flux v2 (0.26.1) and with `ingress-nginx`. Flux complains with: ``` ❯ flux reconcile kustomization infra --with-source ► annotating GitRepository flux-system...

Thank you! I did not know that managed fields are no longer shown by default, assumed it was a different issue. Problem solved.

Snapshot and heap dump shared privately.

@seut 1. Transport protocol nearly always indicates cross zone traffic, we are fine with this. 2. Logical replication never uses the transport protocol in CrateDB Cloud - we always tunnel...

@hlcianfagna may I suggest CrateDB just implements https://github.com/crate/crate/issues/14238, and then Azure AD would be something we can do in CrateDB Cloud.

Yes thank you. There is a plan to completely rework how explain plans are done to make it more user friendly.

Hi @amotl, There is currently a k8s load balancer in front of all the CrateDB nodes, so round-robin is already happening in that sense - although it is L4 so...

We could technically expose each node as a different port on the LB (`mycluster.aks.westeurope.azure.cratedb.cloud:4200`, `mycluster.aks.westeurope.azure.cratedb.cloud:4201`, `mycluster.aks.westeurope.azure.cratedb.cloud:4202` etc). Of course that introduces its own can of worms with health checks as...

Hey Andreas, > So, when imagining a CrateDB cluster comprised of nodes having different roles (e.g. read-only nodes vs. equally shared roles), the K8s load balancer in front of all...

I only have anecdotal evidence, i.e. when we were trying to upgrade to 3.11 in the [cloud-api](https://github.com/crate/cloud-api/pull/2484), there were issues with celery. That made me come to a mental conclusion...