balchua
balchua
Hi @lostwater, maybe this can help. To get your cluster working, you need to have your `pause` container using the registry that you can access from china. You can edit...
This is one of the things that we find need work. I think this was brought up before, the remediation as of now is to enable dns prior to the...
@mahmoodAtcom have you tried creating a `Service` with only 1 `NodePort` instead of `1000`. The only error i see in the logs of freeswitch is this. ``` ERROR: Failed to...
Looking at the logs, it looks like dqlite formed the cluster. Can you try running this on all the three nodes and paste it here? ```shell sudo -E /snap/microk8s/current/bin/dqlite -c...
Apologies for the experience you are having. > What is the current status of ha-cluster? Ha-cluster was the default from v 1.19 (i think), prior to that its using etcd...
I recall theres a `--force` argument in the remove-node that will remove it also from dqlite.
Can you check if you can do `ping microk8s-vm-1` from `microk8s-vm-0` and vice versa? If not can you try adding them to your `/etc/hosts`?
Oops sorry i missed rhat one. The `cluster-agent` logs may reveal something. One can force remove a node though. I think its `microk8s remove-node node_name --force`
@tobiolalusi its likely that the apiserver is restarting. Sometimes Network interface changes can cause the apiserver to be restarted by the apiservice-kicker component.
@adthonb does your cluster already have plenty of workloads running?