Closed sergeykorablin closed 11 months ago
sorry, looks like it's selinux configuration problem not sure it's correct or not but problem solved by:
sudo chcon -t container_runtime_exec_t /var/lib/kubelet/plugins/ru.yandex.s3.csi/geesefs
It's correct, csi-s3 uses a hack to escape the container and start geesefs on the host to survive csi-s3 pod restarts/upgrades :)
Strange problem. The bucket was dynamical created, but is not mounted and pod stuck in ContainerCreating state
but at the same time:
What I'm doing wrong?