trustchain-oc1-orchestral
/
authentik
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

website/docs: add helm RBAC notice (#5255) 

website/docs: add helm notice

Signed-off-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
Jens L 2023-04-14 13:21:05 +02:00 committed by GitHub
parent 8160663214
commit 55ad2d7eab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/docs/releases/2023/v2023.4.md
View File

@ -3,6 +3,14 @@ title: Release 2023.4 - RADIUS support
slug: "/releases/2023.4" slug: "/releases/2023.4"
--- ---
## Breaking changes
- (Kubernetes only) Changes to RBAC objects created by helm
In previous versions, the helm chart would create a _ClusterRole_ and _ClusterRoleBinding_ if the service account creation was enabled. This was done to allow the deployment of outposts in any namespace in kubernetes. As this conflicted with multiple authentik installs per cluster, and was often not used, the new helm chart changes these resources to a _Role_ and _RoleBinding_, which give authentik access to deploy in the same namespace.
To keep the old behaviour, you can install the [authentik-remote-cluster](https://artifacthub.io/packages/helm/goauthentik/authentik-remote-cluster) chart, which deploys the same RBAC into any other namespace or cluster.
## New features ## New features
- RADIUS support - RADIUS support