| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2053 |
Sorry, something went wrong.
|
@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2209 |
Sorry, something went wrong.
|
@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2251 |
Sorry, something went wrong.
|
@vladimirpetrov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1425 |
Sorry, something went wrong.
|
@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1429 |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1430 |
Sorry, something went wrong.
|
@vladimirpetrov a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-2233)
|
Sorry, something went wrong.
|
Trillian test result (tid-2232)
|
Sorry, something went wrong.
|
Trillian test result (tid-2234)
|
Sorry, something went wrong.
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-2252)
|
Sorry, something went wrong.
|
The vmware failure is same as in the health check PR, so not caused by this PR. Tests LGTM. |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM based on manual testing.
SystemVM template improvements:
Tested fresh deployments with KVM (CentOS 7), VMWare 67u3 and XCP-NG 8.2.
Tested upgrades from:
ACS version: 4.15
Hypervisor: KVM CentOS 8
Mgmt OS: CentOS 8
ACS version: 4.15
Hypervisor: VMWare 65u2
Mgmt OS: CentOS 7
ACS version: 4.15
Hypervisor: XenServer 7.2
Mgmt OS: Ubuntu 18
ACS version: 4.15
Hypervisor: VMWare 67u3
Mgmt OS: CentOS 7
ACS version: 4.14
Hypervisor: KVM CentOS 7
Mgmt OS: CentOS 7
ACS version: 4.15
Hypervisor: XCP-NG 8.2
Mgmt OS: CentOS 8
ACS version: 4.15.2
Hypervisor: KVM CentOS 8
Mgmt OS: CentOS 8
ACS version: 4.15.2
Hypervisor: VMWare 67u3
Mgmt OS: CentOS 7
ACS version: 4.15.2
Hypervisor: XCP-NG 8.2
Mgmt OS: Ubuntu 20
Kubernetes Cluster auto-scaling
Tested scenarios:
Deploy a v1.20 kubernetes cluster (not HA), setup scaling (min 1, max 2 worker nodes), increase the load, make sure the cluster scales up, stop the load, make sure the cluster scales down.
Deploy a v1.21 kubernetes cluster (not HA), setup scaling (min 1, max 2 worker nodes), increase the load, make sure the cluster scales up, stop the load, make sure the cluster scales down.
Deploy a v1.20 kubernetes cluster (not HA), setup scaling (min 1, max 2 worker nodes), increase the load, make sure the cluster scales up, stop the load, make sure the cluster scales down, upgrade the cluster to v.1.21 and repeat the procedure.
Deploy a v1.21 kubernetes cluster (not HA), setup scaling (min 1, max 3 worker nodes), increase the load, make sure the cluster scales up, change the scaling parameters to min 1, max 2 worker nodes, make sure the cluster scales down to 2 worker nodes, stop the load, make sure the cluster scales down to 1 worker node.
Deploy a v1.20 kubernetes cluster (HA enabled), setup scaling (min 1, max 2 worker nodes), increase the load, make sure the cluster scales up, stop the load, make sure the cluster scales down.
Deploy a v1.21 kubernetes cluster (HA enabled), setup scaling (min 1, max 2 worker nodes), increase the load, make sure the cluster scales up, stop the load, make sure the cluster scales down.
Sorry, something went wrong.
|
Ping @alexandremattioli or @andrijapanicsb are you lgtm on this as well? |
Sorry, something went wrong.
|
@rhtyd - @alexandremattioli has already provided their review - #4329 (comment) |
Sorry, something went wrong.
|
Ah okay thanks @Pearl1594; just a note to @alexandremattioli - please use Github's review -> LGTM that way it's easy to track approvals. |
Sorry, something went wrong.
|
@andrijapanicsb @alexandremattioli please advise after your tests/review, thanks |
Sorry, something went wrong.
|
Alex is reviewing this, so I will not. Thx |
Sorry, something went wrong.
|
@nvazquez all good with tests. I've used this for some customer demos and worked very well, retested this week and all good. LGTM |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
Adding AutoScaling support for cks
Kubernetes PR : kubernetes/autoscaler#3629
Also replaces CoreOS with Debian
Fixes #4198
TODO: Remove the templateid and template name from KubernetesClusterResponse and DB since the templates can vary after acs upgrades
Types of changes
How Has This Been Tested?
TODO