You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'd like to open a question / raise a request to support CSI volumes for nautobot-static volume. My reason (actually a need) for this setup is due to 2 constraints we have in place:
only read-only file systems are allowed and
no PersistentVolumes are allowed.
The only supported writeable volumes are: a bucket (GCP) (and the only way is to use CSI ephemeral volume) and emptyDir (not really useful for static files and their collecting on each pod startup)
Hence I open this issue and have an intention to create also a PR that could address this specific limitation on my end.
My main concern is to deal with static files (nautobot-static volume) that is already currently hard-coded within your templates. Other locations for jobs/ or media/ was possible for me mount via already existing extraVolumes and extraVolumeMounts.
Happy to discuss some ideas or different approach within PR itself. But given the limitations on my end (within the company), I think there is not much options left on my end :-)
WDYT?
The text was updated successfully, but these errors were encountered:
Hi, I'd like to open a question / raise a request to support CSI volumes for
nautobot-static
volume. My reason (actually a need) for this setup is due to 2 constraints we have in place:The only supported writeable volumes are: a bucket (GCP) (and the only way is to use CSI ephemeral volume) and
emptyDir
(not really useful for static files and their collecting on each pod startup)Hence I open this issue and have an intention to create also a PR that could address this specific limitation on my end.
My main concern is to deal with static files (
nautobot-static
volume) that is already currently hard-coded within your templates. Other locations forjobs/
ormedia/
was possible for me mount via already existingextraVolumes
andextraVolumeMounts
.Happy to discuss some ideas or different approach within PR itself. But given the limitations on my end (within the company), I think there is not much options left on my end :-)
WDYT?
The text was updated successfully, but these errors were encountered: