feat: Add STIG/FIPS-compliant Network Operator deployment instructions #275
Conversation
| Platform Support <platform-support.rst> | ||
| Getting Started with Kubernetes <getting-started-with-kubernetes.rst> | ||
| Getting Started with Red Hat OpenShift <getting-started-with-openshift.rst> | ||
| NVIDIA Network Operator Government Ready <install-network-operator-gov-ready.rst> |
There was a problem hiding this comment.
Do we need NVIDIA Network Operator in the tree link?
Maybe stick with same wording as Getting Started with
There was a problem hiding this comment.
I use the same naming as GPU Operator has. Should we change the title somehow?
There was a problem hiding this comment.
I think that here Government Ready is enough in the left tree.
e0ne
force-pushed
the
stig
branch
2 times, most recently
from
9ee0494 to
9a5829e
Compare
| --set sriov-network-operator.images.sriovConfigDaemon=doca-driver-stig-fips \ | ||
| --set sriov-network-operator.imagePullSecrets={ngc-secret} \ | ||
| --set sriovNetworkOperator.enabled=true | ||
| --set nfd.enabled=true |
There was a problem hiding this comment.
should nfd.enabled be false in this case?
There was a problem hiding this comment.
Why should we disable NFD? it's STIG/FIPS compliant
There was a problem hiding this comment.
You added a section that says users need to deploy nfd separately. AFAIK with nfd.enabled=true in the helm chart we will deploy our own downstream fork chart?
e0ne
changed the title
e0ne
force-pushed
the
stig
branch
7 times, most recently
from
67d9332 to
88a0362
Compare
Documentation previewhttps://mellanox.github.io/network-operator-docs/review/pr-275 |
e0ne
force-pushed
the
stig
branch
6 times, most recently
from
24575ad to
5953aa4
Compare
Signed-off-by: Ivan Kolodiazhnyi <[email protected]>
3 participants
No description provided.