woose/90DaysOfDevOps
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Day 59 - added more resource links

Browse Source
This commit is contained in:
Dean Lewis 2023-03-29 18:32:27 +01:00
parent 3905495192
commit 8b0b80892b
No known key found for this signature in database
GPG Key ID: FB8A62795F0ADC69
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
2023/day59.md
View File

@ -485,3 +485,4 @@ On [Day 60](/day60.md)](/day60.md), we will look at OpenShift Projects Creation,
- [Using the legacy restricted SCC in OCP 4.11+](https://access.redhat.com/articles/6973044) - [Using the legacy restricted SCC in OCP 4.11+](https://access.redhat.com/articles/6973044)
- [Role-based access to security context constraints](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.html#role-based-access-to-ssc_configuring-internal-oauth) - [Role-based access to security context constraints](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.html#role-based-access-to-ssc_configuring-internal-oauth)
- You can specify SCCs as resources that are handled by RBAC. This allows you to scope access to your SCCs to a certain project or to the entire cluster. - You can specify SCCs as resources that are handled by RBAC. This allows you to scope access to your SCCs to a certain project or to the entire cluster.
- Kubernetes.io - [Configure a Security Context for a Pod or Container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/)