Hide Forgot
Description of problem: The usage of openshift.io/imagestreamimages will exceed the Hard Version-Release number of selected component (if applicable): openshift v0.5.3-6613-g37ffc85 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 How reproducible: always Steps to Reproduce: 1. Create quota for the project; more quota.yaml apiVersion: v1 kind: ResourceQuota metadata: name: object-counts spec: hard: configmaps: "10" openshift.io/imagestreamtags: "7" openshift.io/imagestreamimages: "14" persistentvolumeclaims: "4" replicationcontrollers: "20" secrets: "10" services: "10" 2. Create some image referenct or build some images; 3. Check the usage of openshift.io/imagestreamimages ; Actual results: The usage of openshift.io/imagestreamimages will acceed the Hard oc describe quota Name: object-counts Namespace: zhouy Resource Used Hard -------- ---- ---- configmaps 0 10 openshift.io/imagestreamimages 17 14 openshift.io/imagestreamtags 6 7 persistentvolumeclaims 0 4 replicationcontrollers 3 20 secrets 9 10 services 2 10 Expected results: The max usage of openshift.io/imagestreamimages should not exceed the Hard
The usage of openshift.io/imagestreamimages is counted lazily. If you tag a new image reference into the project, the usage will be incremented by 2 (1 for a reference in the spec and one for the status). The catch is that a first increment by 1 happens at once, the second increment happens during the next quota sync after the image is imported. Therefor if you are below the quota, you can tag several images over the limit until it is synced. Once the usage > hard limt, you won't be able to tag or push any more images though. An exception is a manual push or atomated build - a usage increment is immediate. Thus the admission checks will be precise while doing just builds.
Thanks for the answer, will verify this issue.