Use a sidecar container
If you deploy Datalore On-Premises using Kubernetes, you can configure its agents to run as a pod with two containers that share a file system: an unprivileged agent container and a privileged sidecar container.
In this setup, the sidecar system container uses FUSE to mount WebDAV and data sources as local filesystems, exposing them to the container running the notebook agent via shared volumes. Unless you use Reactive mode, the container that runs the notebook agent does not require elevated privileges.
Configure a sidecar agent
Add a volume to the pod:
- id: sidecar-agent ... yaml: ... volumes: - name: sidecar-agent-volume emptyDir: { }In the agent container, add the
SIDECAR_PORTandSIDECAR_MOUNT_ENABLEDenvironment variables:... containers: - name: datalore-agent image: jetbrains/datalore-agent:2026.1 env: - name: SIDECAR_PORT value: "8088" - name: SIDECAR_MOUNT_ENABLED value: "true" volumeMounts: - name: sidecar-agent-volume mountPath: /data mountPropagation: HostToContainerAdd the sidecar container to the pod:
- name: sidecar-mounter repository: jetbrains/datalore-sidecar-mounter:2026.1 pullPolicy: IfNotPresent versionOverride: "" ports: - containerPort: 8088 name: sidecar-port env: - name: SIDECAR_PORT value: "8088" securityContext: privileged: true volumeMounts: - name: sidecar-agent-volume mountPath: /data mountPropagation: Bidirectional
24 February 2026