File tree 3 files changed +7
-7
lines changed
3 files changed +7
-7
lines changed Original file line number Diff line number Diff line change @@ -166,10 +166,10 @@ as a standalone [SGX Admission webhook image](cmd/sgx_admissionwebhook/README.md
166
166
#### Intel SGX EPC memory registration
167
167
168
168
The Intel SGX EPC memory available on each node is registered as a Kubernetes extended resource using
169
- node-feature-discovery (NFD). A custom NFD source hook is installed as part of
169
+ node-feature-discovery (NFD). An NFD Node Feature Rule is installed as part of
170
170
[ SGX device plugin] ( cmd/sgx_plugin/README.md )
171
171
operator deployment and NFD is configured to register the Intel SGX EPC memory
172
- extended resource reported by the hook .
172
+ extended resource.
173
173
174
174
Containers requesting Intel SGX EPC resources in the cluster use
175
175
` sgx.intel.com/epc ` resource which is of
Original file line number Diff line number Diff line change @@ -19,7 +19,7 @@ Table of Contents
19
19
The Intel SGX device plugin and related components allow workloads to use Intel SGX on
20
20
platforms with SGX Flexible Launch Control enabled, e.g.,:
21
21
22
- - 3rd Generation Intel® Xeon® Scalable Platform, code-named “Ice Lake”
22
+ - 3rd/4th Generation Intel® Xeon® Scalable Platforms
23
23
- Intel® Xeon® E3
24
24
- Intel® NUC Kit NUC7CJYH
25
25
@@ -122,7 +122,7 @@ $ kubectl apply -k 'https://github.com/intel/intel-device-plugins-for-kubernetes
122
122
$ kubectl apply -k ' https://github.com/intel/intel-device-plugins-for-kubernetes/deployments/sgx_plugin/overlays/epc-nfd/'
123
123
```
124
124
125
- The second approach has a lesser deployment footprint. It does not require NFD, but a helper daemonset that creates ` sgx.intel.com/capable='true' ` node label and advertises EPC capacity to the API server.
125
+ The second approach has a lesser deployment footprint. It does not require NFD, but a helper daemonset that creates ` sgx.intel.com/capable='true' ` node label and advertises EPC capacity directly to the API server.
126
126
127
127
The following kustomization is used for this approach:
128
128
``` bash
Original file line number Diff line number Diff line change 1
1
FROM ubuntu:22.04 as builder
2
2
3
3
ARG QATLIB_VERSION="23.02.0"
4
- ARG QAT_ENGINE_VERSION="v0.6.19 "
4
+ ARG QAT_ENGINE_VERSION="v1.1.0 "
5
5
ARG ASYNC_NGINX_VERSION="v0.5.0"
6
6
ARG IPSEC_MB_VERSION="v1.3"
7
- ARG IPP_CRYPTO_VERSION="ippcp_2021.7"
7
+ ARG IPP_CRYPTO_VERSION="ippcp_2021.7.1 "
8
8
9
9
RUN apt update && \
10
10
env DEBIAN_FRONTEND=noninteractive apt install -y \
@@ -74,7 +74,7 @@ COPY --from=builder /usr/bin/*_sample* /usr/bin/
74
74
COPY --from=builder /usr/lib/libqat.so.3.0.3 /usr/lib/
75
75
COPY --from=builder /usr/lib/libusdm.so.0.1.0 /usr/lib/
76
76
COPY --from=builder /usr/lib64/libIPSec_MB.so.1 /usr/lib/x86_64-linux-gnu/
77
- COPY --from=builder /usr/local/lib/libcrypto_mb.so.11.5 /usr/lib/x86_64-linux-gnu/
77
+ COPY --from=builder /usr/local/lib/libcrypto_mb.so.11.6 /usr/lib/x86_64-linux-gnu/
78
78
COPY --from=builder /usr/lib/x86_64-linux-gnu/engines-3/qatengine.so /usr/lib/x86_64-linux-gnu/engines-3/qatengine.so
79
79
COPY --from=builder /var/www/ /var/www/
80
80
COPY --from=builder /usr/lib64/nginx/* /usr/lib64/nginx/
You can’t perform that action at this time.
0 commit comments