From the RFE template > 3. What is the nature and description of the request? In the documentation it is specified the following: ~~~ io.openshift.non-scalable An image might use this variable to suggest that it does not support scaling. The UI will then communicate this to consumers of that image. Being not-scalable basically means that the value of replicas should initially not be set higher than 1. ~~~ Given the complexity to limit the number of running instances for an image. It will be useful though to have a warning in the UI when the replication controller is asked to scale to a number bigger than 1 in a similar way as when trying to scale down to zero. > 4. Why does the customer need this? (List the business requirements here) The customer wants to limit the possibility of an incident while someone scale up by mistake to minimize the business impact. > 5. How would the customer like to achieve this? (List the functional requirements here) As an image developer I want to inform the image users that there is a limitation in having more than one running instance of this image. As a web console user I would like to be notified whenever I click on the "up arrow" in order to scale up the application warning me about the existing limitation. > 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Given a Docker image containing the following label in the Dockerfile LABEL io.openshift.non-scalable true In the Web console the user will try to click the "up arrow" in order to scale up the application from 1 to any other number. After the click a modal would appear informing the user about the existing limitation so that the user can ignore or continue at his/her own risk. > 10. List any affected packages or components. Openshift web console
As mentioned in the discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1284104 the UI requires changes from the UI before we can do anything.
Sorry, UI requires changes from the API
This bug has been identified as a dated (created more than 3 months ago) bug. This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, as it is currently not part of the products immediate priorities. Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.