marcel/argo-cd
1
0
Fork 0
mirror of https://github.com/argoproj/argo-cd.git synced 2026-02-20 01:28:45 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: Revise web terminal setup instructions for Argo CD (#25992)

Browse Source 
Signed-off-by: Dan Garfield <dan.garfield@octopus.com>
Signed-off-by: Dan Garfield <dan@codefresh.io>
Co-authored-by: Nitish Kumar <justnitish06@gmail.com>
This commit is contained in:
Dan Garfield
2026-01-15 08:42:04 -07:00
committed by GitHub
parent d2cb56d7c7
commit a6cc7ad9a6
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/operator-manual/web_based_terminal.md
View File

@@ -25,7 +25,12 @@ Kubernetes), then the user effectively has the same privileges as that ServiceAc
exec.enabled: "true"
```
2. Patch the `argocd-server` Role (if using namespaced Argo) or ClusterRole (if using clustered Argo) to allow `argocd-server`
2. Restart Argo CD
### Permissions for Kubernetes <1.31
Starting in Kubernetes 1.31, the `get` privilege is enough to exec into a container, so no additional permissions are required. Enabling web terminal before Kubernetes 1.31 requires adding additional RBAC permissions.
1. Patch the `argocd-server` Role (if using namespaced Argo) or ClusterRole (if using clustered Argo) to allow `argocd-server`
to `exec` into pods
- apiGroups:
@@ -45,7 +50,7 @@ to `exec` into pods
kubectl patch clusterrole <argocd-server-clusterrole-name> --type='json' -p='[{"op": "add", "path": "/rules/-", "value": {"apiGroups": ["*"], "resources": ["pods/exec"], "verbs": ["create"]}}]'
```
3. Add RBAC rules to allow your users to `create` the `exec` resource i.e.
2. Add RBAC rules to allow your users to `create` the `exec` resource i.e.
p, role:myrole, exec, create, */*, allow