Max Jonas Werner

Reopening to take automation of this task into account.

@takirala have you already started working on this?

No worries and thanks for coming back to this. I unassigned you for now but please don't hesitate to pick it back up if you're still up for the task.

> Would it be better to make the source column `namspace/name` since the source can be in a different namespace? I would have loved to do that, plus the source's...

How about this? ``` $ ./bin/flux get ks velero -A --include-source NAMESPACE NAME SOURCE REVISION SUSPENDED READY MESSAGE kommander velero GitRepository/kommander-flux/management main/d8bac31 False True Applied revision: main/d8bac31 ```

I just realized I should've created a new issue in flux2 but instead transferred the existing one from kustomize-controller, effectively making the discussion hard to reason about. Sorry for that

> The goal would be that a given cluster applies one $team/ set of configs and the contents of $team/bases So in that scenario your teams would always have to...

Just one thing that confuses me a little is that the URL is clearly `https://github.com/...` but the error says the cert isn't valid for `airflow-helm.github.io`. 🤔

> @makkes The repo is https://airflow-helm.github.io/charts/. Likely just a redirect. Even if it's a redirect, it should check the proper domain.

At first sight this looks like the helm-controller Pod lost access rights on some API resources. Could you check if anything around RBAC has changed at the time these failures...