It was observed that qat-hw (when built right after qat-sw) is not built
correctly. Run make clean before the build (and back-up qat-sw since
clean removes it).
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
ipp-crypto repository did not provide a tag with the necessary changes
included until recently so we were using the master branch.
Now the tag was added (and master broke our build) so we move to use
it.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Also, move from ENV to ARG to be able to override the versions
using --build-arg option.
Note: releases qat1.7.l.4.3.0-00033 and older do not have consistent
download URLs so wget'ing those will fail from this commit onwards.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Add:
* Dockerfile that builds a container with OpenSSL 1.1.1 + QAT Engine
* Sample openssl-qat-engine-pod deployment yaml
The demo deployment yaml has the following dependencies:
* kata-runtime is installed and registered as the untrusted workload
handler
* QAT virtual function device configuration(s) (from QAT_Engine repo) are
available in /etc for the target hardware.
TODOs:
* readme.md
* move to RuntimeClass
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
