-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
quay-3.7
-
False
-
None
-
False
when following step 5 from 7.1.2. Manually Deploying Clair , the old secret is regenerated.
- locate secret being used by quay-app pod
[sbhavsar@sbhavsar ~]$ oc describe pod quay-app Environment: QE_K8S_CONFIG_SECRET: sam-registry-quay-config-secret-k74t87mg4d
- delete this secret
[sbhavsar@sbhavsar ~]$ oc delete secret sam-registry-quay-config-secret-k74t87mg4d
secret "sam-registry-quay-config-secret-k74t87mg4d" deleted
[sbhavsar@sbhavsar ~]$ oc get secret | grep sam-registry-quay-config-secret-k74t87mg4d sam-registry-quay-config-secret-k74t87mg4d Opaque 1 2s
- Editing secret `am-registry-quay-config-secret-k74t87mg4d` does not work as operator reverts it to original state.
- The only way to add below parameters is to scale down operator
FEATURE_SECURITY_NOTIFICATIONS: trueFEATURE_SECURITY_SCANNER: trueSECURITY_SCANNER_V4_ENDPOINT: http://clairv4