Goal Summary:

Ability to configure Google Artifact Registry Integration with Declarative Configuration  

Goals and expected user outcomes:

Customers would like to use declarative configuration when setting up integration with Google Artifact Registry. This is for both when customers are using Central integration only, as well as when they use delegated scanning. For the latter case, the Sensor's cluster needs to have Workload Identity Federation enabled with Google  see https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_security_for_kubernetes/4.6/html/integrating/integrate-using-short-lived-tokens#google-workload-identity-federation-gke_integrate-using-short-lived-tokens for more details. 

Acceptance Criteria:

 Declaratively configure GAR integration.

Success Criteria or KPIs measured:

A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.

<enter success criteria and/or KPIs here>

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

<your text here>

Considerations:

Curent Declarative Auth config is via ConfigMaps/Secrets. We may continue to do the same way for this Feature. CR support for this integration maybe a stretch goal not in scope.