upgrade-manager
upgrade-manager copied to clipboard
keikoproj
Reliable, extensible rolling-upgrades of Autoscaling groups in Kubernetes
Refactoring goals: - Code re-factor - Cleaner code for maintainability - Better handling of edge cases without any API changes - Proper implementation of Reconcile() operation - Clear documentation of...
**Is this a BUG REPORT or FEATURE REQUEST?**: FEATURE REQUEST **What happened**: There are cases when a misconfigured PDB in a namespace can cause the cluster upgrade to be blocked....
**Is this a BUG REPORT or FEATURE REQUEST?**: improvements **What happened**: - One by one upgrade strategy is not fast enough to get 500-1000 nodes cluster done in short period...
**Is this a BUG REPORT or FEATURE REQUEST?**: Feature request **What happened**: Using an info level message with WARNING as the text in it, is not ideal. [Code snippet](https://github.com/keikoproj/upgrade-manager/blob/5396be7dad50bd42335796f7b03dcee5ee846def/controllers/rollingupgrade_controller.go#L345) which...
**Is this a BUG REPORT or FEATURE REQUEST?**: Bug **What happened**: If user configured MaxUnavailable, then keiko uses it as a batch for rollout. I.e. if it is set to...
1. It continues to rollout. 2. It fails to update object (because it is gone) ``` {"level":"error","ts":1605329457.7081757,"logger":"controllers.RollingUpgrade","msg":"failed to update status","rollingupgrade":"rollingupgrade-node-us-west-2a","error":"Operation cannot be fulfilled on rollingupgrades.upgrademgr.keikoproj.io \"rollingupgrade-node-us-west-2a\": StorageError: invalid object, Code:...
**Is this a BUG REPORT or FEATURE REQUEST?**: Bug **What happened**: use case I observed: 1. rollingUpgrade has drainTimeout configured (7 mins) 2. postDrain helper script fails. 3. drainTimeout specifies...
**Is this a BUG REPORT or FEATURE REQUEST?**: FEATURE In some setups it might be the case, when Node status is `Ready`, but it still fails custom checks (i.e. those...
**Is this a BUG REPORT or FEATURE REQUEST?**: Bug Report **What happened**: upgrade manager was running with `strategy.mode=eager`, and was unable to spin up new nodes due to incorrect IAM...
**BUG REPORT**: **What happened**: Error while installing the CRD as per README ``` $ kubectl apply -f https://raw.githubusercontent.com/keikoproj/upgrade-manager/master/config/crd/bases/upgrademgr.keikoproj.io_rollingupgrades.yaml error: error validating "https://raw.githubusercontent.com/keikoproj/upgrade-manager/master/config/crd/bases/upgrademgr.keikoproj.io_rollingupgrades.yaml": error validating data: ValidationError(CustomResourceDefinition.spec.validation.openAPIV3Schema.properties.spec.properties.strategy.properties.maxUnavailable): unknown field "x-kubernetes-int-or-string" in...
