Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volumes packs/virtualenvs/configs as volumeDevices in "ensure-packs-volumes-are-writable" job #426

Open
jalbertoa opened this issue Dec 9, 2024 · 0 comments

Comments

@jalbertoa
Copy link

The "-job-ensure-packs-volumes-are-writable" is key to allow starting the st2 application properly, but is assuming the volumes should be mounted as volumeMounts+mountPath.
When using certain storage providers and set the 'block' type volumes (and set ReadWriteMany accessMode), these needs to be mounted as volumeDevices+devicePath or we will get a
Unable to attach or mount volumes: unmounted volumes=[st2-pack-configs-vol st2-packs-vol st2-virtualenvs-vol], unattached volumes=[st2-pack-configs-vol k8tz kube-api-access-rxb2c st2-packs-vol st2-virtualenvs-vol]: volume st2-pack-configs-vol has volumeMode Block, but is specified in volumeMounts; volume st2-packs-vol has volumeMode Block, but is specified in volumeMounts; volume st2-virtualenvs-vol has volumeMode Block, but is specified in volumeMounts
I'm wrong and there is another way to customize it or it is needed extending the chart to adapt the job or skip this validation?

Thanks in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant