Merge pull request #694 from martyav/420-new-user-guides-authentication-8

420 new user guides authentication 8/8
This commit is contained in:
Billy Tat
2023-06-21 13:10:29 -07:00
committed by GitHub
9 changed files with 36 additions and 0 deletions
@@ -2,6 +2,10 @@
title: Configuring a Global Default Private Registry
---
<head>
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry"/>
</head>
:::note
This page describes how to configure a global default private registry from the Rancher UI, after Rancher is already installed.
@@ -2,6 +2,10 @@
title: Pod Security Standards (PSS) & Pod Security Admission (PSA)
---
<head>
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards"/>
</head>
[Pod Security Standards (PSS)](https://kubernetes.io/docs/concepts/security/pod-security-standards/) and [Pod Security Admission (PSA)](https://kubernetes.io/docs/concepts/security/pod-security-admission/) define security restrictions for a broad set of workloads.
They became available and were turned on by default in Kubernetes v1.23, and replace [Pod Security Policies (PSP)](https://kubernetes.io/docs/concepts/security/pod-security-policy/) in Kubernetes v1.25 and above.
@@ -2,6 +2,10 @@
title: Pod Security Admission (PSA) Configuration Templates
---
<head>
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/psa-config-templates"/>
</head>
[Pod Security admission (PSA)](./pod-security-standards.md) configuration templates are a Rancher custom-defined resource (CRD), available in Rancher v2.7.2 and above. The templates provide pre-defined security configurations that you can apply to a cluster:
- `rancher-privileged`: The most permissive configuration. It doesn't restrict the behavior of any pods. This allows for known privilege escalations. This policy has no exemptions.