Authentik Outpost with Remote RKE2/Kubernetes Cluster

📋 Before we dive in: There are two RKE2/Kubernetes clusters - production and development - both clusters are separately enrolled clusters. Authentik is installed in the production cluster and automatically added the "local" cluster as "embedded kubernetes cluster" as outpost. To use the authentik proxy forwarding feature for ingresses on the development cluster, we have to add the cluster as remote outpost to Authentik. In this scenario we've the following params: Remote Cluster Address: https://my.remote-development.cluster:6443 Namespace for Helm installation: authentik-remote 1️⃣ Install "authentik-remote-cluster" First we have to add the authentik-remote-cluster Helm Chart to the development cluster. helm repo add authentik https://charts.goauthentik.io helm repo update And then install the authentik-remote-cluster via the Rancher UI or Helm CLI. 2️⃣ Generate Authentik configuration manifest After successful installation, you'll get a script-snippet like this: Copy the snippet and