Facing connection issue.
Closed this issue · 11 comments
Please can you guide me what was the problem.
it is normal updating cluster deployment kubevpn-traffic-manager image, because you are using newer client, we recommand that kubevpn client version should same as container image version
just wait it upgrade finished
Waiting long amount time before reporting.. Can we enable debug mode or source code to run directly to understand what was the issue is...?
maybe because image can not
pull image？you can describe pod to see k8s event, and more,kubevpn is open source for everyone you can check code to see what did it do
Waiting long amount time before reporting.. Can we enable debug mode or source code to run directly to understand what was the issue is...?
here is a flag --debug, you can see more log
@wencaiwulue Please can you guide me, how we can run the code locally.
I checkout the code.
install the Go..
Need your inputs to run the project locally am using windows .
Am new to go :) Please help to me run.
@wencaiwulue
C:\ci_projects\kubevpn\cmd\kubevpn>go run main.go connect
got cidr from cache
update ref count successfully
traffic manager already exist, reuse it
port forward ready
tunnel connected
Get "https://aks-xxxx-rg-wwwww-nonpr-8de222c5-0754bde13.hcp.eastus.azmk8s.io:443/api/v1/pods?timeout=30s&timeoutSeconds=30": read tcp 10.68.141.47:63213->10.21.105.196:443: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
prepare to exit, cleaning up
failed to release ip to dhcp, err: failed to get cm DHCP server, err: Get "https://aks-xxxxxx-rg-wwwww-nonpr-8de222c5-0754bde13.hcp.eastus.azmk8s.io:443/api/v1/namespaces/default/configmaps/kubevpn-traffic-manager": context deadline exceeded
can not update ref-count: update ref-count failed, increment: -1, error: client rate limiter Wait returned an error: context deadline exceeded
clean up successful
Getting above issue.
it is disconnecting our organization ciso vpn connection to..
using azure cloud aks private cluster
@wencaiwulue C:\ci_projects\kubevpn\cmd\kubevpn>go run main.go connect got cidr from cache update ref count successfully traffic manager already exist, reuse it port forward ready tunnel connected Get "https://aks-xxxx-rg-wwwww-nonpr-8de222c5-0754bde13.hcp.eastus.azmk8s.io:443/api/v1/pods?timeout=30s&timeoutSeconds=30": read tcp 10.68.141.47:63213->10.21.105.196:443: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. prepare to exit, cleaning up failed to release ip to dhcp, err: failed to get cm DHCP server, err: Get "https://aks-xxxxxx-rg-wwwww-nonpr-8de222c5-0754bde13.hcp.eastus.azmk8s.io:443/api/v1/namespaces/default/configmaps/kubevpn-traffic-manager": context deadline exceeded can not update ref-count: update ref-count failed, increment: -1, error: client rate limiter Wait returned an error: context deadline exceeded clean up successful
Getting above issue. it is disconnecting our organization ciso vpn connection to.. using azure cloud aks private cluster
here is link to binary , not need to build it manually, kubevpn_v1.1.30_windows_amd64.zip
"https://aks-xxxx-rg-wwwww-nonpr-8de222c5-0754bde13.hcp.eastus.azmk8s.io
you can parse command output: kubectl get cm kubevpn-traffic-manager -o yaml and nslookup aks-xxxx-rg-wwwww-nonpr-8de222c5-0754bde13.hcp.eastus.azmk8s.io ?
@gudipudipradeep hello, it should be solved in this commit, can you clone this repo and pull latest code, run command make kubevpn to build binary, and try it again?
@gudipudipradeep you can try latest version v1.1.31 to verify this bug whether fixed or not ~