-
Notifications
You must be signed in to change notification settings - Fork 288
Expand file tree
/
Copy pathvalues-group-one.yaml
More file actions
110 lines (109 loc) · 3.74 KB
/
values-group-one.yaml
File metadata and controls
110 lines (109 loc) · 3.74 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
clusterGroup:
name: group-one
# Namespace is a dictionary for easier overriding (lists are supported as well)
namespaces:
config-demo:
hello-world:
external-secrets-operator:
operatorGroup: true
targetNamespaces: []
external-secrets:
# The gitops subscription on spokes gets managed by ACM
subscriptions:
eso:
name: openshift-external-secrets-operator
namespace: external-secrets-operator
channel: stable-v1
argoProjects:
- eso
- config-demo
- hello-world
applications:
openshift-external-secrets:
name: openshift-external-secrets
namespace: external-secrets
argoProject: eso
chart: openshift-external-secrets
chartVersion: 0.0.*
config-demo:
name: config-demo
namespace: config-demo
argoProject: config-demo
path: charts/all/config-demo
hello-world:
name: hello-world
namespace: hello-world
argoProject: hello-world
path: charts/all/hello-world
imperative:
# NOTE: We *must* use lists and not hashes. As hashes lose ordering once parsed by helm
# The default schedule is every 10 minutes: imperative.schedule
# Total timeout of all jobs is 1h: imperative.activeDeadlineSeconds
# imagePullPolicy is set to always: imperative.imagePullPolicy
# For additional overrides that apply to the jobs, please refer to
# https://validatedpatterns.io/patterns/multicloud-gitops/mcg-imperative-actions/
jobs:
- name: hello-world
# ansible playbook to be run
playbook: rhvp.cluster_utils.hello_world
# per playbook timeout in seconds
timeout: 234
# verbosity: "-v"
# Explicitly mention the cluster-state based overrides we plan to use for this pattern.
# We can use self-referential variables because the chart calls the tpl function with these variables defined
sharedValueFiles:
- '/overrides/values-{{ $.Values.global.clusterPlatform }}.yaml'
# To mirror the "Classic" magic include structure, the clusterGroup would need all of these:
# sharedValueFiles:
# - '/overrides/values-{{ $.Values.global.clusterPlatform }}.yaml'
# - '/overrides/values-{{ $.Values.global.clusterPlatform }}-{{ $.Values.global.clusterVersion }}.yaml'
# - '/overrides/values-{{ $.Values.global.clusterPlatform }}-{{ $.Values.clusterGroup.name }}.yaml'
# - '/overrides/values-{{ $.Values.global.clusterVersion }}-{{ $.Values.clusterGroup.name }}.yaml"
# To have apps in multiple flavors, use namespaces and use helm overrides as appropriate
#
# pipelines:
# name: pipelines
# namespace: production
# project: datacenter
# path: applications/pipeline
# repoURL: https://github.com/you/applications.git
# targetRevision: stable
# overrides:
# - name: myparam
# value: myparam
#
# pipelines_staging:
# - name: pipelines
# namespace: staging
# project: datacenter
# path: applications/pipeline
# repoURL: https://github.com/you/applications.git
# targetRevision: main
#
# Additional applications
# Be sure to include additional resources your apps will require
# +X machines
# +Y RAM
# +Z CPU
# vendor-app:
# name: vendor-app
# namespace: default
# project: vendor
# path: path/to/myapp
# repoURL: https://github.com/vendor/applications.git
# targetRevision: main
# managedSites:
# factory:
# name: factory
# # repoURL: https://github.com/dagger-refuse-cool/manuela-factory.git
# targetRevision: main
# path: applications/factory
# helmOverrides:
# - name: foo
# value: bar
# clusterSelector:
# matchExpressions:
# - key: vendor
# operator: In
# values:
# - OpenShift