Scaling a service changes the wrong deployment ---------------------------------------------- Key: JBIDE-23030 URL: https://issues.jboss.org/browse/JBIDE-23030 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.1.AM3 Reporter: Fred Bricon Assignee: Jeff Cantrill Priority: Critical In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. The workaround is to open the properties view and issue a scale command on a deployment directly. However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP