|
| 1 | +clusterGroup: |
| 2 | + name: hub |
| 3 | + isHubCluster: true |
| 4 | + namespaces: |
| 5 | + - open-cluster-management |
| 6 | + - vault |
| 7 | + - golang-external-secrets |
| 8 | + - config-demo |
| 9 | + - hello-world |
| 10 | + subscriptions: {} |
| 11 | + projects: |
| 12 | + - hub |
| 13 | + - config-demo |
| 14 | + - hello-world |
| 15 | + # Explicitly mention the cluster-state based overrides we plan to use for this pattern. |
| 16 | + # We can use self-referential variables because the chart calls the tpl function with these variables defined |
| 17 | + sharedValueFiles: |
| 18 | + - '/overrides/values-{{ $.Values.global.clusterPlatform }}.yaml' |
| 19 | + # sharedValueFiles is a flexible mechanism that will add the listed valuefiles to every app defined in the |
| 20 | + # applications section. |
| 21 | + # |
| 22 | + # This kind of variable substitution will work with any of the variables the Validated Patterns operator knows |
| 23 | + # about and sets, so this is also possible, for example: |
| 24 | + # - '/overrides/values-{{ $.Values.global.hubClusterDomain }}.yaml' |
| 25 | + # - '/overrides/values-{{ $.Values.global.localClusterDomain }}.yaml' |
| 26 | + applications: |
| 27 | + vault: |
| 28 | + name: vault |
| 29 | + namespace: vault |
| 30 | + project: hub |
| 31 | + chart: hashicorp-vault |
| 32 | + chartVersion: 0.1.* |
| 33 | + golang-external-secrets: |
| 34 | + name: golang-external-secrets |
| 35 | + namespace: golang-external-secrets |
| 36 | + project: hub |
| 37 | + chart: golang-external-secrets |
| 38 | + chartVersion: 0.1.* |
| 39 | + config-demo: |
| 40 | + name: config-demo |
| 41 | + namespace: config-demo |
| 42 | + project: config-demo |
| 43 | + path: charts/all/config-demo |
| 44 | + hello-world: |
| 45 | + name: hello-world |
| 46 | + namespace: hello-world |
| 47 | + project: hello-world |
| 48 | + path: charts/all/hello-world |
| 49 | + imperative: |
| 50 | + # NOTE: We *must* use lists and not hashes. As hashes lose ordering once parsed by helm |
| 51 | + # The default schedule is every 10 minutes: imperative.schedule |
| 52 | + # Total timeout of all jobs is 1h: imperative.activeDeadlineSeconds |
| 53 | + # imagePullPolicy is set to always: imperative.imagePullPolicy |
| 54 | + # For additional overrides that apply to the jobs, please refer to |
| 55 | + # https://hybrid-cloud-patterns.io/imperative-actions/#additional-job-customizations |
| 56 | + jobs: |
| 57 | + - name: hello-world |
| 58 | + # ansible playbook to be run |
| 59 | + playbook: rhvp.cluster_utils.hello_world |
| 60 | + # per playbook timeout in seconds |
| 61 | + timeout: 234 |
| 62 | + # verbosity: "-v" |
0 commit comments