Closed msivosuo closed 4 years ago
More detailed goals:
qat plugin to be deployable with kubectl apply -k qat_plugin/VERSION
(VERSION
being devel or a release tag)
gpu plugin to be deployable with kubectl apply -k gpu_plugin/...
, possibly configurable command line parameters if needed
fpga plugin to be deployable with kubectl apply -k fpga_plugin/...
, different kustomizations for different run modes (preprogrammed vs orchestrated)
Reasoning for the work:
@askervin FYI, deployments directly from the repo works:
kubectl apply -k github.com/intel/intel-device-plugins-for-kubernetes.git/deployments/qat_dpdk_app/test-crypto1?ref=master
(VERSION being devel or a release tag)
This may not be necessary since we can already do
$ kubectl kustomize github.com/intel/intel-device-plugins-for-kubernetes.git/deployments/qat_dpdk_app/test-crypto1?ref=release-0.15
$ kubectl kustomize github.com/intel/intel-device-plugins-for-kubernetes.git/deployments/qat_dpdk_app/test-crypto1?ref=master
I did consider doing the direct-from-URL deploys in the docs updates, which in the case of using the default images and setup would avoid pulling the sources down. But, one change at a time....
PRs contributing to this issue:
Goals: