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
hi @alpharde , thanks for creating this issue. To me it seems that 10.0.4.139 is the IP of the mysql DB and you want the vcluster to use this DB as the storage. The vcluster apiserver needs to be able to access this IP
So in context of vcluster APIServer there will outgoing connections from vcluster control plane to this IP.
However if you check the network policy in the helm chart, the except block is only used in case of vcluster workloads and not for control plane.
So my guess is as of now, isolated mode and external datastore aren't supposed to work in conjunction
What happened?
The vcluster pod cannot connect to external databases while network isolation is enabled.
What did you expect to happen?
vcluster being able to reach the external server.
How can we reproduce it (as minimally and precisely as possible)?
Create vcluster with
Anything else we need to know?
vcluster log:
2023-12-26 19:39:50 INFO loghelper/klog.go:24 starting kubernetes: preparing server: creating storage endpoint: building kine: dial tcp 10.0.4.139:3306: connect: connection refused {"component": "vcluster", "component": "k3s", "time": "2023-12-26T19:39:50Z", "level": "fatal"}
Host cluster Kubernetes version
Host cluster Kubernetes distribution
vlcuster version
Vcluster Kubernetes distribution(k3s(default)), k8s, k0s)
OS and Arch
The text was updated successfully, but these errors were encountered: