Edgar Hernández

> So the k8s API token which is gathered during the user login is used mostly for everything. One exception is the cache, where kiali strictly uses the service account...

> I don't want to move that far, but what would need to graduate the experimental remote secret feature to be stable? Well, we say it is experimental, because it...

> As a solution: > > * I could imagine the presence of the remote secret could trigger this new behavior to make it zero-conf, or else > I would...

> Will start crafting code for this, Alright! > but for first sight it might be tricky. Code should prepare the k8s client itself for multiple targets, giving back the...

I was thinking a little bit on this. Updating a git repository is probably somewhat out of scope of the goals of Kiali. That said, some integration with GitOps, even...

No feedback. I'd lean towards flagging this with `help wanted` and/or `future`.

I think that even generic Git support would be somewhat big, because the structure of the repo is something that would need to be standardized or configurable (and most likely,...

The `client_id` is in the Kiali CR because it's public (Reference: https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/). So, it didn't make sense to put it in a secret. What we currently have is OK, so...

> It seems like a bug that the slash is stripped, no? Any trailing slash is stripped [at the operator side](https://github.com/kiali/kiali-operator/blob/dc28335bafd9c008cd149f901f874c11d046999a/roles/default/kiali-deploy/tasks/main.yml). I think this was more a design choice, because...

Well, I think that we devs have the right to either relax or build on top of any concept as long as it is properly documented. Honestly, I don't think...