bernardodemarco commented on PR #9102: URL: https://github.com/apache/cloudstack/pull/9102#issuecomment-2980772012
> in the UI we are preventing that case as the user is requested to set a node per offering instead of a global one @nvazquez, yes > do you think we can add the same check for the API? The problem with this approach is that it would break backwards compatibility, right? Prior to the changes, the `serviceofferingid` was used to change the service offering of all nodes of a k8s cluster. With the current patch, it can still be used to achieve such action and, thus, the API behavior seems to be ok. The only drawback is that the cluster's metadata is not fully consistent. -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
