We had used this build CoreOS-stable-2135.5.0-hvm (ami-02b51824b39a1d52a) as worker and master nodes upon setting manual kubernetes cluster.
We used the cluster to host our gitlab instance and other applications after some time there is a need to add another gitlab instance and additional worker nodes for resources.
As practice, we always used the latest stable build thus we used CoreOS-stable-2247.5.0-hvm (ami-047242a24cd6b4bc9)
$ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=2247.6.0
VERSION_ID=2247.6.0
BUILD_ID=2019-11-06-2138
PRETTY_NAME="Container Linux by CoreOS 2247.6.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
Environment
AWS
Expected Behavior
No "i/o timeout failed to register this runner"
Actual Behavior
i/o timeout failed to register this runner
Other Information
We tried adding worker nodes using previous build CoreOS-stable-2135.5.0-hvm (ami-02b51824b39a1d52a) and then the installation worked as expected. what could be causing the problem?
Issue Report
We had used this build CoreOS-stable-2135.5.0-hvm (ami-02b51824b39a1d52a) as worker and master nodes upon setting manual kubernetes cluster. We used the cluster to host our gitlab instance and other applications after some time there is a need to add another gitlab instance and additional worker nodes for resources.
As practice, we always used the latest stable build thus we used CoreOS-stable-2247.5.0-hvm (ami-047242a24cd6b4bc9)
Bug
Container Linux Version
CoreOS-stable-2247.5.0-hvm (ami-047242a24cd6b4bc9)
Environment
AWS
Expected Behavior
No "i/o timeout failed to register this runner"
Actual Behavior
i/o timeout failed to register this runner
Other Information
We tried adding worker nodes using previous build CoreOS-stable-2135.5.0-hvm (ami-02b51824b39a1d52a) and then the installation worked as expected. what could be causing the problem?