-
Feature
-
Resolution: Duplicate
-
Critical
-
None
-
None
-
False
-
False
Currently, CSO checks the pod spec for any pull secrets and uses those credentials when connecting to the secscan API endpoint:
However, OpenShift allows global pull secrets to be defined as well:
It would be great if we could implement a feature that would allow CSO to use a global pull secret in addition to checking individual pod specs for one. This will allow pods that do not have a pull secret explicitly defined and are in fact relying on the global, cluster pull secret to be scanned by CSO.
- relates to
-
PROJQUAY-1603 Container-security-operator does not take pull secrets of OpenShift into account
- Closed