- 
    
Bug
 - 
    Resolution: Unresolved
 - 
    
Normal
 - 
    None
 - 
    4.18, 4.19
 
- 
        Quality / Stability / Reliability
 - 
        False
 - 
        
 - 
        None
 - 
        Moderate
 - 
        None
 
- 
        None
 - 
        Rejected
 - 
        NI&D Sprint 272, NI&D Sprint 273
 - 
        2
 
- 
        None
 - 
        None
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 
Context
- aws-load-balancer/pre-install step creates AWS credentials for operator and operand (controller).
 - It's done via creation of CredentialsRequest resource. CRD which is managed by Cloud Credentials Operator (CCO).
 - Most of the recent versions of ALBO needed AWS credentials in a form of secret before the operator can be installed. That's why we did the credentials provisioning in the CI as a custom workflow.
 - Now ALBO can provision credentials for itself at the startup. So, CredentialsRequest for the operator is not needed to be pre created in the CI.
 
Description
CredentialsRequest may fail to provision the secret because the namespace where it should provision it (aws-load-balancer-operator) doesn't exist at the pre-install step.
Since operator will try to create the same CredentialsRequest at the start-up if it was already created by the CI, it won't do anything. So we risk to leave operator without AWS credentials which may result into CI failures.
Example of failed operator's CredentialsRequest: link.