Skip to content

Commit 5e597d2

Browse files
Merge pull request #1439 from mythi/PR-2023-029
doc and version updates
2 parents 819d302 + 93bea62 commit 5e597d2

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -166,10 +166,10 @@ as a standalone [SGX Admission webhook image](cmd/sgx_admissionwebhook/README.md
166166
#### Intel SGX EPC memory registration
167167

168168
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
170170
[SGX device plugin](cmd/sgx_plugin/README.md)
171171
operator deployment and NFD is configured to register the Intel SGX EPC memory
172-
extended resource reported by the hook.
172+
extended resource.
173173

174174
Containers requesting Intel SGX EPC resources in the cluster use
175175
`sgx.intel.com/epc` resource which is of

cmd/sgx_plugin/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Table of Contents
1919
The Intel SGX device plugin and related components allow workloads to use Intel SGX on
2020
platforms with SGX Flexible Launch Control enabled, e.g.,:
2121

22-
- 3rd Generation Intel® Xeon® Scalable Platform, code-named “Ice Lake”
22+
- 3rd/4th Generation Intel® Xeon® Scalable Platforms
2323
- Intel® Xeon® E3
2424
- Intel® NUC Kit NUC7CJYH
2525

@@ -122,7 +122,7 @@ $ kubectl apply -k 'https://github.com/intel/intel-device-plugins-for-kubernetes
122122
$ kubectl apply -k 'https://github.com/intel/intel-device-plugins-for-kubernetes/deployments/sgx_plugin/overlays/epc-nfd/'
123123
```
124124

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.
126126

127127
The following kustomization is used for this approach:
128128
```bash

demo/openssl-qat-engine/Dockerfile

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
FROM ubuntu:22.04 as builder
22

33
ARG QATLIB_VERSION="23.02.0"
4-
ARG QAT_ENGINE_VERSION="v0.6.19"
4+
ARG QAT_ENGINE_VERSION="v1.1.0"
55
ARG ASYNC_NGINX_VERSION="v0.5.0"
66
ARG IPSEC_MB_VERSION="v1.3"
7-
ARG IPP_CRYPTO_VERSION="ippcp_2021.7"
7+
ARG IPP_CRYPTO_VERSION="ippcp_2021.7.1"
88

99
RUN apt update && \
1010
env DEBIAN_FRONTEND=noninteractive apt install -y \
@@ -74,7 +74,7 @@ COPY --from=builder /usr/bin/*_sample* /usr/bin/
7474
COPY --from=builder /usr/lib/libqat.so.3.0.3 /usr/lib/
7575
COPY --from=builder /usr/lib/libusdm.so.0.1.0 /usr/lib/
7676
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/
7878
COPY --from=builder /usr/lib/x86_64-linux-gnu/engines-3/qatengine.so /usr/lib/x86_64-linux-gnu/engines-3/qatengine.so
7979
COPY --from=builder /var/www/ /var/www/
8080
COPY --from=builder /usr/lib64/nginx/* /usr/lib64/nginx/

0 commit comments

Comments
 (0)