-
Notifications
You must be signed in to change notification settings - Fork 829
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
Cant get cluster members #5143
Comments
Let's get started with this. |
Hello there , |
cc @chaosi-zju for help |
Ok so as you told me i targeted the karmada config using this command : just joining the cloud cluster is the issue that remains .. |
Hi @oussexist, I will answer your above two questions. First
I spent some time today verifying this problem for you, here are two cases:
Second
here is a command option for ...
# Specify external IPs(load balancer or HA IP) which used to sign the certificate
karmadactl init --cert-external-ip 10.235.1.2 --cert-external-dns www.karmada.io
Options:
--cert-external-dns='':
the external DNS of Karmada certificate (e.g localhost,localhost.com)
--cert-external-ip='':
the external IP of Karmada certificate (e.g 192.168.1.2,172.16.1.2)
... So, you can add Then, even though we initialize karmada using local ip, you can modify your ip in kubeconfig to public ip, and with |
Hello there ,
PS: Although , i tried to initialize the cluster with the public addr as an endpoint and its getting it in the kubeconfig file but the karmada always uses the internal one example :
Edited: Well , i found an advertise flag on init command that may be helpfull on that case , I am checking it rn |
Hello again @chaosi-zju , This is the full log :
|
Hi @oussexist, sorry to hear this error.
|
By the way , this error happens only on cloud cluster although it's nsg is just allowing all so , i dont think it's a security group issue..
|
use just like |
|
Probably same unresolved issue #5105 can you refer to #5105 (comment), and check whether it can give you some help? |
As you said:
I suspect that there is something to do with the container network of your cloud environment, which makes the karmada-apiserver unable to connect to etcd. |
Hi @oussexist, so did you come to any new conclusions later? |
Hi @chaosi-zju , Sorry i was kind of busy, |
Ok so , Hello again and sorry for being a bit late , anyway i initialized karmada on my local cluster and put it with a public ip and assured the 32443 port is accesible tho ( this is kind of important ) , and then after fixing the cloud cluster from network issues it connected fine . |
Hi, does the network issue refers to If yes, then I'm curious how you fixed this network issue at last, haha |
Hello again , I was on holidays . Edited : Also i have a little problem , when i create a deployment through propagation file , and get deployments i found the local deployment is not ready ! |
i think by adding the |
I think we can Close this issue , the propagation problem was just a lack of concentration from me , |
Hello there ,
I have an on-prem cluster and a cloud cluster so , if i do the init on the on-prem cluster so it'll be the controlplane host cluster lets say i want to join members with create token command it'll give me the register command and use that command on the cloud cluster , it won't be able to register since the ip adresse is for a local network , althoguht the local cluster have network acces and can ping google.com just fine , what to do ?
Do I need to init on the cloud cluster and join the local one or what ?
even tho if i did init on the cloud cluster and want to join the local cluster , the api server config ( karmada config file ) i should manually move it the local cluster ? and when joining give the path to the file i manually created with the same content as the cloud karmada config inited ?
P.S : I tried karmada init on the local cluster and joined it but when i try to use karmada get cluster command i get this : error: failed to list all member clusters in control plane, err: the server could not find the requested resource (get clusters.cluster.karmada.io)
The text was updated successfully, but these errors were encountered: