diff --git a/blog/2021-12-31-medical-diagnosis/index.html b/blog/2021-12-31-medical-diagnosis/index.html index c9a602e95..0ce485002 100644 --- a/blog/2021-12-31-medical-diagnosis/index.html +++ b/blog/2021-12-31-medical-diagnosis/index.html @@ -157,7 +157,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -812,7 +811,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1455,7 +1456,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1551,7 +1552,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1560,8 +1561,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-03-23-acm-mustonlyhave/index.html b/blog/2022-03-23-acm-mustonlyhave/index.html index d780fa78d..a7c02994b 100644 --- a/blog/2022-03-23-acm-mustonlyhave/index.html +++ b/blog/2022-03-23-acm-mustonlyhave/index.html @@ -227,7 +227,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -882,7 +881,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1525,7 +1526,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1621,7 +1622,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1630,8 +1631,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-03-30-multicloud-gitops/index.html b/blog/2022-03-30-multicloud-gitops/index.html index 63b021c56..b18c89ebc 100644 --- a/blog/2022-03-30-multicloud-gitops/index.html +++ b/blog/2022-03-30-multicloud-gitops/index.html @@ -151,7 +151,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -806,7 +805,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1449,7 +1450,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1545,7 +1546,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1554,8 +1555,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-06-30-ansible-edge-gitops/index.html b/blog/2022-06-30-ansible-edge-gitops/index.html index 491b37c0f..469b6c154 100644 --- a/blog/2022-06-30-ansible-edge-gitops/index.html +++ b/blog/2022-06-30-ansible-edge-gitops/index.html @@ -150,7 +150,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -805,7 +804,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1448,7 +1449,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1544,7 +1545,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1553,8 +1554,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-07-15-push-vs-pull/index.html b/blog/2022-07-15-push-vs-pull/index.html index 1995ad08e..e62e96ba1 100644 --- a/blog/2022-07-15-push-vs-pull/index.html +++ b/blog/2022-07-15-push-vs-pull/index.html @@ -151,7 +151,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -806,7 +805,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1449,7 +1450,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1545,7 +1546,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1554,8 +1555,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-08-24-clustergroups/index.html b/blog/2022-08-24-clustergroups/index.html index 285cbc868..eb0494d68 100644 --- a/blog/2022-08-24-clustergroups/index.html +++ b/blog/2022-08-24-clustergroups/index.html @@ -150,7 +150,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -805,7 +804,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1448,7 +1449,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1544,7 +1545,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1553,8 +1554,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-09-02-route/index.html b/blog/2022-09-02-route/index.html index e0009a9a7..db58527cb 100644 --- a/blog/2022-09-02-route/index.html +++ b/blog/2022-09-02-route/index.html @@ -227,7 +227,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -882,7 +881,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1525,7 +1526,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1621,7 +1622,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1630,8 +1631,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-10-12-acm-provisioning/index.html b/blog/2022-10-12-acm-provisioning/index.html index 8d40fb451..a235aeced 100644 --- a/blog/2022-10-12-acm-provisioning/index.html +++ b/blog/2022-10-12-acm-provisioning/index.html @@ -237,7 +237,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -892,7 +891,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1535,7 +1536,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1631,7 +1632,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1640,8 +1641,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-11-20-argo-rollouts/index.html b/blog/2022-11-20-argo-rollouts/index.html index 85c531d8b..2852e281e 100644 --- a/blog/2022-11-20-argo-rollouts/index.html +++ b/blog/2022-11-20-argo-rollouts/index.html @@ -353,7 +353,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -1008,7 +1007,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1651,7 +1652,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1747,7 +1748,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1756,8 +1757,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/2022-12-01-multicluster-devsecops/index.html b/blog/2022-12-01-multicluster-devsecops/index.html index 3a8c33d59..74aca0d53 100644 --- a/blog/2022-12-01-multicluster-devsecops/index.html +++ b/blog/2022-12-01-multicluster-devsecops/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/index.html b/blog/index.html index 69a2ec038..46b7e1384 100644 --- a/blog/index.html +++ b/blog/index.html @@ -163,7 +163,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -818,7 +817,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1461,7 +1462,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1557,7 +1558,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1566,8 +1567,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog/page/2/index.html b/blog/page/2/index.html index b63b9130d..80ab313a5 100644 --- a/blog/page/2/index.html +++ b/blog/page/2/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/acm/index.html b/blog_tags/acm/index.html index 3f0211165..ae392e5d1 100644 --- a/blog_tags/acm/index.html +++ b/blog_tags/acm/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/acs/index.html b/blog_tags/acs/index.html index 09f38d809..91a9b0d81 100644 --- a/blog_tags/acs/index.html +++ b/blog_tags/acs/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/ansible-edge-gitops/index.html b/blog_tags/ansible-edge-gitops/index.html index df5dea9e0..6b20344c0 100644 --- a/blog_tags/ansible-edge-gitops/index.html +++ b/blog_tags/ansible-edge-gitops/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/devops/index.html b/blog_tags/devops/index.html index 050a8eb07..1b7f6233d 100644 --- a/blog_tags/devops/index.html +++ b/blog_tags/devops/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/devsecops/index.html b/blog_tags/devsecops/index.html index 87f2a66f2..64a14f6fc 100644 --- a/blog_tags/devsecops/index.html +++ b/blog_tags/devsecops/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/gitops/index.html b/blog_tags/gitops/index.html index a32eab264..517f11a91 100644 --- a/blog_tags/gitops/index.html +++ b/blog_tags/gitops/index.html @@ -155,7 +155,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -810,7 +809,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1453,7 +1454,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1549,7 +1550,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1558,8 +1559,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/index.html b/blog_tags/index.html index 52b6c132a..13d0cedf5 100644 --- a/blog_tags/index.html +++ b/blog_tags/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/medical-diagnosis/index.html b/blog_tags/medical-diagnosis/index.html index 487cd3c02..15aa9a2f7 100644 --- a/blog_tags/medical-diagnosis/index.html +++ b/blog_tags/medical-diagnosis/index.html @@ -151,7 +151,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -806,7 +805,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1449,7 +1450,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1545,7 +1546,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1554,8 +1555,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/multi-cloud-gitops/index.html b/blog_tags/multi-cloud-gitops/index.html index a2895cc13..95b29d2f5 100644 --- a/blog_tags/multi-cloud-gitops/index.html +++ b/blog_tags/multi-cloud-gitops/index.html @@ -151,7 +151,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -806,7 +805,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1449,7 +1450,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1545,7 +1546,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1554,8 +1555,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/openshift-platform-plus/index.html b/blog_tags/openshift-platform-plus/index.html index 9c0fd8b0f..0bf9a401a 100644 --- a/blog_tags/openshift-platform-plus/index.html +++ b/blog_tags/openshift-platform-plus/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/openshift/index.html b/blog_tags/openshift/index.html index 588456203..dba3aaf93 100644 --- a/blog_tags/openshift/index.html +++ b/blog_tags/openshift/index.html @@ -151,7 +151,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -806,7 +805,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1449,7 +1450,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1545,7 +1546,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1554,8 +1555,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/page/2/index.html b/blog_tags/page/2/index.html index 489dc4a1b..d85030d1d 100644 --- a/blog_tags/page/2/index.html +++ b/blog_tags/page/2/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/page/3/index.html b/blog_tags/page/3/index.html index ac614075f..43075033c 100644 --- a/blog_tags/page/3/index.html +++ b/blog_tags/page/3/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/patterns/index.html b/blog_tags/patterns/index.html index dd8a22f70..da9bd3fc4 100644 --- a/blog_tags/patterns/index.html +++ b/blog_tags/patterns/index.html @@ -163,7 +163,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -818,7 +817,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1461,7 +1462,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1557,7 +1558,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1566,8 +1567,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/pipelines/index.html b/blog_tags/pipelines/index.html index 6648b3380..847f1c693 100644 --- a/blog_tags/pipelines/index.html +++ b/blog_tags/pipelines/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/provisioning/index.html b/blog_tags/provisioning/index.html index 49b674121..c39951300 100644 --- a/blog_tags/provisioning/index.html +++ b/blog_tags/provisioning/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/quay/index.html b/blog_tags/quay/index.html index f237d25e2..8834c11f5 100644 --- a/blog_tags/quay/index.html +++ b/blog_tags/quay/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/route/index.html b/blog_tags/route/index.html index 72bcd4168..3e3bd810a 100644 --- a/blog_tags/route/index.html +++ b/blog_tags/route/index.html @@ -151,7 +151,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -806,7 +805,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1449,7 +1450,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1545,7 +1546,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1554,8 +1555,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/security/index.html b/blog_tags/security/index.html index 87d7fc782..2d360e6f5 100644 --- a/blog_tags/security/index.html +++ b/blog_tags/security/index.html @@ -156,7 +156,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -811,7 +810,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1454,7 +1455,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1550,7 +1551,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1559,8 +1560,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/validated-pattern/index.html b/blog_tags/validated-pattern/index.html index af3f06c50..fd193ed13 100644 --- a/blog_tags/validated-pattern/index.html +++ b/blog_tags/validated-pattern/index.html @@ -155,7 +155,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -810,7 +809,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1453,7 +1454,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1549,7 +1550,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1558,8 +1559,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/blog_tags/xray/index.html b/blog_tags/xray/index.html index b816416cd..d454548f1 100644 --- a/blog_tags/xray/index.html +++ b/blog_tags/xray/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/ci/index.html b/ci/index.html index de81a4f17..8785de2c0 100644 --- a/ci/index.html +++ b/ci/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/ci/internal/index.html b/ci/internal/index.html index 1f92fdc4f..1d08d99b9 100644 --- a/ci/internal/index.html +++ b/ci/internal/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/contribute/background-on-pattern-development/index.html b/contribute/background-on-pattern-development/index.html index 67bf1db56..f4c9ce92b 100644 --- a/contribute/background-on-pattern-development/index.html +++ b/contribute/background-on-pattern-development/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/contribute/contribute-to-docs/index.html b/contribute/contribute-to-docs/index.html index f9f12d896..eaad955db 100644 --- a/contribute/contribute-to-docs/index.html +++ b/contribute/contribute-to-docs/index.html @@ -207,7 +207,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -862,7 +861,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1505,7 +1506,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1601,7 +1602,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1610,8 +1611,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/contribute/creating-a-pattern/index.html b/contribute/creating-a-pattern/index.html index 4dab89464..8bde300f7 100644 --- a/contribute/creating-a-pattern/index.html +++ b/contribute/creating-a-pattern/index.html @@ -236,7 +236,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -891,7 +890,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1534,7 +1535,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1630,7 +1631,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1639,8 +1640,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/contribute/extending-a-pattern/index.html b/contribute/extending-a-pattern/index.html index 655d71def..6aa33f7e0 100644 --- a/contribute/extending-a-pattern/index.html +++ b/contribute/extending-a-pattern/index.html @@ -253,7 +253,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -908,7 +907,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1551,7 +1552,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1647,7 +1648,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1656,8 +1657,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/contribute/index.html b/contribute/index.html index 4c3e4d537..c6298126f 100644 --- a/contribute/index.html +++ b/contribute/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/contribute/structure/index.html b/contribute/structure/index.html index 7f0ecf220..880627524 100644 --- a/contribute/structure/index.html +++ b/contribute/structure/index.html @@ -237,7 +237,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -892,7 +891,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1535,7 +1536,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1631,7 +1632,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1640,8 +1641,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/index.html b/index.html index 4bddc4478..22d2a5b8f 100644 --- a/index.html +++ b/index.html @@ -158,7 +158,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -813,7 +812,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1456,7 +1457,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1552,7 +1553,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1561,8 +1562,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/index.xml b/index.xml index 321d73e10..b7a129175 100644 --- a/index.xml +++ b/index.xml @@ -1,7 +1,7 @@ Validated Patternshttps://validatedpatterns.io/Recent content on Validated PatternsHugo -- gohugo.ioen-usWed, 15 Nov 2023 00:00:00 +0000About Validated Patternshttps://validatedpatterns.io/learn/about/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/about/Validated Patterns and upstream Community Patterns are a natural progression from reference architectures with additional value. Here is a brief video to explain what patterns are all about:Contributor's guidehttps://validatedpatterns.io/contribute/contribute-to-docs/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/contribute/contribute-to-docs/Contribute to Validated Patterns documentation Different ways to contribute There are a few different ways you can contribute to Validated Patterns documentation:Getting startedhttps://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/Deploying the Emerging Disease Detection pattern Prerequisites An OpenShift cluster (Go to the OpenShift console). Cluster must have a dynamic StorageClass to provision PersistentVolumes.Getting startedhttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.Getting Startedhttps://validatedpatterns.io/patterns/ansible-edge-gitops/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/getting-started/Deploying the Ansible Edge GitOps Pattern General Prerequisites An OpenShift cluster ( Go to the OpenShift console). See also sizing your cluster.Getting Startedhttps://validatedpatterns.io/patterns/devsecops/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/getting-started/Deploying the Multicluster DevSecOps Pattern Prerequisites An OpenShift cluster (Go to the OpenShift console). Cluster must have a dynamic StorageClass to provision PersistentVolumes.Getting Startedhttps://validatedpatterns.io/patterns/industrial-edge/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/getting-started/Deploying the Industrial Edge Pattern Prerequisites An OpenShift cluster (Go to the OpenShift console). Cluster must have a dynamic StorageClass to provision PersistentVolumes.Getting Startedhttps://validatedpatterns.io/patterns/medical-diagnosis/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/medical-diagnosis/getting-started/Deploying the Medical Diagnosis pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.Getting Startedhttps://validatedpatterns.io/patterns/multicloud-gitops-portworx/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops-portworx/getting-started/Deploying the Multicloud GitOps pattern Prerequisite An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.Getting Startedhttps://validatedpatterns.io/patterns/retail/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/getting-started/Deploying the Retail Pattern Prerequisites An OpenShift cluster (Go to the OpenShift console). Cluster must have a dynamic StorageClass to provision PersistentVolumes.Background on pattern developmenthttps://validatedpatterns.io/contribute/background-on-pattern-development/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/contribute/background-on-pattern-development/Introduction This section provides details on how to create a new pattern using the validated patterns framework. Creating a new pattern might start from scratch or it may start from an existing deployment that would benefit from a repeatable framework based on GitOps.Cluster Sizinghttps://validatedpatterns.io/patterns/medical-diagnosis/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/medical-diagnosis/cluster-sizing/About OpenShift cluster sizing for the Medical Diagnosis pattern To understand cluster sizing requirements for the Medical Diagnosis pattern, consider the following components that the Medical Diagnosis pattern deploys on the datacenter or the hub OpenShift cluster:Factory Siteshttps://validatedpatterns.io/patterns/industrial-edge/factory/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/factory/Having a factory (edge) cluster join the datacenter (hub) Allow ACM to deploy the factory application to a subset of clusters By default the factory applications are deployed on all clusters that ACM knows about.Installation Detailshttps://validatedpatterns.io/patterns/ansible-edge-gitops/installation-details/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/installation-details/Installation Details Installation Steps These are the steps run by make install and what each one does: -operator-deploy The operator-deploy task installs the Validated Patterns Operator, which in turn creates a subscription for the OpenShift GitOps operator and installs both the cluster and hub instances of it.Managed cluster siteshttps://validatedpatterns.io/patterns/multicloud-gitops-portworx/managed-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops-portworx/managed-cluster/Attach a managed cluster (edge) to the management hub Understanding Red Hat Advanced Cluster Management requirements Allow Red Hat Advanced Cluster Management (RHACM) to deploy the managed cluster application to a subset of clusters.Managed cluster siteshttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-managed-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-managed-cluster/Attach a managed cluster (edge) to the management hub Understanding Red Hat Advanced Cluster Management requirements By default, Red Hat Advanced Cluster Management (RHACM) manages the clusterGroup applications that are deployed on all clusters.Patterns quick starthttps://validatedpatterns.io/learn/quickstart/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/quickstart/Patterns quick start Each pattern can be deployed using the command line. The only requirement is to have git and podman installed.Secured Development Clusterhttps://validatedpatterns.io/patterns/devsecops/devel-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/devel-cluster/Having a development cluster (devel) join the hub Introduction Development clusters are responsible for building applications and delivering the applications to a secured registry.Store Siteshttps://validatedpatterns.io/patterns/retail/store/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/store/Having a store (edge) cluster join the datacenter (hub) Allow ACM to deploy the store application to a subset of clusters A store (“ATLANTA”) is installed on the hub cluster by default.Importing a clusterhttps://validatedpatterns.io/learn/importing-a-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/importing-a-cluster/Importing a managed cluster Many validated patterns require importing a cluster into a managed group. These groups have specific application sets that will be deployed and managed.Validated pattern structurehttps://validatedpatterns.io/contribute/structure/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/contribute/structure/Framework fundamentals The validated patterns framework uses OpenShift GitOps (ArgoCD) as the primary driver for deploying patterns and keeping them up to date.Application Demoshttps://validatedpatterns.io/patterns/industrial-edge/application/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/application/Demonstrating Industrial Edge example applications Background Up until now the Industrial Edge 2.0 validated patterns has focused primarily on successfully deploying the architectural pattern.Application Demoshttps://validatedpatterns.io/patterns/retail/application/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/application/Demonstrating Retail example applications Background Up until now the Retail validated pattern has focused primarily on successfully deploying the architectural pattern.Cluster sizinghttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements.Cluster Sizinghttps://validatedpatterns.io/patterns/ansible-edge-gitops/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/cluster-sizing/OpenShift Cluster Sizing for the Ansible Edge GitOps Pattern Tested Platforms The Ansible Edge GitOps pattern has been tested on AWS:Cluster Sizinghttps://validatedpatterns.io/patterns/multicloud-gitops-portworx/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops-portworx/cluster-sizing/About OpenShift cluster sizing for the Multicloud GitOps Pattern Support matrix for Multicloud GitOps pattern The Multicloud GitOps pattern has been tested in the following Certified Cloud Providers.Componentshttps://validatedpatterns.io/patterns/retail/components/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/components/Component Details The Quarkus Coffeeshop Store Chart This chart is responsible for deploying the applications, services and routes for the Quarkus Coffeeshop demo.Extending an existing patternhttps://validatedpatterns.io/contribute/extending-a-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/contribute/extending-a-pattern/Introduction to extending a pattern using a fork Extending an existing pattern usually means adding a new product and/or configuration to the existing pattern.Infrastructurehttps://validatedpatterns.io/learn/infrastructure/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/infrastructure/Background Each validated pattern has infrastructure requirements. The majority of the validated patterns will run Red Hat OpenShift while some parts will run directly on Red Hat Enterprise Linux or (RHEL), more likely, a version of RHEL called RHEL for Edge.Secured Production Clustershttps://validatedpatterns.io/patterns/devsecops/production-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/production-cluster/Having a production cluster join the hub Introduction Production clusters need to be secured and so one part of the deployment is to install the Advanced Cluster Security operator with a secured configuration.OpenShift General Sizinghttps://validatedpatterns.io/learn/ocp-cluster-general-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/ocp-cluster-general-sizing/OpenShift General Sizing Recommended node host practices The OpenShift Container Platform node configuration file contains important options. For example, two parameters control the maximum number of pods that can be scheduled to a node: podsPerCore and maxPods.RHEL for Edge General Sizinghttps://validatedpatterns.io/learn/rhel-for-edge-general-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/rhel-for-edge-general-sizing/RHEL for Edge General Sizing Recommended node host practices TBDAnsible Automation Platformhttps://validatedpatterns.io/patterns/ansible-edge-gitops/ansible-automation-platform/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/ansible-automation-platform/Ansible Automation Platform How it’s installed See the installation details here. +operator-deploy The operator-deploy task installs the Validated Patterns Operator, which in turn creates a subscription for the OpenShift GitOps operator and installs both the cluster and hub instances of it.Managed cluster siteshttps://validatedpatterns.io/patterns/multicloud-gitops-portworx/managed-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops-portworx/managed-cluster/Attach a managed cluster (edge) to the management hub Understanding Red Hat Advanced Cluster Management requirements Allow Red Hat Advanced Cluster Management (RHACM) to deploy the managed cluster application to a subset of clusters.Managed cluster siteshttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-managed-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-managed-cluster/Attach a managed cluster (edge) to the management hub Understanding Red Hat Advanced Cluster Management requirements By default, Red Hat Advanced Cluster Management (RHACM) manages the clusterGroup applications that are deployed on all clusters.Patterns quick starthttps://validatedpatterns.io/learn/quickstart/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/quickstart/Patterns quick start Each pattern can be deployed using the command line. The only requirement is to have git and podman installed.Secured Development Clusterhttps://validatedpatterns.io/patterns/devsecops/devel-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/devel-cluster/Having a development cluster (devel) join the hub Introduction Development clusters are responsible for building applications and delivering the applications to a secured registry.Store Siteshttps://validatedpatterns.io/patterns/retail/store/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/store/Having a store (edge) cluster join the datacenter (hub) Allow ACM to deploy the store application to a subset of clusters A store (“ATLANTA”) is installed on the hub cluster by default.Importing a clusterhttps://validatedpatterns.io/learn/importing-a-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/importing-a-cluster/Importing a managed cluster Many validated patterns require importing a cluster into a managed group. These groups have specific application sets that will be deployed and managed.Validated pattern structurehttps://validatedpatterns.io/contribute/structure/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/contribute/structure/Framework fundamentals The validated patterns framework uses OpenShift GitOps (ArgoCD) as the primary driver for deploying patterns and keeping them up to date.Application Demoshttps://validatedpatterns.io/patterns/industrial-edge/application/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/application/Demonstrating Industrial Edge example applications Background Up until now the Industrial Edge 2.0 validated patterns has focused primarily on successfully deploying the architectural pattern.Application Demoshttps://validatedpatterns.io/patterns/retail/application/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/application/Demonstrating Retail example applications Background Up until now the Retail validated pattern has focused primarily on successfully deploying the architectural pattern.Cluster sizinghttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example:Cluster Sizinghttps://validatedpatterns.io/patterns/ansible-edge-gitops/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/cluster-sizing/OpenShift Cluster Sizing for the Ansible Edge GitOps Pattern Tested Platforms The Ansible Edge GitOps pattern has been tested on AWS:Cluster Sizinghttps://validatedpatterns.io/patterns/multicloud-gitops-portworx/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops-portworx/cluster-sizing/About OpenShift cluster sizing for the Multicloud GitOps Pattern Support matrix for Multicloud GitOps pattern The Multicloud GitOps pattern has been tested in the following Certified Cloud Providers.Componentshttps://validatedpatterns.io/patterns/retail/components/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/components/Component Details The Quarkus Coffeeshop Store Chart This chart is responsible for deploying the applications, services and routes for the Quarkus Coffeeshop demo.Extending an existing patternhttps://validatedpatterns.io/contribute/extending-a-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/contribute/extending-a-pattern/Introduction to extending a pattern using a fork Extending an existing pattern usually means adding a new product and/or configuration to the existing pattern.Infrastructurehttps://validatedpatterns.io/learn/infrastructure/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/infrastructure/Background Each validated pattern has infrastructure requirements. The majority of the validated patterns will run Red Hat OpenShift while some parts will run directly on Red Hat Enterprise Linux or (RHEL), more likely, a version of RHEL called RHEL for Edge.Secured Production Clustershttps://validatedpatterns.io/patterns/devsecops/production-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/production-cluster/Having a production cluster join the hub Introduction Production clusters need to be secured and so one part of the deployment is to install the Advanced Cluster Security operator with a secured configuration.OpenShift General Sizinghttps://validatedpatterns.io/learn/ocp-cluster-general-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/ocp-cluster-general-sizing/OpenShift General Sizing Recommended node host practices The OpenShift Container Platform node configuration file contains important options. For example, two parameters control the maximum number of pods that can be scheduled to a node: podsPerCore and maxPods.RHEL for Edge General Sizinghttps://validatedpatterns.io/learn/rhel-for-edge-general-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/rhel-for-edge-general-sizing/RHEL for Edge General Sizing Recommended node host practices TBDAnsible Automation Platformhttps://validatedpatterns.io/patterns/ansible-edge-gitops/ansible-automation-platform/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/ansible-automation-platform/Ansible Automation Platform How it’s installed See the installation details here. How to Log In The default login user is admin and the password is generated randomly at install time; you will need the password to login in to the AAP interface.Creating a patternhttps://validatedpatterns.io/contribute/creating-a-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/contribute/creating-a-pattern/The validated patterns community has relied on existing architectures that have been successfully deployed in an enterprise. The architecture itself is a best practice in assembling technologies and projects to provide a working solution.Imperative actionshttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-imperative-actions/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-imperative-actions/Using kubernetes cronjobs to apply imperative actions There is currently no way within Argo CD to apply an imperative action against a cluster.Multicluster DevSecOps Demohttps://validatedpatterns.io/patterns/devsecops/secure-supply-chain-demo/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/secure-supply-chain-demo/Demonstrating Multicluster DevSecOps Background Up until now the Multicluster DevSecOps validated pattern has focused primarily on successfully deploying the architectural pattern components on the three different clusters.Troubleshootinghttps://validatedpatterns.io/patterns/industrial-edge/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/troubleshooting/Troubleshooting Our Issue Tracker Installation-phase Failures The framework for deploying the applications and their operators has been made easy for the user by using OpenShift GitOps for continuous deployment (Argo CD).Troubleshootinghttps://validatedpatterns.io/patterns/medical-diagnosis/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/medical-diagnosis/troubleshooting/Understanding the Makefile The Makefile is the entrypoint for the pattern. We use the Makefile to bootstrap the pattern to the cluster.Troubleshootinghttps://validatedpatterns.io/patterns/retail/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/troubleshooting/Troubleshooting Our Issue TrackerUsing the Validated Patterns Operatorhttps://validatedpatterns.io/learn/using-validated-pattern-operator/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/using-validated-pattern-operator/About the Validated Patterns Operator You can use the Validated Patterns Operator to install and manage Validated Patterns. Use the Red Hat Hybrid Cloud Console to install the Validated Patterns Operator.Workflowhttps://validatedpatterns.io/learn/workflow/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/workflow/Workflow These patterns are designed to be composed of multiple components, and for those components to be used in gitops workflows by consumers and contributors.Implementation Requirementshttps://validatedpatterns.io/learn/implementation/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/implementation/Technical Requirements Additional requirements specific to the implementation for all Community, and Validated patterns Must Patterns MUST include one or more Git repositories, in a publicly accessible location, containing configuration elements that can be consumed by the OpenShift GitOps operator (ArgoCD) without supplying custom ArgoCD images.Community Patternshttps://validatedpatterns.io/learn/community/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/community/Community Pattern Requirements tl;dr What are they: Best practice implementations conforming to the Validated Patterns implementation practices -Purpose: Codify best practices and promote collaboration between different groups inside, and external to, Red HatValidated Patternshttps://validatedpatterns.io/learn/validated/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/validated/Validated Pattern Requirements tl;dr What are they: Technical foundations, backed by CI, that have succeeded in the market and Red Hat expects to be repeatable across customers and segments.Cluster Sizinghttps://validatedpatterns.io/patterns/devsecops/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/cluster-sizing/OpenShift Cluster Sizing for the Multicluster DevSecOps Pattern Tested Platforms The Multicluster DevSecOps pattern has been tested in the following Certified Cloud Providers.Cluster Sizinghttps://validatedpatterns.io/patterns/industrial-edge/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/cluster-sizing/OpenShift Cluster Sizing for the Industrial Edge Pattern Tested Platforms The Industrial-Edge pattern has been tested in the following Certified Cloud Providers.Cluster Sizinghttps://validatedpatterns.io/patterns/retail/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/cluster-sizing/OpenShift Cluster Sizing for the Retail Pattern Tested Platforms The retail pattern has been tested in the following Certified Cloud Providers.Ideas for customizationhttps://validatedpatterns.io/patterns/medical-diagnosis/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/medical-diagnosis/ideas-for-customization/About customizing the pattern Medical Diagnosis pattern One of the major goals of the Validated Patterns development process is to create modular and customizable demos.OpenShift Virtualizationhttps://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/OpenShift Virtualization Understanding the Edge GitOps VMs Helm Chart The heart of the Edge GitOps VMs helm chart is a template file that was designed with a fair amount of flexibility in mind.Ideas for customizationhttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/ansible-edge-gitops/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/ideas-for-customization/Ideas for Customization Why change it? One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/devsecops/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/ideas-for-customization/Ideas for Customization More desirable tools in the development pipeline One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/industrial-edge/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/ideas-for-customization/Ideas for Customization Why change it? One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/multicloud-gitops-portworx/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops-portworx/ideas-for-customization/Ideas for customization Why change it? One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/retail/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/ideas-for-customization/Ideas for CustomizationSecretshttps://validatedpatterns.io/learn/secrets/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/secrets/Infrastructure Background Enterprise applications require security, especially in multi-cluster and multi-site environments. Applications require trust and use certificates and other secrets in order to establish and maintain trust.HashiCorp Vaulthttps://validatedpatterns.io/learn/vault/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/vault/Deploying HashiCorp Vault in a validated pattern Prerequisites You have deployed/installed a validated pattern using the instructions provided for that pattern.Troubleshootinghttps://validatedpatterns.io/patterns/ansible-edge-gitops/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/troubleshooting/Troubleshooting Our Issue Tracker Please file an issue if you see a problem!FAQhttps://validatedpatterns.io/learn/faq/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/faq/FAQ What is a Validated Pattern? Validated Patterns are collections of applications (in the ArgoCD sense) that demonstrate aspects of hub/edge computing that seem interesting and useful.Multicluster DevSecOpshttps://validatedpatterns.io/blog/2022-12-01-multicluster-devsecops/Thu, 01 Dec 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-12-01-multicluster-devsecops/A validated pattern that uses OpenShift Platform Plus and OpenShift Pipelines to securely build, scan, and deliver applicationsProgressive Delivery with Argo Rolloutshttps://validatedpatterns.io/blog/2022-11-20-argo-rollouts/Thu, 03 Nov 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-11-20-argo-rollouts/Argo Rollouts lets us simplify delivery strategies like blue/green and canary deployments.Multi-cluster GitOps with Provisioninghttps://validatedpatterns.io/blog/2022-10-12-acm-provisioning/Wed, 12 Oct 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-10-12-acm-provisioning/With validated patterns, you can easily create and configure complex cluster topologiesUsing subdomain in your OpenShift route definitionshttps://validatedpatterns.io/blog/2022-09-02-route/Fri, 02 Sep 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-09-02-route/When to use subdomain when defining a Route in OpenShiftUsing clusterGroups in the Validated Patterns Frameworkhttps://validatedpatterns.io/blog/2022-08-24-clustergroups/Wed, 24 Aug 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-08-24-clustergroups/Defining what we mean by clusterGroups in the Validated Pattern Framework (and how to use them)Push or Pull?https://validatedpatterns.io/blog/2022-07-15-push-vs-pull/Fri, 15 Jul 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-07-15-push-vs-pull/Considerations on Push and Pull in change management systemsAnsible Edge GitOpshttps://validatedpatterns.io/blog/2022-06-30-ansible-edge-gitops/Thu, 30 Jun 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-06-30-ansible-edge-gitops/A validated pattern that introduces Ansible and Virtualization to the frameworkMulti-Cloud GitOpshttps://validatedpatterns.io/blog/2022-03-30-multicloud-gitops/Wed, 30 Mar 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-03-30-multicloud-gitops/A validated pattern for multi-cluster and/or multi-cloud gitopsTo musthave or to mustonlyhavehttps://validatedpatterns.io/blog/2022-03-23-acm-mustonlyhave/Wed, 23 Mar 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-03-23-acm-mustonlyhave/ACM has multiple enforcement strategies, be careful which one you useMedical Diagnosishttps://validatedpatterns.io/blog/2021-12-31-medical-diagnosis/Fri, 31 Dec 2021 00:00:00 +0000https://validatedpatterns.io/blog/2021-12-31-medical-diagnosis/A validated pattern for the medical fieldInternal CI Statushttps://validatedpatterns.io/ci/internal/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/ci/internal/These are the latest results of the Validated Patterns CI test runs. The links on this page are internal Red Hat links and require a valid Red Hat login to access them. \ No newline at end of file +Purpose: Codify best practices and promote collaboration between different groups inside, and external to, Red HatValidated Patternshttps://validatedpatterns.io/learn/validated/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/validated/Validated Pattern Requirements tl;dr What are they: Technical foundations, backed by CI, that have succeeded in the market and Red Hat expects to be repeatable across customers and segments.Cluster Sizinghttps://validatedpatterns.io/patterns/devsecops/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/cluster-sizing/OpenShift Cluster Sizing for the Multicluster DevSecOps Pattern Tested Platforms The Multicluster DevSecOps pattern has been tested in the following Certified Cloud Providers.Cluster Sizinghttps://validatedpatterns.io/patterns/industrial-edge/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/cluster-sizing/OpenShift Cluster Sizing for the Industrial Edge Pattern Tested Platforms The Industrial-Edge pattern has been tested in the following Certified Cloud Providers.Cluster Sizinghttps://validatedpatterns.io/patterns/retail/cluster-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/cluster-sizing/OpenShift Cluster Sizing for the Retail Pattern Tested Platforms The retail pattern has been tested in the following Certified Cloud Providers.Ideas for customizationhttps://validatedpatterns.io/patterns/medical-diagnosis/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/medical-diagnosis/ideas-for-customization/About customizing the pattern Medical Diagnosis pattern One of the major goals of the Validated Patterns development process is to create modular and customizable demos.OpenShift Virtualizationhttps://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/OpenShift Virtualization Understanding the Edge GitOps VMs Helm Chart The heart of the Edge GitOps VMs helm chart is a template file that was designed with a fair amount of flexibility in mind.Ideas for customizationhttps://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/ansible-edge-gitops/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/ideas-for-customization/Ideas for Customization Why change it? One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/devsecops/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/devsecops/ideas-for-customization/Ideas for Customization More desirable tools in the development pipeline One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/industrial-edge/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/industrial-edge/ideas-for-customization/Ideas for Customization Why change it? One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/multicloud-gitops-portworx/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/multicloud-gitops-portworx/ideas-for-customization/Ideas for customization Why change it? One of the major goals of the Red Hat patterns development process is to create modular, customizable demos.Ideas for Customizationhttps://validatedpatterns.io/patterns/retail/ideas-for-customization/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/retail/ideas-for-customization/Ideas for CustomizationSecretshttps://validatedpatterns.io/learn/secrets/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/secrets/Infrastructure Background Enterprise applications require security, especially in multi-cluster and multi-site environments. Applications require trust and use certificates and other secrets in order to establish and maintain trust.HashiCorp Vaulthttps://validatedpatterns.io/learn/vault/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/vault/Deploying HashiCorp Vault in a validated pattern Prerequisites You have deployed/installed a validated pattern using the instructions provided for that pattern.Troubleshootinghttps://validatedpatterns.io/patterns/ansible-edge-gitops/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/patterns/ansible-edge-gitops/troubleshooting/Troubleshooting Our Issue Tracker Please file an issue if you see a problem!FAQhttps://validatedpatterns.io/learn/faq/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/learn/faq/FAQ What is a Validated Pattern? Validated Patterns are collections of applications (in the ArgoCD sense) that demonstrate aspects of hub/edge computing that seem interesting and useful.Multicluster DevSecOpshttps://validatedpatterns.io/blog/2022-12-01-multicluster-devsecops/Thu, 01 Dec 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-12-01-multicluster-devsecops/A validated pattern that uses OpenShift Platform Plus and OpenShift Pipelines to securely build, scan, and deliver applicationsProgressive Delivery with Argo Rolloutshttps://validatedpatterns.io/blog/2022-11-20-argo-rollouts/Thu, 03 Nov 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-11-20-argo-rollouts/Argo Rollouts lets us simplify delivery strategies like blue/green and canary deployments.Multi-cluster GitOps with Provisioninghttps://validatedpatterns.io/blog/2022-10-12-acm-provisioning/Wed, 12 Oct 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-10-12-acm-provisioning/With validated patterns, you can easily create and configure complex cluster topologiesUsing subdomain in your OpenShift route definitionshttps://validatedpatterns.io/blog/2022-09-02-route/Fri, 02 Sep 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-09-02-route/When to use subdomain when defining a Route in OpenShiftUsing clusterGroups in the Validated Patterns Frameworkhttps://validatedpatterns.io/blog/2022-08-24-clustergroups/Wed, 24 Aug 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-08-24-clustergroups/Defining what we mean by clusterGroups in the Validated Pattern Framework (and how to use them)Push or Pull?https://validatedpatterns.io/blog/2022-07-15-push-vs-pull/Fri, 15 Jul 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-07-15-push-vs-pull/Considerations on Push and Pull in change management systemsAnsible Edge GitOpshttps://validatedpatterns.io/blog/2022-06-30-ansible-edge-gitops/Thu, 30 Jun 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-06-30-ansible-edge-gitops/A validated pattern that introduces Ansible and Virtualization to the frameworkMulti-Cloud GitOpshttps://validatedpatterns.io/blog/2022-03-30-multicloud-gitops/Wed, 30 Mar 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-03-30-multicloud-gitops/A validated pattern for multi-cluster and/or multi-cloud gitopsTo musthave or to mustonlyhavehttps://validatedpatterns.io/blog/2022-03-23-acm-mustonlyhave/Wed, 23 Mar 2022 00:00:00 +0000https://validatedpatterns.io/blog/2022-03-23-acm-mustonlyhave/ACM has multiple enforcement strategies, be careful which one you useMedical Diagnosishttps://validatedpatterns.io/blog/2021-12-31-medical-diagnosis/Fri, 31 Dec 2021 00:00:00 +0000https://validatedpatterns.io/blog/2021-12-31-medical-diagnosis/A validated pattern for the medical fieldInternal CI Statushttps://validatedpatterns.io/ci/internal/Mon, 01 Jan 0001 00:00:00 +0000https://validatedpatterns.io/ci/internal/These are the latest results of the Validated Patterns CI test runs. The links on this page are internal Red Hat links and require a valid Red Hat login to access them. \ No newline at end of file diff --git a/learn/about/index.html b/learn/about/index.html index 3d769a1bf..54c277d45 100644 --- a/learn/about/index.html +++ b/learn/about/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/community/index.html b/learn/community/index.html index 425a53b4c..9ddcb2c92 100644 --- a/learn/community/index.html +++ b/learn/community/index.html @@ -155,7 +155,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -810,7 +809,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1453,7 +1454,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1549,7 +1550,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1558,8 +1559,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/faq/index.html b/learn/faq/index.html index 64b7a7386..95c06208d 100644 --- a/learn/faq/index.html +++ b/learn/faq/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/implementation/index.html b/learn/implementation/index.html index 17d248832..f3c8c6531 100644 --- a/learn/implementation/index.html +++ b/learn/implementation/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/importing-a-cluster/index.html b/learn/importing-a-cluster/index.html index 15267ebf7..0cb64846c 100644 --- a/learn/importing-a-cluster/index.html +++ b/learn/importing-a-cluster/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/index.html b/learn/index.html index 886cf1c1a..7fbb3bc61 100644 --- a/learn/index.html +++ b/learn/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/infrastructure/index.html b/learn/infrastructure/index.html index 8d4db2536..86b16c99a 100644 --- a/learn/infrastructure/index.html +++ b/learn/infrastructure/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/ocp-cluster-general-sizing/index.html b/learn/ocp-cluster-general-sizing/index.html index c12ff80f3..5823ef946 100644 --- a/learn/ocp-cluster-general-sizing/index.html +++ b/learn/ocp-cluster-general-sizing/index.html @@ -154,7 +154,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -809,7 +808,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1452,7 +1453,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1548,7 +1549,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1557,8 +1558,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/page/2/index.html b/learn/page/2/index.html index f7c2b6420..5fe1c3c4a 100644 --- a/learn/page/2/index.html +++ b/learn/page/2/index.html @@ -154,7 +154,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -809,7 +808,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1452,7 +1453,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1548,7 +1549,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1557,8 +1558,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/page/3/index.html b/learn/page/3/index.html index 27c7bb84f..a8e31ef00 100644 --- a/learn/page/3/index.html +++ b/learn/page/3/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/quickstart/index.html b/learn/quickstart/index.html index 4c1670c84..c085a3afa 100644 --- a/learn/quickstart/index.html +++ b/learn/quickstart/index.html @@ -161,7 +161,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -816,7 +815,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1459,7 +1460,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1555,7 +1556,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1564,8 +1565,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/rhel-for-edge-general-sizing/index.html b/learn/rhel-for-edge-general-sizing/index.html index 785bbd367..000be423d 100644 --- a/learn/rhel-for-edge-general-sizing/index.html +++ b/learn/rhel-for-edge-general-sizing/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/secrets/index.html b/learn/secrets/index.html index 28036d5e8..2d7c32623 100644 --- a/learn/secrets/index.html +++ b/learn/secrets/index.html @@ -152,7 +152,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -807,7 +806,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1450,7 +1451,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1546,7 +1547,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1555,8 +1556,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/using-validated-pattern-operator/index.html b/learn/using-validated-pattern-operator/index.html index 13cb3f3e8..bca95c1fb 100644 --- a/learn/using-validated-pattern-operator/index.html +++ b/learn/using-validated-pattern-operator/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/validated/index.html b/learn/validated/index.html index de436bef4..db788ff5b 100644 --- a/learn/validated/index.html +++ b/learn/validated/index.html @@ -176,7 +176,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -831,7 +830,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1474,7 +1475,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1570,7 +1571,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1579,8 +1580,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/vault/index.html b/learn/vault/index.html index 1d681fd28..804fb76b0 100644 --- a/learn/vault/index.html +++ b/learn/vault/index.html @@ -176,7 +176,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -831,7 +830,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1474,7 +1475,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1570,7 +1571,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1579,8 +1580,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/learn/workflow/index.html b/learn/workflow/index.html index f73b67efd..02438c47a 100644 --- a/learn/workflow/index.html +++ b/learn/workflow/index.html @@ -172,7 +172,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -827,7 +826,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1470,7 +1471,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1566,7 +1567,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1575,8 +1576,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/ansible-automation-platform/index.html b/patterns/ansible-edge-gitops/ansible-automation-platform/index.html index 5331e9c96..cb4accdcd 100644 --- a/patterns/ansible-edge-gitops/ansible-automation-platform/index.html +++ b/patterns/ansible-edge-gitops/ansible-automation-platform/index.html @@ -184,7 +184,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -839,7 +838,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1482,7 +1483,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1578,7 +1579,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1587,8 +1588,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/cluster-sizing/index.html b/patterns/ansible-edge-gitops/cluster-sizing/index.html index 77a524d84..884da81d9 100644 --- a/patterns/ansible-edge-gitops/cluster-sizing/index.html +++ b/patterns/ansible-edge-gitops/cluster-sizing/index.html @@ -151,7 +151,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -806,7 +805,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1449,7 +1450,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1545,7 +1546,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1554,8 +1555,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/getting-started/index.html b/patterns/ansible-edge-gitops/getting-started/index.html index bab53bd0b..ca158f7db 100644 --- a/patterns/ansible-edge-gitops/getting-started/index.html +++ b/patterns/ansible-edge-gitops/getting-started/index.html @@ -206,7 +206,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -861,7 +860,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1504,7 +1505,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1600,7 +1601,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1609,8 +1610,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/ideas-for-customization/index.html b/patterns/ansible-edge-gitops/ideas-for-customization/index.html index 85845bdaa..1aabbd76b 100644 --- a/patterns/ansible-edge-gitops/ideas-for-customization/index.html +++ b/patterns/ansible-edge-gitops/ideas-for-customization/index.html @@ -344,7 +344,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -999,7 +998,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1642,7 +1643,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1738,7 +1739,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1747,8 +1748,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/index.html b/patterns/ansible-edge-gitops/index.html index d47f9887b..46fa96e75 100644 --- a/patterns/ansible-edge-gitops/index.html +++ b/patterns/ansible-edge-gitops/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/installation-details/index.html b/patterns/ansible-edge-gitops/installation-details/index.html index 729281419..07cafaaee 100644 --- a/patterns/ansible-edge-gitops/installation-details/index.html +++ b/patterns/ansible-edge-gitops/installation-details/index.html @@ -158,7 +158,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -813,7 +812,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1456,7 +1457,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1552,7 +1553,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1561,8 +1562,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/openshift-virtualization/index.html b/patterns/ansible-edge-gitops/openshift-virtualization/index.html index 9aecad0ce..76d3fad60 100644 --- a/patterns/ansible-edge-gitops/openshift-virtualization/index.html +++ b/patterns/ansible-edge-gitops/openshift-virtualization/index.html @@ -356,7 +356,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -1011,7 +1010,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1654,7 +1655,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1750,7 +1751,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1759,8 +1760,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/ansible-edge-gitops/troubleshooting/index.html b/patterns/ansible-edge-gitops/troubleshooting/index.html index f46581c6e..91756ea6b 100644 --- a/patterns/ansible-edge-gitops/troubleshooting/index.html +++ b/patterns/ansible-edge-gitops/troubleshooting/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/cockroachdb/index.html b/patterns/cockroachdb/index.html index 8f86399d7..4143fbe28 100644 --- a/patterns/cockroachdb/index.html +++ b/patterns/cockroachdb/index.html @@ -150,7 +150,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -805,7 +804,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1448,7 +1449,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1544,7 +1545,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1553,8 +1554,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/connected-vehicle-architecture/index.html b/patterns/connected-vehicle-architecture/index.html index bbc8b6829..85d4448b5 100644 --- a/patterns/connected-vehicle-architecture/index.html +++ b/patterns/connected-vehicle-architecture/index.html @@ -150,7 +150,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -805,7 +804,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1448,7 +1449,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1544,7 +1545,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1553,8 +1554,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/devsecops/cluster-sizing/index.html b/patterns/devsecops/cluster-sizing/index.html index 2547cd74d..04bb3e194 100644 --- a/patterns/devsecops/cluster-sizing/index.html +++ b/patterns/devsecops/cluster-sizing/index.html @@ -157,7 +157,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -812,7 +811,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1455,7 +1456,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1551,7 +1552,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1560,8 +1561,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/devsecops/devel-cluster/index.html b/patterns/devsecops/devel-cluster/index.html index fa9982427..ceab03b2c 100644 --- a/patterns/devsecops/devel-cluster/index.html +++ b/patterns/devsecops/devel-cluster/index.html @@ -164,7 +164,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -819,7 +818,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1462,7 +1463,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1558,7 +1559,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1567,8 +1568,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/devsecops/getting-started/index.html b/patterns/devsecops/getting-started/index.html index ffc8ea9ca..7fa051e53 100644 --- a/patterns/devsecops/getting-started/index.html +++ b/patterns/devsecops/getting-started/index.html @@ -190,7 +190,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -845,7 +844,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1488,7 +1489,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1584,7 +1585,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1593,8 +1594,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/devsecops/ideas-for-customization/index.html b/patterns/devsecops/ideas-for-customization/index.html index c76477b8c..af14757d0 100644 --- a/patterns/devsecops/ideas-for-customization/index.html +++ b/patterns/devsecops/ideas-for-customization/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/devsecops/index.html b/patterns/devsecops/index.html index 78f0d0385..384f52191 100644 --- a/patterns/devsecops/index.html +++ b/patterns/devsecops/index.html @@ -153,7 +153,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -808,7 +807,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1451,7 +1452,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1547,7 +1548,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1556,8 +1557,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/devsecops/production-cluster/index.html b/patterns/devsecops/production-cluster/index.html index 4b21948ad..dcaee92ff 100644 --- a/patterns/devsecops/production-cluster/index.html +++ b/patterns/devsecops/production-cluster/index.html @@ -162,7 +162,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -817,7 +816,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1460,7 +1461,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1556,7 +1557,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1565,8 +1566,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/devsecops/secure-supply-chain-demo/index.html b/patterns/devsecops/secure-supply-chain-demo/index.html index 2793e8f9d..21c6a3898 100644 --- a/patterns/devsecops/secure-supply-chain-demo/index.html +++ b/patterns/devsecops/secure-supply-chain-demo/index.html @@ -149,7 +149,6 @@ Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern. Using the Emerging Disease Detection pattern The following steps describes how you can use this pattern in a demo. Viewing the Sepsis Detection dashboard TO-DO: Describe how to examine the various parts of the Sepsis application -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/emerging-disease-detection/edd-getting-started/",breadcrumb:"/patterns/emerging-disease-detection/edd-getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/":{title:"Getting started",tags:[],content:` Deploying the Multicloud GitOps pattern Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. @@ -804,7 +803,9 @@ Click the “Add” button next to a menu item; the item name will appear. Add a name for the order: You can add as many orders as you want. On your last item, click the “Place Order” button on the item dialog: As the orders are serviced by the barista and kitchen services, you can see their status in the “Orders” section of the page: -`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern For information on minimum hardware requirements for an OpenShift cluster, refer to the {ocp} documentation for System and environment requirements. +`,url:"https://validatedpatterns.io/patterns/retail/application/",breadcrumb:"/patterns/retail/application/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-cluster-sizing/":{title:"Cluster sizing",tags:[],content:` About OpenShift cluster sizing for the Multicloud GitOps Pattern The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example: +For AWS, see Installing OpenShift Container Platform on AWS. +For bare-metal, see Installing OpenShift Container Platform on bare metal. To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: Name Kind Namespace Description multicloud-gitops-hub Application @@ -1447,7 +1448,7 @@ Initial User login (cloud-user) In general, and before the VMs have been configured by the Ansible Jobs, you can log in to the VMs on the console using the user and password you specified in the Helm chart, or else you can look at the VirtualMachine object and see what the username and password setting are. The pattern, by design, replaces the typical console view with Firefox running in kiosk mode. But this mechanism can still be used if you change the console from “VNC Console” to “Serial Console”. The “extra” VM Template Also included in the edge-gitops-vms chart is a separate template that will allow the creation of VMs with similar (though not identical characteristics) to the ones defined in the chart. The rhel8-kiosk-with-svc template is preserved as an intermediate step to creating your own VM types, to see how the pipeline from default VM template -> customized template -> Helm-variable chart can work. -Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern {mcg-pattern} One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. +Next Steps Help & Feedback Report Bugs `,url:"https://validatedpatterns.io/patterns/ansible-edge-gitops/openshift-virtualization/",breadcrumb:"/patterns/ansible-edge-gitops/openshift-virtualization/"},"https://validatedpatterns.io/patterns/multicloud-gitops/mcg-ideas-for-customization/":{title:"Ideas for customization",tags:[],content:`Ideas for customization About customizing the pattern Multicloud GitOps pattern One of the major goals of the Validated Patterns development process is to create modular, customizable demos. The Multicloud Gitops is just an example of a pattern managing multiple clusters in a GitOps fashion. It contains a very simple config-demo application, which prints out a secret that was injected into the vault through an out-of-band mechanism. You can customize this demo in different ways. Split the config-demo across hub and regional clusters Currently hub and regional clusters are reusing the exact same helm chart found at charts/all/config-demo. The first customization step could be to split the demo app in two separate charts: one in charts/hub/config-demo and one in charts/region/config-demo. Once charts/all/config-demo has been copied to charts/hub/config-demo and charts/region/config-demo, you need to include them in the respective values-hub.yaml and values-region-one.yaml, respectively. After completing this configuration, you can start customizing the two apps and make them output a different web page entirely depending if the pod is running on the hub or on the cluster. @@ -1543,7 +1544,7 @@ We will review pull requests to our pattern repositories. `,url:"https://validatedpatterns.io/learn/faq/",breadcrumb:"/learn/faq/"},"https://validatedpatterns.io/patterns/hypershift/":{title:"HyperShift",tags:[],content:`About the HyperShift pattern (hosted control plane) Background This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters. Workflow Install multicluster engine for Kubernetes Operator -Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview). +Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature. Install the AWS Controllers for Kubernetes - Amazon S3 Operator Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC) Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired. @@ -1552,8 +1553,8 @@ The HyperShift pattern uses the following products and technologies: Red Hat OpenShift Container Platform for container orchestration Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution -multicluster engine for Kubernetes, the multicluster-engine provider -{ack-s3}, a S3 storage controller +The multicluster engine for Kubernetes Operator, the multicluster-engine provider +AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller `,url:"https://validatedpatterns.io/patterns/hypershift/",breadcrumb:"/patterns/hypershift/"},"https://validatedpatterns.io/patterns/":{title:"Patterns",tags:[],content:`Browse through available patterns and their respective documentation for deployment and operation. Filter patterns by type, industry, and product. `,url:"https://validatedpatterns.io/patterns/",breadcrumb:"/patterns/"},"https://validatedpatterns.io/":{title:"Validated Patterns",tags:[],content:` Reference architectures with added value Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application. diff --git a/patterns/emerging-disease-detection/edd-getting-started/index.html b/patterns/emerging-disease-detection/edd-getting-started/index.html index 991cff8c1..8e03ea419 100644 --- a/patterns/emerging-disease-detection/edd-getting-started/index.html +++ b/patterns/emerging-disease-detection/edd-getting-started/index.html @@ -61,8 +61,7 @@ kam kam-openshift-gitops.apps.wh-edd-cluster.aws.validatedpatterns.com kam 8443 passthrough/None None openshift-gitops-server openshift-gitops-server-openshift-gitops.apps.wh-edd-cluster.aws.validatedpatterns.com openshift-gitops-server https passthrough/Redirect None # admin.password -FdGgWHsBYkeqOczE3PuRpU1jLn7C2fD6

