I recently deployed selenium grid 4 on my kubernetes cluster using the helm chart https://github.com/SeleniumHQ/docker-selenium/blob/trunk/charts/selenium-grid/values.yaml. Everything works fine but when video recording is enabled, the sidecar video container records sessions with a null value. the logs of the container are as follows
2025-04-08 12:55:26,502 INFO supervisord started with pid 34
2025-04-08 12:55:27,504 INFO spawned: 'video-ready' with pid 82
2025-04-08 12:55:27,506 INFO spawned: 'video-recording' with pid 83
2025-04-08 12:55:27,593 [video.recorder] - Video folder exists: /videos
2025-04-08 12:55:27,593 INFO success: video-ready entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-04-08 12:55:27,593 INFO success: video-recording entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-04-08 12:55:27,595 [video.recorder] - Waiting for the display 10.106.100.177:99.0 is open
2025-04-08 12:55:27,827 [video.recorder] - Display 10.106.100.177:99.0 is open with dimensions 1920x1080
2025-04-08 12:55:27,828 [video.recorder] - Waiting for Node endpoint responds
2025-04-08 12:55:27,844 [video.recorder] - Session: null
null is created
2025-04-08 12:55:28,867 [video.recorder] - Start recording: true, video file name: nullnull.mp4
2025-04-08 12:55:28,868 [video.recorder] - Starting to record video
2025-04-08 12:55:28,876 [video.recorder] - Video recording started
[x11grab @ 0x55a77d638d40] Stream #0: not enough frames to estimate rate; consider increasing probesize
2025-04-08 12:55:29,888 [video.recorder] - Video recording in progress
2025-04-08 12:55:30,899 [video.recorder] - Video recording in progress
2025-04-08 12:55:32,567 [video.recorder] - Video recording stopped
2025-04-08 12:55:32,832 [video.recorder] - Session: null
null
null
null
null
null
null