-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathvalues-simple.yaml
208 lines (192 loc) · 6.16 KB
/
values-simple.yaml
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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
# This is currently configured as an 'all in one' deployment in one cluster.
clusterGroup:
name: simple
isHubCluster: true
namespaces:
- open-cluster-management
- vault
- golang-external-secrets
- openshift-sandboxed-containers-operator
- trustee-operator-system
- hello-openshift
- cert-manager-operator
- cert-manager
- letsencrypt
subscriptions:
# ACM is kept anticipating
acm:
name: advanced-cluster-management
namespace: open-cluster-management
channel: release-2.12
sandbox:
name: sandboxed-containers-operator
namespace: openshift-sandboxed-containers-operator
channel: stable
version: "1.8.1" # ask for latest
trustee:
name: trustee-operator
namespace: trustee-operator-system
source: redhat-operators
channel: stable
version: "0.2.0"
cert-manager:
name: openshift-cert-manager-operator
namespace: cert-manager-operator
channel: stable-v1
projects:
- hub
- vault
- trustee
- golang-external-secrets
- sandbox
- hello-openshift
# 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'
applications:
acm:
name: acm
namespace: open-cluster-management
project: hub
chart: acm
chartVersion: 0.1.*
vault:
name: vault
namespace: vault
project: vault
chart: hashicorp-vault
chartVersion: 0.1.*
secrets-operator:
name: golang-external-secrets
namespace: golang-external-secrets
project: golang-external-secrets
chart: golang-external-secrets
chartVersion: 0.1.*
trustee:
name: trustee
namespace: trustee-operator-system #upstream config
project: trustee
path: charts/hub/trustee
sandbox:
name: sandbox
namespace: openshift-sandboxed-containers-operator #upstream config
project: sandbox
path: charts/all/sandbox
letsencrypt:
name: letsencrypt
namespace: letsencrypt
project: hub
path: charts/all/letsencrypt
hello-openshift:
name: hello-openshift
namespace: hello-openshift
project: hello-openshift
path: charts/coco-supported/hello-openshift
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://hybrid-cloud-patterns.io/imperative-actions/#additional-job-customizations
jobs:
- name: install-deps
playbook: ansible/install-deps.yaml
verbosity: -vvv
timeout: 3600
- name: configure-azure-dns
playbook: ansible/configure-issuer.yaml
# this image has not been changes. TBD would make sense
#image: quay.io/hybridcloudpatterns/ansible-edge-gitops-ee:latest
verbosity: -vvv
timeout: 3600
# - name: hello-world
# # ansible playbook to be run
# playbook: common/ansible/playbooks/hello-world/hello-world.yaml
# # per playbook timeout in seconds
# timeout: 234
# # verbosity: "-v"
managedClusterGroups:
exampleRegion:
name: group-one
acmlabels:
- name: clusterGroup
value: group-one
helmOverrides:
- name: clusterGroup.isHubCluster
value: false
# Before enabling cluster provisioning, ensure AWS and/or Azure
# credentials and OCP pull secrets are defined in Vault.
# See values-secret.yaml.template
#
#clusterPools:
# exampleAWSPool:
# name: aws-ap
# openshiftVersion: 4.10.18
# baseDomain: blueprints.rhecoeng.com
# platform:
# aws:
# region: ap-southeast-2
# clusters:
# - One
#
# exampleAzurePool:
# name: azure-us
# openshiftVersion: 4.10.18
# baseDomain: blueprints.rhecoeng.com
# platform:
# azure:
# baseDomainResourceGroupName: dojo-dns-zones
# region: eastus
# clusters:
# - Two
# - Three
# 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: site.isHubCluster
# value: false
# clusterSelector:
# matchExpressions:
# - key: vendor
# operator: In
# values:
# - OpenShift