with docker 23.0.0, the builder defaults to Buildx which changed
how multi-stage builds are done. It looks the images used during
builds are no longer part of "docker images" which make the image
base layer test to fail:
Testing docker.io/intel/intel-deviceplugin-operator:devel base layer
Error: No such object: gcr.io/distroless/static
ERROR: failed to inspect gcr.io/distroless/static
Therefore, we must ensure gcr.io/distroless/static is pulled before
the image base layer is checked.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
This should fix the following set-version issue:
./scripts/set-version.sh bla
fatal: charts: no such path in the working tree.
Use 'git <command> -- <path>...' to specify paths that do not exist locally.
Signed-off-by: Ed Bartosh <eduard.bartosh@intel.com>
set-version exits with 0 even if there are errors in the script.
This makes CI to ignore set-version failures.
Doing some weird sh magic + adding -eu option should fix the issue.
- used different pods for PF and VF workloads
- increased waiting timeout to 200s
- used 'epoll' waiting mode for test apps
- decreased amount of packets from 128 to 8 for test apps
- output pod logs
- done small code optimisations
Signed-off-by: Ed Bartosh <eduard.bartosh@intel.com>
Added LABELs (name, vendor, version, release, summary, description) to all plugins and updated
scripts/set-version.sh script to include the LABEL version='<image-tag>' by passing TAG parameter
to make set-version TAG=<image-tag>
Signed-off-by: chaitanya1731 <chaitanya.kulkarni@intel.com>
Jenkinsfile had a disabled stage that connected to a
BMAAS CI to run scripts/jenkins/* to do QAT validation.
These are no longer used so drop them.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
All but one (VPU) of the published container images can be built with
static binaries which allows us to use distroless/static as the
base image. Moreover, when combined with stripping the plugin binaries,
we can get both build time and image size savings.
This is the part 1 (out of 2) of the rework. Part 2 will finish the
change by making some adjustments to VPU plugin image and moving the
FPGA/SGX/GPU initcontainers to distroless/static too.
Partial: #516
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Signed-off-by: Ed Bartosh <eduard.bartosh@intel.com>
fpga: make AFU resource name 63 char long
webhook: drop mode from README
webhook: extend mappings description
webhook: tighten CRD definitions
webhook: drop mapping to non-existing afuId
explicitly state mappings names can be in any format
use consistent terminology across fpga webhook and plugin
The certificate got signed for wrong service name (fallback default
"webhook-svc") due to incorrectly passed parameter. This showed as
"http: TLS handshake error from ... tls: bad certificate"
error in webhook pod logs.
Fixes: #303
Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
Setting --output-dir DIR enables writing contents of the secret to DIR
instead of creating the secret in the cluster. This allows creating
the secret later, for instance during fpga_plugin kustomization.
Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
This commit adds bash scripts with the proper granularity for each sub-stage,
needed for QAT device main stage validation.
Signed-off-by: Rivera Gonzalez, Julio C <julio.c.rivera.gonzalez@intel.com>
This commit adds a script that is (primarily) used in Dockerfiles
to install runtime Go dependencies' LICENSE/NOTICE files into the
image and modifies the Dockerfiles to use the script.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
opae-nlb-demo name is more descriptive about the content and becomes
base image agnostic.
Also, set ENTRYPOINT similar to what we did with other images
and deployment files.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Currently we have hardcoded mapping from human readable names of
AFs and FPGA regions like arria10-nlb0 to the resource names
produced by the FPGA device plugin. This is not sustainable
long term solution.
Implement CRD based mappings so that a new mapping can be added or
removed dynamically by cluster admins with CRD resources.
