Merge pull request #8170 from shubham-pampattiwar/update-scc-docs

Update Openshift SCC docs link
This commit is contained in:
Xun Jiang/Bruce Jiang
2024-09-05 10:52:38 +08:00
committed by GitHub
3 changed files with 3 additions and 2 deletions

View File

@@ -0,0 +1 @@
Update Openshift SCC docs link

View File

@@ -502,7 +502,7 @@ advanced configuration options for `BackupPVC`, allowing users to fine-tune acce
[3]: file-system-backup.md
[4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/
[5]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation
[6]: https://docs.openshift.com/container-platform/3.11/admin_guide/manage_scc.html
[6]: https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html
[7]: https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv
[8]: api-types/backupstoragelocation.md
[9]: supported-providers.md

View File

@@ -138,7 +138,7 @@ To mount the correct hostpath to pods volumes, run the node-agent pod in `privil
If node-agent is not running in a privileged mode, it will not be able to access pods volumes within the mounted
hostpath directory because of the default enforced SELinux mode configured in the host system level. You can
[create a custom SCC](https://docs.openshift.com/container-platform/3.11/admin_guide/manage_scc.html) to relax the
[create a custom SCC](https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html) to relax the
security in your cluster so that node-agent pods are allowed to use the hostPath volume plugin without granting
them access to the `privileged` SCC.