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
I'd like to be able to record video like in normal selenoid. Doing so will require attaching another container in the pod (probably only when enableVideo is requested as a cap).
I'm assuming video endpoints would need to be exposed on seleniferous since it doesn't seem to have them yet. Selenosis probably also should get new args for video container image and such.
Let me know if you have any concerns, or questions with this, or if I'm not noticing something important. I'm still familiarizing myself with these two code bases.
The text was updated successfully, but these errors were encountered:
Let me know if you have any concerns, or questions with this, or if I'm not noticing something important. I'm still familiarizing myself with these two code bases.
I'm not interested in adding a video recording feature to this project.
I'd like to be able to record video like in normal selenoid. Doing so will require attaching another container in the pod (probably only when enableVideo is requested as a cap).
Existing logic that drives this in selenoid
https://github.com/aerokube/selenoid/blob/68ce8aa754e473fe4c961178e5974edd337e625c/service/docker.go#L498-L546
Basically if the video cap is requested, create container and forward a bunch of context to it. Transposing this to a k8s approach doesn't look too bad to me (basically append the container in
https://github.com/alcounit/selenosis/blob/main/platform/kubernetes.go#L395-L432
in the event that the cap is requested)
I'm assuming video endpoints would need to be exposed on seleniferous since it doesn't seem to have them yet. Selenosis probably also should get new args for video container image and such.
Let me know if you have any concerns, or questions with this, or if I'm not noticing something important. I'm still familiarizing myself with these two code bases.
The text was updated successfully, but these errors were encountered: