-
Notifications
You must be signed in to change notification settings - Fork 458
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
Custom VPC SSH into a VM #4908
Comments
The custom VPC is isolated from the host network. So if virtctl relies on network to do the ssh or port-forwarding work I think it is not possible from the host network. You need to run ssh in the same vpc network, or expose the VM through EIP and ssh to the EIP address. |
Would you be able to give me an example of this please? Using the EIP method? Or is it possible to port forward? I am able to VNC to the vm even if it is in a custom VPC |
Would you be able to provide an example? It still does not appear to be working. Even just sshing into pods would be a good test (as long as it is in a custom VPC) |
https://kubeovn.github.io/docs/v1.13.x/en/advance/ovn-eip-fip-snat/?h=eip https://kubeovn.github.io/docs/v1.13.x/en/guide/eip-snat/?h=eip https://kubeovn.github.io/docs/v1.13.x/en/guide/vpc/ maybe you can setup a sshd pod in your VPC for your testing |
Is there a way to accomplish this using some kind of ssh tunnel or other mechanism? Without having to use an EIP |
maybe, you can use a sshd pod to access your vm in the same VPC |
Hello all, had a quick question regarding default VPC and custom VPC routing to allow for SSH connections to a VM using Kubevirt. In the default VPC, when I create a VM, I can ssh into the vm using virtctl using the standard command specified (virtctl ssh VM). However, when I try to ssh into a VM that is in a custom VPC, it is not able to connect? Is there any specific routing commands I have to run for this to work? I have tried port-forwarding but to no avail. Thanks again and let me know if you have any follow up questions.
The text was updated successfully, but these errors were encountered: