Greatings from England!
Being prevalent in providing technical support elsewhere, I am an avid fan of thrashing the issue out to the best of ones abilities first. Consequently, I have put in over 200 hours and easily over a 1000 research tabs to try to resolve the issue myself but feel it is now time to turn to the lovely people here.
Thank you massively in advance if you can spare a few moments to help me out - it would be truly appreciated! Oh, and feel free to let me know if this can be better submitted.
My 1st ever k8s setup is hopefully using 4x Oracle instances and one private VPS with 6gb ram, all of which are running CentOS 7. Ideally, I’d like to test with 3x control planes and 2x workers but the logs bellow are for just 3x control planes and 1x worker as I am temporarily using one of the Oracle instances to rke up.
I’ve tried dozens of things from ensuring the servers times align, removing firewalld in place of IPTables, completely disabling firewalld, through to using different baremetals/virtuals to rke up, almost every attempt on fresh OS installs but all to no avail.
No matter what I try, I always end up with an error like the following:
Host [140.238.87.137] is not able to connect to the following ports: [140.238.67.47:2380, 140.238.67.47:2379, 140.238.65.66:2379, 140.238.65.66:2380, 140.238.87.137:2380, 140.238.87.137:2379]. Please check network policies and firewall rules]
Despite trying to decipher the rke up log below myself, I am sadly not adept enough to work out why the etcd containers never come up.
rke -d up
log from one of the Oracle instances with 3x control plans and 1x worker:
Please do let me know if further files/logs are required beyond the cluster.yml below and I will get the uploaded.
cluster.yml from one of the Oracle instances with 3x control plans and 1x worker:
kubectl version --client
Client Version: version.Info{Major:“1”, Minor:“17”, GitVersion:“v1.17.3”, GitCommit:“06ad960bfd03b39c8310aaf92d1e7c12ce618213”, GitTreeState:“clean”, BuildDate:“2020-02-11T18:14:22Z”, GoVersion:“go1.13.6”, Compiler:“gc”, Platform:“linux/amd64”}
rke --version
rke version v1.0.4
helm version
version.BuildInfo{Version:“v3.1.1”, GitCommit:“afe70585407b420d0097d07b21c47dc511525ac8”, GitTreeState:“clean”, GoVersion:“go1.13.8”}
docker version
Client: Docker Engine - Community
Version: 19.03.6
API version: 1.39 (downgraded from 1.40)
Go version: go1.12.16
Git commit: 369ce74a3c
Built: Thu Feb 13 01:29:29 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 03:47:25 2019
OS/Arch: linux/amd64
Experimental: false
Not sure why the docker client and engine versions are different having used the Rancher instal script but my research suggested that is no longer an issue these days.
Again, I cannot thank you enough in advance for any pointer as to how to progress as as you can probably guess, I’ve been pulling my hair out for some time now.
Warmest regards,
-binvius-