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

   ### Description
   
   This PR adds support for specifying affinity groups during CKS (CloudStack 
Kubernetes Service) cluster creation, allowing users to control VM placement 
for high availability.
   
   ### Changes:
   
   - New `nodeaffinitygroups` parameter for `createKubernetesCluster` API
   - Supports per-node-type _(CONTROL, WORKER, ETCD)_ affinity group assignment
   - New kubernetes_cluster_affinity_group_map table for normalized storage
   
   
   ### Design doc: 
   
   
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+users+to+select+affinity+group+during+managed+CKS+cluster+creation
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [x] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [x] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   TODO
   
   ### How Has This Been Tested?
   
   - Tested on simulator environment
   - Added Unit tests
   - Test against KVM (TODO)
   
   #### How did you try to break this feature and the system with this change?
   
   - Invalid affinity group UUID
   - Invalid node type
   - Duplicate node type entries
   - Clusters without affinity groups (backward compatibility)
   


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