Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

502 error occurs when kasmweb service is connected with dns url through nginx-ingress-controller in k8s environment. #110

Open
yoongeon1206 opened this issue Jul 22, 2024 · 2 comments

Comments

@yoongeon1206
Copy link

yoongeon1206 commented Jul 22, 2024

Hi,

I have verified kasmvnc in my local environment and think it will be useful for developers. To show kasmvnc to development team members, I created a helm chart to deploy to K8s.

We are trying to deploy the kasmweb Docker image (ubuntu-focal-dind:1.15.0) on Kubernetes and attempting to connect to DNS through nginx-ingress-controller. However, even though all DNS connections are made properly, the Kasm VNC screen is not visible.

  1. ( OK ) ubuntu-focal-dind:1.15.0 runs well without problems when run locally with the docker command.
  2. ( Not work ) When deployed to k8s and connected to DNS through nginx-ingress-controller, error 502 occurs. (port: 6901)
  3. ( OK ) When deployed on k8s and connected through port-forwarding, the VNC screen is displayed.

In above case 2, When connecting to other services, it connects without problem. I confirmed that only the kasmweb service was not connected with DNS on K8S. Is there any settings or env option that we need to connect to DNS in KASMWEB VNC service? or do we need to purchase a license to connect? Has anyone had the same issue as me or can help?

it seems to have to be updated something in dockerfile.

I simply share how i set up kasmvnc on k8s as follows.


Deployment

spec:
  containers:
  - name: kasmweb
    image: kasmweb/ubuntu-focal-dind:1.13.0
    ports:
    - containerPort: 6901

Service

ports:

  • protocol: TCP
    port: 6901
    targetPort: 6901

Ingress

spec:
rules:

  • host: develop.xxxxxxx.com
    http:
    paths:
    • path: /
      pathType: Prefix
      backend:
      service:
      name: kasm-service
      port:
      number: 6901
@MSandro
Copy link

MSandro commented Sep 2, 2024

I have the same problem, since kasmweb forces HTTPS and BasicAuth on port 6901, it seems to need additional configuration.

@orshih6
Copy link

orshih6 commented Sep 30, 2024

i also have the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants