Add gsm-config.yaml

[psalajova]

This PR introduces the initial gsm-config.yaml mapping file that will centralize how secrets from Google Secret Manager are bundled and consumed across our CI infrastructure.

What's included:

• gsm-config.yaml with cluster group definitions and a test bundle
• config_updater plugin entry to sync this file to all build farm clusters

This mapping file will be consumed by:

• ci-operator (for CSI-based secret mounting); see related PR
• ci-secret-bootstrap (for creating K8s Secrets from GSM); see related PR

gsm-config.yaml currently contains a test bundle to validate the config_updater integration. It will be extended with real secret bundles (user credentials, infrastructure secrets, etc.) as we progress with the migration.

[openshift-ci]

@psalajova: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Prucek, psalajova

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• core-services/ci-secret-bootstrap/OWNERS [Prucek,psalajova]
• core-services/prow/02_config/OWNERS [Prucek,psalajova]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[psalajova]

/pj-rehearse ack

[openshift-ci-robot]

@psalajova: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@psalajova: Updated the plugins configmap in namespace ci at cluster app.ci using the following files:

• key plugins.yaml using file core-services/prow/02_config/_plugins.yaml

Details

In response to this:

This PR introduces the initial gsm-config.yaml mapping file that will centralize how secrets from Google Secret Manager are bundled and consumed across our CI infrastructure.

What's included:

• gsm-config.yaml with cluster group definitions and a test bundle
• config_updater plugin entry to sync this file to all build farm clusters

This mapping file will be consumed by:

• ci-operator (for CSI-based secret mounting); see related PR
• ci-secret-bootstrap (for creating K8s Secrets from GSM); see related PR

gsm-config.yaml currently contains a test bundle to validate the config_updater integration. It will be extended with real secret bundles (user credentials, infrastructure secrets, etc.) as we progress with the migration.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.