OpenShift quota management can be difficult

[qodfathr]

When a developer is using OpenShift as their development platform, especially when it is a shared platform for which they do not have complete or direct control or one on which they have been granted limited resources, it can be difficult to manage the various OpenShift artifacts (applications, memory, cores, routes, services, etc.) within these constraints. These resource constraints can lead to failures which are hard to diagnose -- for example, a build suddenly failing without any code changes -- often requiring the examination of various log files across different technologies (e.g. k8s and Jenkins).

If OpenShift quota limitations of all kinds were revealed to the developer at development time in the tools they use day-by-day and minute-by-minute, it has the potential to greatly reduce this diagnostic frustration as it would become far more self-evident that failures caused by quota limitations were happening.

Supporting Value Propositions

Realizing Experiences

See also

• Quota limits, when reached and resulting in deployment failures, are not reported to user in OSIO UI #874

[qodfathr]

Moved to OpenShift.io: https://openshift.io/openshiftio/openshiftio/plan/detail/1990