George Gaál

we will have the same issue with the tenant cluster versions and compatibility between kubectl utility and tenants clusters...

> Flux 2.3 CLI can't work with Flux 2.2 because some deprecated versions are finally removed after years. it is totally not understandable, because kubectl works (!)

The solution is simple as 2*2. One needs to add new command-line argument like "--api-server-timeout" for helm and pass it's value to [client-go](https://github.com/kubernetes/client-go) library.

I observer the same behavior. The issue that we are using 100% gitops approach with FluxCD. And I need `subnetRefs` to substitute correct `subnetIDs` in runtime. It looks like that...

p.s. it is really very annoying bug.

Hi! I am not administrator, neither developer, nor consultant from Weave. So the below only my POV: 1. The weave gitops shows only basic objects without any relation to downstream...

Hm. strange... maybe I am wrong.. I checked the docs for weave gitops... Please take a look Here: https://github.com/weaveworks/weave-gitops/blob/main/doc/img/02-workload-detail.png we don't see any rs and pods but here: https://github.com/weaveworks/weave-gitops/blob/main/doc/img/03-graph.png we...

I think the issue is that it was compiled against old fluxcd library versions: https://github.com/weaveworks/weave-gitops/commit/591cc3d862f8c80d95a7db951aefb73a3a501061 and now we are using newer fluxcd 2.3.0 with NEW API for Helmreleases and kustomization

@FernandoMiguel Good day! Probably a stupid question, but did the `Role` get into Ready condition? I faced several times that Roles are not going to `Ready`, so all refs to...

/remove-lifecycle stale