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.

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

feat: add network policies reference #425

Merged
merged 1 commit into from
Jul 3, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 1 addition & 0 deletions changes/425.added
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Documentation on network policies.
14 changes: 2 additions & 12 deletions docs/source/reference/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,5 @@ For a step-by-step guide on how to deploy the application on Kubernetes, please
This section provides a reference of how various Kubernetes resources should look like once deployed with the default settings.
Substra is distributed as Helm charts, and most values can be customized to accommodate the requirements of your environment.

Pod Security Standards
----------------------

All pods in a Substra deployment are compliant with the *baseline* policy of the
`Pod Security Standards <https://kubernetes.io/docs/concepts/security/pod-security-standards>`_.

All pods can run as non-root, with two exceptions:

* If the builder feature is enabled (at least one backend per network must have the ability to build images), Kaniko pods used for building images run as root.
* If the private CA feature is used, the initContainer `add-cert` runs as root.

We are working on ensuring that all pods except the two listed above are compliant with the *restricted* policy.
.. include:: pss.rst
.. include:: netpol.rst
Loading
Loading