[PPML] Add deploy_intel_sgx_device_plugin_for_kubernets in QuickStart (#3512)
* [PPML] Add deploy_intel_sgx_device_plugin in QuickStart * Append k8s-deploy doc in index.rst
This commit is contained in:
parent
c75ad40e67
commit
30b4c3d9d5
2 changed files with 28 additions and 0 deletions
|
|
@ -0,0 +1,27 @@
|
|||
# Deploy the Intel SGX Device Plugin for Kubenetes
|
||||
|
||||
The instructions in this section are modified from the [Intel SGX Device Plugin homepage][intelSGX], to which please refer should questions arise.
|
||||
|
||||
## Prerequisites
|
||||
Prerequisites for building and running these device plugins include:
|
||||
- Appropriate hardware. ([3rd Gen Intel Xeon Scalable Processors][GIXSP])
|
||||
- A fully configured Kubernetes cluster
|
||||
- A working Go environment, of at least version v1.16
|
||||
|
||||
Here we would want to deploy the plugin as a DaemonSet, so pull the [source code][pluginCode]. In the working directory, compile with
|
||||
``` bash
|
||||
make intel-sgx-plugin
|
||||
make intel-sgx-initcontainer
|
||||
```
|
||||
Deploy the DaemonSet with
|
||||
```bash
|
||||
kubectl apply -k deployments/sgx_plugin/overlays/epc-register/
|
||||
```
|
||||
Verify with (replace the `<node name>` with your own node name)
|
||||
```
|
||||
kubectl describe node <node name> | grep sgx.intel.com
|
||||
```
|
||||
|
||||
[intelSGX]: https://intel.github.io/intel-device-plugins-for-kubernetes/cmd/sgx_plugin/README.html
|
||||
[GIXSP]: https://www.intel.com/content/www/us/en/products/docs/processors/xeon/3rd-gen-xeon-scalable-processors-brief.html
|
||||
[pluginCode]: https://github.com/intel/intel-device-plugins-for-kubernetes
|
||||
|
|
@ -82,6 +82,7 @@ BigDL Documentation
|
|||
doc/PPML/Overview/trusted_big_bata_analytics_and_ml.md
|
||||
doc/PPML/Overview/trusted_fl.md
|
||||
doc/PPML/QuickStart/build_kernel_with_sgx.md
|
||||
doc/PPML/QuickStart/deploy_intel_sgx_device_plugin_for_kubernets.md
|
||||
doc/PPML/QuickStart/trusted-serving-on-k8s-guide.md
|
||||
|
||||
.. toctree::
|
||||
|
|
|
|||
Loading…
Reference in a new issue