This topic explains how you can use Git with Supply Chain Choreographer.
The out of the box supply chains and delivery use Git in three ways:
- To fetch the developers source code, using the template.
- To store complete Kubernetes configuration, the write side of GitOps, using template 1, template 2, template 3 (experimental), and template 4 (experimental).
- To fetch stored Kubernetes configuration, the read side of GitOps, from either the same or a different Kubernetes cluster, using the template.
Tanzu Application Platform supports three Git providers:
- GitHub
- GitLab
- Azure DevOps
Git Authentication walks through the objects, such as secrets and service accounts, you can create on a cluster to allow successful supply chain Git operations. This includes the configuring a custom CA certificate.
GitOps versus RegistryOps discusses the two methods of storing built Kubernetes configuration, either in a Git repository or a container image registry, and walks through the parameters that must be provided for each.
Configuration for Azure DevOps: discusses configuration necessary for working with this Git provider.