sass1997

I do have the same issue here. Are you also having istio activated?

As far as I've read the documentation: > As a security enhancement, the argocd-repo-server Deployment uses its own Service Account instead of default. > > If you have a custom...

I will try to debug and let you know with the correct Rolebinding which is needed to start this pod

I can confirm it's definitely missing special rights for this service account. I granted now everything for this service account and now the argocd-repo-server is starting. I'm now digging into...

``` kind: Role apiVersion: rbac.authorization.k8s.io/v1 metadata: namespace: argocd name: argocd-repo-server rules: - apiGroups: ["*"] resources: ["*"] verbs: ["*"] --- kind: RoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: argocd-repo-server namespace: argocd subjects: -...

+1. I was using until now an ugly hack to retrieve the roles via the data sources and then templating the CRD and using the kubectl terraform provider to apply...

Same issue in v2.7.5

Seems to have solved the issue on our side as well Rancher 2.7.5 Keycloak 22.04

Update: It seems that this stuff isn't working anymore. @eliaoggian I can see in your logs that you have added keycloak via generic oidc on rancher side. Any reasons for...

+1