How can a private Git repository be accessed by a BuildConfig during a build?

How can a private Git repository be accessed by a BuildConfig during a build?

• A. Use a public Git URL with no credentials.
• B. BuildConfig cannot access private repos.
• C. Store credentials directly in the BuildConfig YAML.
• D. Configure a secret with SSH keys or credentials and attach it to the BuildConfig as a source secret.

Answer: (D)

To access a private Git repository during a build, you provide credentials via a Secret and attach it to the BuildConfig as a source secret. Create a Secret that holds either an SSH private key (for SSH URLs) or basic authentication credentials (username/password or a token for HTTPS), and then reference that Secret in the BuildConfig’s source section as the sourceSecret. The build process will use those credentials to authenticate when cloning the private repository. This approach keeps credentials secure and is the supported method. Using a public URL with no credentials won’t work for private repos, and embedding credentials directly in the BuildConfig YAML is insecure and not recommended.

To access a private Git repository during a build, you provide credentials via a Secret and attach it to the BuildConfig as a source secret. Create a Secret that holds either an SSH private key (for SSH URLs) or basic authentication credentials (username/password or a token for HTTPS), and then reference that Secret in the BuildConfig’s source section as the sourceSecret. The build process will use those credentials to authenticate when cloning the private repository. This approach keeps credentials secure and is the supported method. Using a public URL with no credentials won’t work for private repos, and embedding credentials directly in the BuildConfig YAML is insecure and not recommended.