-
Bug
-
Resolution: Done
-
Blocker
-
None
-
False
-
False
-
Quay Enterprise
-
Undefined
-
To recreate the issue create quay registry with following your config.yaml file provided to quay-operator
DEFAULT_TAG_EXPIRATION: 4w SERVER_HOSTNAME: quay.apps.dgangaia.apacshift.support
Rollout the deployment and ensure you are able to push and pull images
Now launch Quay config app, Change the DEFAULT_TAG_EXPIRATION to 2w and also add super user and reconfigure Quay
No new pods are deployed, so deleted quay-operator and new quay-operator pod didnt reconcile aswell
2021-05-07T02:06:01.001Z INFO setup starting server on port 70712021-05-07T02:06:01.001Z INFO setup starting server on port 70712021-05-07T02:06:01.001Z INFO setup starting manager2021-05-07T02:06:01.001Z INFO controller-runtime.manager starting metrics server {"path": "/metrics"}2021-05-07T02:06:01.001Z INFO controller-runtime.controller Starting EventSource {"controller": "quayregistry", "source": "kind source: /, Kind="}2021-05-07T02:06:01.001Z INFO controller-runtime.controller Starting EventSource {"controller": "quayecosystem", "source": "kind source: /, Kind="}2021-05-07T02:06:01.102Z INFO controller-runtime.controller Starting Controller {"controller": "quayregistry"}2021-05-07T02:06:01.102Z INFO controller-runtime.controller Starting workers {"controller": "quayregistry", "worker count": 1}2021-05-07T02:06:01.102Z INFO controller-runtime.controller Starting Controller {"controller": "quayecosystem"}2021-05-07T02:06:01.102Z INFO controller-runtime.controller Starting workers {"controller": "quayecosystem", "worker count": 1}2021-05-07T02:06:01.102Z INFO controllers.QuayRegistry begin reconcile {"quayregistry": "quay-enterprise/registry"}2021-05-07T02:06:01.202Z INFO controllers.QuayRegistry successfully retrieved referenced `configBundleSecret` {"quayregistry": "quay-enterprise/registry", "configBundleSecret": "registry-quay-config-bundle-cq44p", "resourceVersion": "2630832"}2021-05-07T02:06:01.234Z INFO controllers.QuayRegistry cluster supports `Routes` API2021-05-07T02:06:01.835Z INFO controllers.QuayRegistry detected router canonical hostname: apps.dgangaia.apacshift.support2021-05-07T02:06:01.955Z INFO controllers.QuayRegistry cluster supports `ObjectBucketClaims` API2021-05-07T02:06:01.955Z INFO controllers.QuayRegistry `ObjectBucketClaim` exists2021-05-07T02:06:02.055Z INFO controllers.QuayRegistry found `ObjectBucketClaim` and credentials `Secret`, `ConfigMap`2021-05-07T02:06:02.055Z INFO controllers.QuayRegistry `ObjectBucketClaim` is using in-cluster endpoint, ensuring we use the fully qualified domain name2021-05-07T02:06:02.056Z INFO controllers.QuayRegistry monitoring is only supported in AllNamespaces mode. Disabling component monitoring2021-05-07T02:06:03.065Z DEBUG controller-runtime.controller Successfully Reconciled {"controller": "quayregistry", "request": "quay-enterprise/registry"}2021-05-07T02:06:03.065Z DEBUG controller-runtime.manager.events Warning {"object": {"kind":"QuayRegistry","namespace":"quay-enterprise","name":"registry","uid":"46b8a6de-92bd-4c46-a065-60e95963f01c","apiVersion":"quay.redhat.com/v1","resourceVersion":"2631039"}, "reason": "MonitoringComponentDependencyError", "message": "could not check for monitoring support: monitoring is only supported in AllNamespaces mode. Disabling component monitoring"}
So we manually scalled down Quay app pod and scaled it back to see if the config gets updated but still not effect , from Quay-app pod we see DEFAULT_TAG_EXPIRATION set to 4w
Please fix the reconcile from Quay config app, we have may users reporting the same behavior
- relates to
-
PROJQUAY-2185 Quay CR modified after making changes via the config tool
- Closed
-
PROJQUAY-1961 Quay-operator should reconcile if anything changes in configBundleSecret secret
- Closed