kiranchavala commented on issue #12783: URL: https://github.com/apache/cloudstack/issues/12783#issuecomment-4045583188
> Hi [@kiranchavala](https://github.com/kiranchavala) [@weizhouapache](https://github.com/weizhouapache) [@DaanHoogland](https://github.com/DaanHoogland) I think the conflicting step here is: > > `3. Navigate to one of the worker instances and unmanaged it` > > IMO it is expected the CKS cluster to go to Alert state as the unmanage VM operation will completely make CloudStack unaware of that VM (a different operation than removing a node from a CKS cluster, in which CloudStack will still be aware of that VM but removes it from the CKS cluster). > > I think we can add a validation on the `unmanageInstance` API to cover these cases, preventing to unmanage a VM from CloudStack if it is part of a CKS cluster. What do you think? validation on the unmanageInstance API for a vm which is part of cks cluster sounds good to me -- 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]
