Upgrade/ks 2.1.1 #182
Merged
Upgrade/ks 2.1.1 #182
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cc8c61a to
1d4a62e
Compare
add gpu node add nvidia label to gpu node mark more labels to gpu nodes support all possible csi storage classes allow more wait time for files from first master node shorten start time to fail fast add upgrade scripts adjust dns upgrade dependent roles set up after all node ready Add dns warm-up use variable for cluster api server instead of hard-coded adjust init order fix caddy issue adjust upgrade process Fix metrics issue Align with parallel in-place upgrade create lb in background to save time workaround pek3 tag not found replace cut with awk to avoid false positive columns allow cluster function normally even creation was failed upgrade csi qingcloud to 1.1.1 add more time to wait kube-lb created for k8s only cluster support custom ks components fix upgrade issue allow client SSH to k8s nodes address testing comments Address comments improve dns resolve custom ssh key & all-in-one support auto bind eip update snapshot for upgrade fix ks components install issue allow user ssh to all nodes provide more information when failed to delete nodes update notice when update msg provide more msg when deleting masters fix ssh key issue add coredns configmap from ks-installer for ref update qingcloud ccm and fix client kubectl issue fix client creation failed issue fix upgrade client issue and add workers issue refactor preScaleOut allow custom cpu model of all k8s nodes fix audit policy issue refactor audit policy volume config allow pvc expansion for storageclass fix overlay2 after upgrade to avoid layer lost Update images fix upgrade issues - LB file and kube-apiserver certs allow install ks without metrics server move some logic to client node to unblock upgrade move upgrade logic to client node fix etcd can't start after upgrade enable all ks components when upgrade adjust upgrade snapshot file structure fix wrong ks modules count during upgrade update docker mirrors and some images specify start order for k8s nodes and client node fix permission issue for docker overlay2 fix upgrade issues fix resolv-conf when replaced ubuntu 16.04 with 18.04 add pre_check for upgrade fix create failure fix ha cluster issues update snapshot for upgrade update docker images disable scale master nodes use human readible storage class names update kvm image not change default sc when upgrade fix kubelet auto restart issue fix loadbalancer issue update ks-installer image to fix mysql issue fix lb issue when one master is down update snapshots for upgrade refactor update images increase lb creation timeout add nfs-client docker image fix lbcli issue update images fix docker image permission issue fix recover issue review
1d4a62e to
c78f520
Compare
This was referenced May 19, 2020
Closed
Closed
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., usage docs, etc.: