andrijapanicsb opened a new pull request, #14605:
URL: https://github.com/apache/cloudstack/pull/14605

   CloudManaged Kubernetes nodes can currently be resized individually through 
the Instances view or VM APIs. 
   This leaves the VM resources out of sync with the cluster configuration and 
reported capacity and later messes up cluster-level scaling.
   
   This change prevents individual compute offering changes for those nodes. 
Resizing remains available through the Kubernetes cluster scaling operations. 
Ordinary instances and ExternalManaged clusters retain their existing behaviour.
   
   Fixes #14553
   
   ### Changes
   
   - Add compute offering validation to KubernetesServiceHelper, following the 
existing CKS validation patterns.
   - Apply the validation to scaleVirtualMachine and the deprecated 
changeServiceForVirtualMachine API, including administrator variants.
   - Check cluster membership so the restriction also covers adopted nodes.
   - Include the cluster management type in VM responses and hide the Instances 
scale action for CloudManaged members.
   
   ### Cluster scaling
   
   Validation is limited to the VM API entry points. Internal offering-change 
methods remain unchanged for cluster-wide and node-group resizing, including 
the paths used by #14223.
   
   ### Tests
   
   - 57 focused Java tests passed.
   - 5 focused UI tests passed.
   - Maven reactor build passed across the 34 required modules.
   - Patch applicability checked against the head of #14223.
   
   Tests cover blocked API operations, permitted ordinary and ExternalManaged 
instances, adopted nodes, UI visibility, and internal stopped/live resizing.
   
   ### Scope
   
   This change guards compute offering replacement. Dynamic resource changes 
through updateVirtualMachine details and the resource-detail APIs remain 
separate follow-up work.


-- 
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]

Reply via email to