The most important ArgoCD instance to examine at this point is emerging-disease-detection-hub. This is where all the applications for the pattern can be tracked.

  • Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern.

    • Using the Emerging Disease Detection pattern

    The following steps describes how you can use this pattern in a demo.

    Viewing the Sepsis Detection dashboard

    TO-DO: Describe how to examine the various parts of the Sepsis application

    Next Steps

    Help & Feedback -Report Bugs

    QUICKLINKS

    The most important ArgoCD instance to examine at this point is emerging-disease-detection-hub. This is where all the applications for the pattern can be tracked.

  • Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern.

    • Using the Emerging Disease Detection pattern

    The following steps describes how you can use this pattern in a demo.

    Viewing the Sepsis Detection dashboard

    TO-DO: Describe how to examine the various parts of the Sepsis application

    QUICKLINKS

    CONTRIBUTE

    HyperShift

    Validation status:
    Community
    CI status:
    Links:

    About the HyperShift pattern (hosted control plane)

    Background

    This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters.

    Workflow

    • Install multicluster engine for Kubernetes Operator

    • Create an instance of the MultiClusterEngine to enable hypershift, which is a [technology preview feature](https://access.redhat.com/support/offerings/techpreview).

    • Install the AWS Controllers for Kubernetes - Amazon S3 Operator

    • Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC)

    • Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired.

    hypershift high level architecture
    Figure 1. source: https://hypershift-docs.netlify.app/

    If you have any questions or concerns contact Jonny Rickard.

    About the solution elements

    The solution enables the rapid provisioning of hosted control plane.

    The HyperShift pattern uses the following products and technologies:

    • Red Hat OpenShift Container Platform for container orchestration

    • Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution

    • multicluster engine for Kubernetes, the multicluster-engine provider

    • {ack-s3}, a S3 storage controller

    QUICKLINKS

    About the HyperShift pattern (hosted control plane)

    Background

    This pattern simplifies the deployment of an hosted control plane or hosted control plane cluster. Use this pattern to create hosted control plane clusters.

    Workflow

    • Install multicluster engine for Kubernetes Operator

    • Create an instance of the MultiClusterEngine to enable hypershift, which is a technology preview feature.

    • Install the AWS Controllers for Kubernetes - Amazon S3 Operator

    • Create an S3 bucket that hosted control plane will use for OpenID Connect (OIDC)

    • Create a buildconfig and imagestream that provide the HyperShift cli (hypershift) as an imagestream to be used in further automation if desired.

    hypershift high level architecture
    Figure 1. source: https://hypershift-docs.netlify.app/

    If you have any questions or concerns contact Jonny Rickard.

    About the solution elements

    The solution enables the rapid provisioning of hosted control plane.

    The HyperShift pattern uses the following products and technologies:

    • Red Hat OpenShift Container Platform for container orchestration

    • Red Hat OpenShift GitOps, a GitOps continuous delivery (CD) solution

    • The multicluster engine for Kubernetes Operator, the multicluster-engine provider

    • AWS Controllers for Kubernetes - Amazon S3 Operator, an S3 storage controller

    QUICKLINKS

    CONTRIBUTE