Pearl1594 commented on issue #11994: URL: https://github.com/apache/cloudstack/issues/11994#issuecomment-4025981933
> > [@chandrakantrai](https://github.com/chandrakantrai) Currently the issue is not reproducible on 4.22 release > > The API call with the size parameter is working fine > > cmk scale kubernetescluster id=<> size=2 > > dynamic change of service offering of a running cks cluster or vm is not supported for kvm hypervisor > > https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/virtual_machines.html#cpu-and-memory-scaling-for-running-instances > > This is the reason you are hitting the exception Scaling Kubernetes cluster : test failed, scaling Kubernetes cluster with running VMs on hypervisor KVM is not supported!" > > cc [@weizhouapache](https://github.com/weizhouapache) [@sureshanaparti](https://github.com/sureshanaparti) > > [@kiranchavala](https://github.com/kiranchavala) I totally agree with you that scaling vm with fixed offering is not supported in KVM. > > however, when scale a K8S, scaling often means the provision of new VMs. I am not sure if the inconsistent service offerings (e.g. user specify the service offering when scale Kubernetes cluster) of existing K8S nodes should block the scaling. IMHO, it should apply only on the new VMs. @weizhouapache I believe this behaviour has been historic. If one attempts to change the offering while changing the cluster size, it changes the offering on the pre-existing nodes as well (not just the new nodes that get added) - Tested this on 4.20.2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
