SeleniumHQ / SeleniumHQ/docker-selenium
vnc is not working with helm template deployment on gke used 5900 port can you please help on it
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
What happened?
i have provided below values in values.yaml and applied helm template
chromeNode:
port: 6666 # Update SE_NODE_PORT to 6666
nodePort: 30666 # Specify a NodePort to expose SE_NODE_PORT to outside traffic
ports:
- 5900 # You can give port number alone, default protocol is TCP
- 7900
service:
type: NodePort # Expose entire ports on Service via NodePort
ports:
- name: vnc-port
protocol: TCP
port: 5900
targetPort: 5900
nodePort: 30590 # Specify a NodePort to expose VNC port
- name: novnc-port
protocol: TCP
port: 7900
targetPort: 7900
# NodePort will be assigned randomly if not set
still i am not able to see the video browsing.
video uploader is also not working , i am not seeing the videos in gcs bucket
videoRecorder:
enabled: true
imageRegistry: selenium
Image of video recorder
imageName: video
Image of video recorder
imageTag: ffmpeg-6.1.1-20240505
Image pull policy (see https://kubernetes.io/docs/concepts/containers/images/#updating-images)
imagePullPolicy: IfNotPresent
Image pull secret (see https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/)
targetFolder: "/videos"
uploader:
enabled: true
# Where to upload the video file e.g. remoteName://bucketName/path. Refer to destination syntax of rclone https://rclone.org/docs/
destinationPrefix: "gcs://seleniumgrid_bucket/vnc"
# What uploader to use. See .videRecorder.rclone for how to create a new one.
name:
configFileName: upload.conf
entryPointFileName: upload.sh
# For environment variables used in uploader which contains sensitive information, store in secret and refer envFrom
# Set config for rclone via ENV var with format: RCLONE_CONFIG_ + name of remote + _ + name of config file option (make it all uppercase)
#secrets:
secrets:
RCLONE_CONFIG_GCS_TYPE: "s3"
RCLONE_CONFIG_GCS_PROVIDER: "GCS"
RCLONE_CONFIG_GCS_ENV_AUTH: "true"
RCLONE_CONFIG_GCS_ACL: "private"
RCLONE_CONFIG_GCS_PROJECT_NUMBER: "856041249079"
RCLONE_CONFIG_GCS_OBJECT_ACL: "private"
secretName: "gcs-service-account"
secretKey: "key.json"
Command used to start Selenium Grid with Docker (or Kubernetes)
helm repo add docker-selenium https://www.selenium.dev/docker-selenium
helm search repo docker-selenium
helm install/upgrade selenium-grid docker-selenium/selenium-grid
Relevant log output
video browsing and video recorder and uploader need to work
Operating System
gke
Docker Selenium version (image tag)
4.9.0-20230421
Selenium Grid chart version (chart version)
4.9.0-20230421
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied values.yaml settings and the Selenium Grid Helm chart configuration for the Chrome node service, VNC ports, videoRecorder, and uploader. Reproduce the deployment on GKE, inspect the rendered Helm manifest and relevant pod or uploader logs, and verify that VNC/noVNC is reachable and recordings arrive in the specified GCS bucket.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, helm, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100