k8s-sig-cluster-lifecycleawskubesprayhigh-availabilityansiblekubernetes-clustergcekubernetesbare-metal

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 29cfe2b8eb

ant31-patch-1

component_hash_update/master

dependabot/pip/cryptography-45.0.3

floryut-patch-1

lean/pre-commit-hook-2

master

master-patch-updates

optional-coredns

packet-test

pre-commit-hook

reduce-vm-requests

release-2.10

release-2.11

release-2.12

release-2.13

release-2.14

release-2.15

release-2.16

release-2.17

release-2.18

release-2.19

release-2.20

release-2.21

release-2.22

release-2.23

release-2.24

release-2.25

release-2.26

release-2.27

release-2.28

release-2.7

release-2.8

release-2.9

remove-ci-ok-to-test

revert-11831-ipv6only

symlinketcd

test-CI

test-ci

test-precommit

test/flatcar-4081

update-approvers-ant31

1.3.0

1.3.0_k1.1.3

1.4.0

1.5.0

test-tag-1

v1.0

v1.0.0

v1.0.1

v1.1

v1.1.0

v1.1.3

v2.0.0

v2.0.1

v2.1.0

v2.1.1

v2.1.2

v2.10.0

v2.10.3

v2.10.4

v2.11.0

v2.11.1

v2.11.2

v2.12.0

v2.12.1

v2.12.10

v2.12.2

v2.12.3

v2.12.4

v2.12.5

v2.12.6

v2.12.7

v2.12.8

v2.12.9

v2.13.0

v2.13.1

v2.13.2

v2.13.3

v2.13.4

v2.14.0

v2.14.1

v2.14.2

v2.15.0

v2.15.1

v2.16.0

v2.17.0

v2.17.1

v2.18.0

v2.18.1

v2.18.2

v2.19.0

v2.19.1

v2.2.0

v2.2.1

v2.20.0

v2.21.0

v2.22.0

v2.22.1

v2.22.2

v2.23.0

v2.23.1

v2.23.2

v2.23.3

v2.24.0

v2.24.1

v2.24.2

v2.24.3

v2.25.0

v2.25.1

v2.26.0

v2.27.0

v2.28.0

v2.3.0

v2.4.0

v2.5.0

v2.6.0

v2.7.0

v2.8.0

v2.8.1

v2.8.2

v2.8.3

v2.8.4

v2.8.5

v2.9.0

Branches Tags

${ item.name }

Create branch ${ searchTerm }

from '29cfe2b8eb'

${ noResults }

kubespray/.gitlab-ci

History

Rick Haan 5cba8b1614 Wait for kube-apiserver availability before starting upgrade (#6243) * Wait for kube-apiserver availability before starting upgrade I am experiencing a timing issue when upgrading from kubespray 2.11.0(k8s 1.15.3) to kubespray 2.12.6(k8s 1.16.9). The certificates get replaced in `kubeadm-secondary-legacy.yml` and kube-apiserver notices a mismatch (for a fraction of a second) between `apiserver.crt` and `apiserver.key` which causes it to restart. And sometimes ( ~ 1 out of 5 upgrades) the kube-apiserver isn't back on time for the start of the upgrade task. It fails when kubeadm checks with the kube-apiserver to start the upgrade. The kube-apiserver returns a `connect: connection refused`. I have created this small task to check the availability of the kube-apiserver before starting the upgrade, so that the upgrade will run without an issue. Signed-off-by: Rick Haan <rickhaan94@gmail.com> * Fix markdownlint * Remove old CI Co-authored-by: Maxime Guyot <maxime@root314.com>		5 years ago
..
gce.yml	Support for Oracle Linux (#3655)	5 years ago
lint.yml	Use kubespray/kubespray:v2.11.0 for CI (#5363)	5 years ago
packet.yml	Re introduce CI for upgrades (#5427)	5 years ago
shellcheck.yml	Always rebase on master before running a job (#4616)	6 years ago
terraform.yml	Wait for kube-apiserver availability before starting upgrade (#6243)	5 years ago