-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
quay-v3.8.6
-
False
-
-
False
-
User Experience
-
-
Customer is running a operator-managed Quay instance without Clair or Quay Mirror. However, the corresponding HorizontalPodAutoscalers are still created. As they do not contain any associated pods, customer regularly get warning events that are "false positives" and should not be created.
$ oc get hpa -n my-quay
NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
registry-clair-app Deployment/clair-app <unknown>/90%, <unknown>/90% 2 10 0 116d
registry-quay-app Deployment/registry-quay-app 46%/90%, 1%/90% 2 20 2 116d
registry-quay-mirror Deployment/quay-mirror <unknown>/90%, <unknown>/90% 2 20 0 116d
$ oc get events -n magic-plat-quay
LAST SEEN TYPE REASON OBJECT MESSAGE
75s Normal Valid secretstore/magic-plat-quay store validated
23s Warning FailedGetScale horizontalpodautoscaler/registry-clair-app deployments/scale.apps "clair-app" not found
47m Normal Updated externalsecret/registry-quay-config-bundle Updated Secret
23s Warning FailedGetScale horizontalpodautoscaler/registry-quay-mirror deployments/scale.apps "quay-mirror" not found
2m5s Normal ComponentsCreationSuccess quayregistry/registry All objects created/updated successfully
$ oc get quayregistry -n my-quay -o yaml
...
spec:
components:
- kind: clair
managed: false
- kind: clairpostgres
managed: false
- kind: mirror
managed: false
- kind: monitoring
managed: false
- kind: horizontalpodautoscaler
managed: true
- kind: objectstorage
managed: true
- kind: postgres
managed: true
- kind: quay
managed: true
overrides:
env:
- name: NO_PROXY
value: cluster.local,.local,.svc,127.0.0.1,192.168.0.0/16,localhost,proxy-user
- name: HTTP_PROXY
value: http://proxy-user:8080
- name: HTTPS_PROXY
value: http://proxy-user:8080
- kind: redis
managed: true
- kind: route
managed: true
- kind: tls
managed: true
configBundleSecret: registry-quay-config-bundle
...