website/docs: add outpost integrations docs

Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>

website/docs/outposts/integrations/docker.md

@@ -0,0 +1,51 @@
+---
+title: Docker
+---
+
+The docker integration will automatically deploy and manage outpost containers using the Docker HTTP API.
+
+This integration has the advantage over manual deployments of automatic updates (whenever authentik is updated, it updates the outposts), and authentik can (in a future version) automatically rotate the token that the outpost uses to communicate with the core authentik server.
+
+The following outpost settings are used:
+
+- `object_naming_template`: Configures how the container is called
+- `container_image`: Optionally overwrites the standard container image (see [Configuration](../../installation/configuration.md) to configure the global default)
+- `docker_network`: The docker network the container should be added to. This needs to be modified if you plan to connect to authentik using the internal hostname.
+- `docker_map_ports`: Enable/disable the mapping of ports. When using a proxy outpost with traefik for example, you might not want to bind ports as they are routed through traefik.
+
+The container is created with the following hardcoded properties:
+
+- Labels
+
+    - `io.goauthentik.outpost-uuid`: Used by authentik to identify the container, and to allow for name changes.
+
+    Additionally, the proxy outposts have the following extra labels to add themselves into traefik automatically.
+
+    - `traefik.enable`: "true"
+    - `traefik.http.routers.ak-outpost-<outpost-id>-router.rule`: `Host(...)`
+    - `traefik.http.routers.ak-outpost-<outpost-id>-router.service`: `ak-outpost-<outpost-id>-service`
+    - `traefik.http.routers.ak-outpost-<outpost-id>-router.tls`: "true"
+    - `traefik.http.services.ak-outpost-<outpost-id>-service.loadbalancer.healthcheck.path`: "/akprox/ping"
+    - `traefik.http.services.ak-outpost-<outpost-id>-service.loadbalancer.healthcheck.port`: "9300"
+    - `traefik.http.services.ak-outpost-<outpost-id>-service.loadbalancer.server.port`: "9000"
+
+## Permissions
+
+To minimise the potential risks of mapping the docker socket into a container/giving an application access to the docker API, many people use Projects like [docker-socket-proxy](https://github.com/Tecnativa/docker-socket-proxy). authentik requires these permissions from the docker API:
+
+- Images/Pull: authentik tries to pre-pull the custom image if one is configured, otherwise falling back to the default image.
+- Containers/Read: Gather infos about currently running container
+- Containers/Create: Create new containers
+- Containers/Kill: Cleanup during upgrades
+- Containers/Remove: Removal of outposts
+
+## Remote hosts
+
+To connect remote hosts, you can follow this Guide from Docker [Use TLS (HTTPS) to protect the Docker daemon socket](https://docs.docker.com/engine/security/protect-access/#use-tls-https-to-protect-the-docker-daemon-socket) to configure Docker.
+
+Afterwards, create two Certificate-keypairs in authentik:
+
+- `Docker CA`, with the contents of `~/.docker/ca.pem` as Certificate
+- `Docker Cert`, with the contents of `~/.docker/cert.pem` as Certificate and `~/.docker/key.pem` as Private key.
+
+Create an integration with `Docker CA` as *TLS Verification Certificate* and `Docker Cert` as *TLS Authentication Certificate*.

website/docs/outposts/integrations/kubernetes.md

@@ -0,0 +1,46 @@
+---
+title: Kubernetes
+---
+
+The kubernetes integration with automatically deploy outposts on any Kubernetes Cluster.
+
+This integration has the advantage over manual deployments of automatic updates (whenever authentik is updated, it updates the outposts), and authentik can (in a future version) automatically rotate the token that the outpost uses to communicate with the core authentik server.
+
+This integration creates the following objects:
+
+- Deployment for the outpost container
+- Service
+- Secret to store the token
+- Prometheus ServiceMonitor (if the Prometheus Operator is installed in the target cluster)
+- Ingress (only Proxy outposts)
+- Traefik Middleware (only Proxy outposts with forward auth enabled)
+
+The following outpost settings are used:
+
+- `object_naming_template`: Configures how the container is called
+- `container_image`: Optionally overwrites the standard container image (see [Configuration](../../installation/configuration.md) to configure the global default)
+- `kubernetes_replicas`: Replica count for the deployment of the outpost
+- `kubernetes_namespace`: Namespace to deploy in, defaults to the same namespace authentik is deployed in (if available)
+- `kubernetes_ingress_annotations`: Any additional annotations to add to the ingress object, for example cert-manager
+- `kubernetes_ingress_secret_name`: Name of the secret that is used for TLS connections
+- `kubernetes_service_type`: Service kind created, can be set to LoadBalancer for LDAP outposts for example
+- `kubernetes_disabled_components`: Disable any components of the kubernetes integration, can be any of
+    - 'secret'
+    - 'deployment'
+    - 'service'
+    - 'prometheus servicemonitor'
+    - 'ingress'
+    - 'traefik middleware'
+- `kubernetes_image_pull_secrets`: If the above docker image is in a private repository, use these secrets to pull.
+
+    NOTE: The secret must be created manually in the namespace first.
+
+## Permissions
+
+The permissions required for this integration are documented in the helm chart, see [Cluster-level](https://github.com/goauthentik/helm/blob/main/charts/authentik-remote-cluster/templates/cluster-role-binding.yaml) and [Namespace-level](https://github.com/goauthentik/helm/blob/main/charts/authentik-remote-cluster/templates/role-binding.yaml).
+
+## Remote clusters
+
+To add a remote cluster, you can simply install this helm chart in the target cluster and namespace: https://artifacthub.io/packages/helm/goauthentik/authentik-remote-cluster
+
+After installation, the helm chart outposts an example kubeconfig file, that you can enter in authentik to connect to the cluster.