[backend] Error when installing kfp in a custom namespace

[gopalsarda]

Environment

• How did you deploy Kubeflow Pipelines (KFP)?
  • Followed the steps at https://www.kubeflow.org/docs/components/pipelines/legacy-v1/installation/standalone-deployment/#change-deployment-namespace

• KFP version:
  • git branch origin/release-2.4.0

• KFP SDK version:
  • N/A

Materials and Reference

I followed the steps listed in the docs to install kfp in a different namespace but I get an error like below -

Error from server (Forbidden): error when creating "/manifests/kustomize/cluster-scoped-resources": clusterroles.rbac.authorization.k8s.io "kubeflow-pipelines-cache-deployer-clusterrole" is forbidden: user "[email protected]" (groups=["..." "system:authenticated"]) is attempting to grant RBAC permissions not currently held:
{APIGroups:["admissionregistration.k8s.io"], Resources:["mutatingwebhookconfigurations"], Verbs:["create" "delete" "get" "list" "patch"]}
{APIGroups:["certificates.k8s.io"], Resources:["certificatesigningrequests"], Verbs:["create" "delete" "get" "update"]}
{APIGroups:["certificates.k8s.io"], Resources:["certificatesigningrequests/approval"], Verbs:["create" "delete" "get" "update"]}
{APIGroups:["certificates.k8s.io"], Resources:["signers"], ResourceNames:["kubernetes.io/*"], Verbs:["approve"]}

I see there has been a similar issue reported in the past (#4781) but it does not seem to have any resolution. We do not need the caching feature for our installation. What would be the recommended steps to solve this?

---

Impacted by this bug? Give it a 👍.