![]() The problem solvers who create careers with code. LinkedIn YouTube Twitter Facebook Products The feature will be available in Red Hat OpenShift GitOps 1.8. You can find more details about the feature in the documentation. The multiple sources feature in Argo CD 2.6 provides control and flexibility for managing resources spanning multiple repositories for a single application, making it easier to manage these resources. If the path field is not set, Argo CD will use the repository solely as a source of value files. ![]() If the path field is set in the source with a ref key set (in the last example, the source with key ref: values), Argo CD will attempt to generate resources from the git repository at that URL. So, you would want to avoid setting the Chart field for the source used for referencing value files. Taking the value files from an external Helm source is not currently supported. The $values variable can be specified only at the beginning of the value file path. The tag $values resolves to the root of the value-files repository referenced by the ref key in the list of sources. In the preceding example with multiple sources and external value files for the Helm source, the Prometheus chart uses the value file stored in the repository /org/value-files.git. Let's consider the following example to understand the use case: apiVersion: argoproj.io/v1alpha1 The multiple sources feature also allows users to specify value files from different Git repositories to a Helm chart stored in either a Helm repository or Git repository. With this configuration, Argo CD can manage both Helm charts as a single application, making it easier to deploy and maintain the components of your application. The combined resources from these two repositories will be deployed to the my-namespace namespace in the Kubernetes cluster. The first repository is synced to the root directory, while the second is synced to the charts/chart-2 directory. In this example, the application my-app is pulling resources from two Git repositories: Let's see an example of how the Argo CD application specification YAML file with multiple sources might look like: apiVersion: argoproj.io/v1alpha1 With the multiple sources feature, you can combine these two Helm charts into a single application in Argo CD. Suppose you have two Git repositories, each containing a Helm chart for a different application component. Examples of multiple sources applications This helps organizations manage the resources separately and share them across multiple applications. In all of these scenarios, the multiple sources feature lets you combine resources from different Git repositories to create an application entity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |