deploy: 89b1de8

blog/2021-12-31-medical-diagnosis/index.html

@@ -3445,7 +3445,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-03-23-acm-mustonlyhave/index.html

@@ -3515,7 +3515,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-03-30-multicloud-gitops/index.html

@@ -3439,7 +3439,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-06-30-ansible-edge-gitops/index.html

@@ -3438,7 +3438,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-07-15-push-vs-pull/index.html

@@ -3439,7 +3439,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-08-24-clustergroups/index.html

@@ -3438,7 +3438,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-09-02-route/index.html

@@ -3515,7 +3515,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-10-12-acm-provisioning/index.html

@@ -3525,7 +3525,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following:

blog/2022-11-20-argo-rollouts/index.html

@@ -3641,7 +3641,7 @@
 imperative: jobs: - name: hello-world playbook: rhvp.cluster_utils.hello_world After the above changes are implemented the pattern is not using any helm charts nor ansible bits from common.
 How to reference another external chart If you need to reference a helm chart that is not in the validated patterns chart helm repository, you can simply point to another one. For example:
 clusterGroup: applications: test: project: hub chart: nginx chartVersion: 13.2.12 repoURL: https://charts.bitnami.com/bitnami How to develop a chart directly from git It is possible to point the framework directly to a git repository pointing to a helm chart. This is especially useful for developing a chart. There are two cases to distinguish here.
-The clustergroup chart. This one gets instantiated by the operator, so we need to change things in the Pattern CR. Edit the pattern with oc edit -n openshift-operators patterns and make sure the Pattern CR has the following:
+The clustergroup chart. Tweak values-global.yaml as follows:
 spec: clusterGroupName: hub multiSourceConfig: enabled: true clusterGroupGitRepoUrl: https://github.com/myorg/clustergroup-chart clusterGroupChartGitRevision: dev-branch For all the other charts we just need to add repoURL, path and the chartVersion fields:
 clusterGroup: applications: acm: name: acm namespace: open-cluster-management project: hub path: "." chartVersion: dev-branch repoURL: https://github.com/myorg/acm-chart `,url:"https://validatedpatterns.io/blog/2024-09-26-slimming-of-common/",breadcrumb:"/blog/2024-09-26-slimming-of-common/"},"https://validatedpatterns.io/blog/2024-09-13-using-hypershift/":{title:"Using HyperShift",tags:[],content:`Getting Started Hosted Control Planes (aka: HyperShift) is project that enables rapid provisioning and deprovisioning of OpenShift clusters. Use this guide to create and delete your hostedclusters and to interrogate the hostingcluster for compute resource information. Upstream documentation can be found HyperShift Upstream Project Docs
 PreReqs and Assumptions Deploying HyperShift clusters requires the following: