y-system-ci opened a new issue, #14412: URL: https://github.com/apache/cloudstack/issues/14412
### The required feature described as a wish Hi team, I am creating a K8S cluster that utilizes a network share and a Security Group. However, the instances being automatically provisioned are not having the Security Group applied. As a result, the Management Server cannot connect to the cluster's API endpoint (on port 6443), which prevents the UI from displaying the `kube.conf` connection details—unlike the behavior seen with CKS or Isolated deployments. I attempted to manually attach the Security Group to the instance via the Cloud Management Console (CMK), but I received an error stating that the instance must be powered off before the Security Group can be added. `(CI) > update virtualmachine id=a779691d-4195-4cf8-8c65-2b16a3bd91eb securitygroupids=ece24195-d429-45b1-8212-77ca86c3593f 🙈 Error: (HTTP 530, error code 4250) Failed to update Instance, due to: VM a779691d-4195-4cf8-8c65-2b16a3bd91eb must be stopped prior to update security groups (CI) > ` Cloudstack version `4.23.0` <img width="1578" height="503" alt="Image" src="https://github.com/user-attachments/assets/582c298a-73a1-4668-848f-f7f5aabab9c9"; /> Controll Node and worker still running service inside <img width="1252" height="625" alt="Image" src="https://github.com/user-attachments/assets/6895a641-032b-4148-bffb-3153eab1ff25"; /> Can we add Security group without stop Instance ? Thanks team. -- 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]
