Red Hat Bugzilla – Bug 1284104
Restrict number of replicas
Last modified: 2017-08-23 05:01:36 EDT
This is a web console/UI issue: https://github.com/openshift/origin/issues/6134
I agree that what you linked is relevant, however, the customer that raised this issue to our attention, yielding this bug, tested it via the CLI as well and still experienced the issue.
Also it seems that it is likely an issue with setting io.openshift.non-scalable as they seemed to have followed the documentation properly.
I noticed in the github link Dan Mace included, that a potential warning was discussed as well. Has this been discussed any further anywhere else, implemented or completely abandoned? Would it also be possible to implement a warning for the CLI? As I indicated in my last update, this issue was found using the UI AND the CLI.
Not abandoned, but there was some discussion in the issue about how we want to implement it.
any plan to fix this ?
Would also like to see this.
(In reply to Samuel Padgett from comment #5)
> Not abandoned, but there was some discussion in the issue about how we want
> to implement it.
> Adding Clayton.
Eric, just FYI the `io.openshift.non-scalable` label on the image is not a functional label but was intented as a hint/suggestion that the replica count should be 1 for this image (typical for a standalone database images, or statefull applications etc.).
I don't think having this restriction in ReplicaSet or ReplicationController will be accepted in upstream, but I can clearly see the use case for this in StatefullSets where you still want to manage the Pod under StatefulSet because of PVC/migration/evacuation, but you never want to scale that image up as it might break terribly.