Tuomas Katila

It seems that a colon in volumes/binds is a known issue: https://github.com/docker/docker-py/issues/2041 https://github.com/moby/moby/issues/39293 https://github.com/moby/moby/issues/22825

I'd add another item to your list: Simplify GPU plugin deployment options. I would vote to only have two examples: * NFD + GPU-plugin with shared-dev-num=1 and monitoring * Basic...

Would something like this work? ``` ARG BASEIMG=debian:unstable-slim FROM ${BASEIMG} ARG USE_DNF=0 COPY ./LICENSE /licenses/intel-device-plugins-for-kubernetes/LICENSE RUN if [ $USE_DNF -eq 0 ]; then \ apt-get update && apt-get install -y...

Not sure if it's related, but we've seen somewhat similar with e2e fpga. Seems like a Pod is scheduled with the generic resource name (Pod goes to Pending) and when...

I wonder if it's some upgrade test where the changed labels causes confusion. edit: nevermind, apparently I can't read. The fix that is causing this was related to the operator...

I'm trying to think of a way that would not include bumping up the version number and creating a patch release. If we update the name permanently, what are the...

I submitted a question to the community operators project: https://github.com/k8s-operatorhub/community-operators/issues/4434

After discussing with @hj-johannes-lee I'd propose a transient deployment name change in the operator bundle: 1. Release `0.30.0` with a different deployment name (only in operator bundle) 2. Keep deployment...

As discussed, let's keep the deployment name same in the bundle (as it is in 0.30.0), and change the deployment name in the project yamls. This will require manual changes...

We don't currently have a way to configure SR-IOV via GPU plugin. That would have to be done manually unfortunately. When SR-IOV is configured, the _gpu.intel.com/i915_ resource could be leveraged...