Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update kubeconfig behavior PEM-4198 #1888

Merged
merged 2 commits into from
Dec 11, 2023
Merged

docs: update kubeconfig behavior PEM-4198 #1888

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fc6da9f
docs: update kubeconfig behavior PEM-4198
karl-cardenas-coding Dec 11, 2023
aa91be6
Update docs/docs-content/clusters/cluster-management/kubeconfig.md
karl-cardenas-coding Dec 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/docs-content/clusters/cluster-management/kubeconfig.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Palette exposes kubeconfig files for each cluster deployed through the platform.

Your assigned [Palette permissions](../../user-management/palette-rbac/project-scope-roles-permissions.md) determine which clusters you can access and what operations you can perform on the cluster. The permissions assigned to you in Palette determine if you can download and access the kubeconfig files for a cluster.

As a rule of thumb, users with the Palette role [*Cluster Admin*](../../user-management/palette-rbac/project-scope-roles-permissions#cluster) can access both kubeconfig files for all clusters in the project. Users with lower-level project roles such as the *Cluster Editor* or the *Cluster Viewer* may not be able to access the kubeconfig file of the cluster.
As a rule, users with the Palette role [*Cluster Admin*](../../user-management/palette-rbac/project-scope-roles-permissions#cluster) can access the admin kubeconfig files for all clusters in the project. Users with lower-level project roles such as the *Cluster Editor* or the *Cluster Viewer* may not be able to access the kubeconfig file of the cluster.
karl-cardenas-coding marked this conversation as resolved.
Show resolved Hide resolved



Expand Down Expand Up @@ -75,7 +75,7 @@ The following table shows the *Cluster Admin* role or equivalent provides access
**Is OIDC Configured?** | **Is Spectro Proxy Enabled?** | **Access to Kubeconfig File** | **Access to Admin Kubeconfig File** |
--- | --- | --- | --- |
Yes | Yes | ✅ | ✅ |
No | Yes| ✅ | ✅ |
No | Yes| ❌ | ✅ |
Yes | No | ✅ | ✅ |

### Non-Cluster Admin
Expand Down