Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

The InstancesV1 interface handled this for us by combining the ProviderName and InstanceID values; the new interface requires us to do it manually
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: matttrach <matttrach@gmail.com>

For 1.24 and earlier, the svclb pods need a ServiceAccount so that we can allow their sysctls in PSPs
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Fix dualStack test

Signed-off-by: Manuel Buil <mbuil@suse.com>

* Replace ioutil package
* check integration test null pointer
* Remove rotate retries
Signed-off-by: Derek Nola <derek.nola@suse.com>

Taint the first node so that the helm job doesn't run on it. In a real cluster the helm job would eventually succeed once all the servers were upgraded and had the new chart tarball.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Use setup-go action to cache dependencies

Add journalctl logs to E2E tests

Replace ETCD-JOIN-STABLE-SECOND with ETCD-JOIN-LATEST-FIRST. We don't
support joining down-level servers to existing clusters, as the new
down-level server will try to deploy older versions of the packaged
manifests.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Derek Nola <derek.nola@suse.com>

Signed-off-by: jongwooo <han980817@gmail.com>

CA cert will never be equal to the serving-kube-apiserver cert so it seems like a copy-paste error.
Signed-off-by: Vladimir Pouzanov <farcaller@gmail.com>

The kubelet port can be overridden by users; we shouldn't assume its always 10250
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

We should be reading from the hijacked bufio.ReaderWriter instead of
directly from the net.Conn. There is a race condition where the
underlying http handler may consume bytes from the hijacked request
stream, if it comes in the same packet as the CONNECT header. These
bytes are left in the buffered reader, which we were not using. This was
causing us to occasionally drop a few bytes from the start of the
tunneled connection's client data stream.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

If CCM and ServiceLB are both disabled, don't run the cloud-controller-manager at all;
this should provide the same CLI flag behavior as previous releases, and not create
problems when users disable the CCM but still want ServiceLB.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

... and drop legacy ClusterID support.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Add cluster reset test

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Shylaja Devadiga <shylaja@rancher.com>

Signed-off-by: Shylaja Devadiga <shylaja@rancher.com>

Add flannel-external-ip when there is a k3s node-external-ip

E2E: Groundwork for PR runs

Signed-off-by: Manuel Buil <mbuil@suse.com>

Signed-off-by: matttrach <matttrach@gmail.com>

Signed-off-by: Derek Nola <derek.nola@suse.com>

Signed-off-by: Derek Nola <derek.nola@suse.com>

Signed-off-by: Derek Nola <derek.nola@suse.com>

* Update to v1.25.1
* bump go version
Signed-off-by: matttrach <matttrach@gmail.com>

Restore original INSTALL_K3S_SKIP_DOWNLOAD behavior

Signed-off-by: Derek Nola <derek.nola@suse.com>