On Thu, Apr 25, 2019 at 10:10:26PM +0200, Thorsten Kukuk wrote:
like Cilium would run as DeamonSets on Kubernetes
where CRI-O surely has to be started before. To fix this, I changed the upstream
behavior for the CNI plugin directory validation that not existing directories
will be created automatically by CRI-O . This makes the following lines in
the spec obsolete for the next major (v1.15.0) release:
# This is the additional directory where cri-o is going to look up for CNI
# plugins installed by DaemonSets running on Kubernetes (i.e. Cilium).
mkdir -p /opt/cni/bin
I would prefer to fix it "correct": Add /opt/cni/bin as directory to the
filelist of the "right" RPM, whichever this is. Or use systemd-tmpfiles
to create it.
/opt is not a part of the / ro BTRFS parition. Wouldn't be that a
problem for transactional updates and RPM packages? Using
systemd-tmpfiles is probably better.
But Sascha already fixed the problem with his upstream patch, so I guess
we can just remove the %post step with the next release of CRI-O and we
don't need to think about anything else.
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org