Skip to content

Commit

Permalink
deploy: 2b1044c
Browse files Browse the repository at this point in the history
  • Loading branch information
mbaldessari committed Oct 3, 2023
1 parent c37c0cb commit 92e9477
Show file tree
Hide file tree
Showing 112 changed files with 789 additions and 789 deletions.
14 changes: 7 additions & 7 deletions blog/2021-12-31-medical-diagnosis/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@
[source,javascript]
`,url:"https://validatedpatterns.io/contribute/contribute-to-docs/",breadcrumb:"/contribute/contribute-to-docs/"},"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 OpenShift -> Clusters -> Create cluster.
Select Services -> Containers -> Create cluster.
The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster.
Optional: A second OpenShift cluster for multicloud demonstration.
Install the tooling dependencies.
Expand Down Expand Up @@ -333,7 +333,7 @@
Uninstalling We currently do not support uninstalling this pattern.
`,url:"https://validatedpatterns.io/patterns/industrial-edge/getting-started/",breadcrumb:"/patterns/industrial-edge/getting-started/"},"https://validatedpatterns.io/patterns/medical-diagnosis/getting-started/":{title:"Getting Started",tags:[],content:`Deploying the Medical Diagnosis pattern Prerequisites An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShiftClusters → Create cluster.
Select ServicesContainers → Create cluster.
The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster.
A GitHub account and a token for it with repositories permissions, to read from and write to your forks.
An S3-capable Storage set up in your public or private cloud for the x-ray images
Expand Down Expand Up @@ -395,7 +395,7 @@
$ oc scale deploymentconfig/image-generator --replicas=0 Watch the dashboard stop processing images.
You can also simulate the change of the AI model version - as it’s only an environment variable in the Serverless Service configuration.
$ oc patch service.serving.knative.dev/risk-assessment --type=json -p '[{"op":"replace","path":"/spec/template/metadata/annotations/revisionTimestamp","value":"'"$(date +%F_%T)"'"},{"op":"replace","path":"/spec/template/spec/containers/0/env/0/value","value":"v2"}]' This changes the model version value, and the revisionTimestamp in the annotations, which triggers a redeployment of the service.
`,url:"https://validatedpatterns.io/patterns/medical-diagnosis/getting-started/",breadcrumb:"/patterns/medical-diagnosis/getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops-portworx/getting-started/":{title:"Getting Started",tags:[],content:`Deploying the Multicloud GitOps pattern Prerequisite An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select OpenShift -> Clusters -> Create cluster. The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster. Optional: A second OpenShift cluster for multicloud demonstration. The git binary and podman. For details see Installing Git and Installing Podman The use of this pattern depends on having at least one running Red Hat OpenShift cluster. It is desirable to have a cluster for deploying the GitOps management hub assets and a separate cluster(s) for the managed cluster(s).
`,url:"https://validatedpatterns.io/patterns/medical-diagnosis/getting-started/",breadcrumb:"/patterns/medical-diagnosis/getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops-portworx/getting-started/":{title:"Getting Started",tags:[],content:`Deploying the Multicloud GitOps pattern Prerequisite An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster. Optional: A second OpenShift cluster for multicloud demonstration. The git binary and podman. For details see Installing Git and Installing Podman The use of this pattern depends on having at least one running Red Hat OpenShift cluster. It is desirable to have a cluster for deploying the GitOps management hub assets and a separate cluster(s) for the managed cluster(s).
If you do not have a running Red Hat OpenShift cluster, you can start one on a public or private cloud by using Red Hat’s cloud service.
Procedure For installation tooling dependencies, see link:https://validatedpatterns.io/learn/quickstart/[Patterns quick start].
{% include prerequisite-tools.md %}
Expand Down Expand Up @@ -575,7 +575,7 @@
By default the clusterGroup applications are deployed on all clusters that RHACM manages. In the value-hub.yaml, file add a managedClusterCgroup for each cluster or group of clusters that you want to manage as one.
managedClusterGroups: - name: region-one helmOverrides: - name: clusterGroup.isHubCluster value: false clusterSelector: matchLabels: clusterGroup: region-one The above YAML file segment deploys the clusterGroup applications on managed clusters with the label clusterGroup=region-one. Specific subscriptions and Operators, applications and projects for that clusterGroup are then managed in a value-region-one.yaml file. For example:
namespaces: - config-demo projects: - config-demo applications: config-demo: name: config-demo namespace: config-demo project: config-demo path: charts/all/config-demo #Subscriptions can be added too - multicloud-gitops at present does not require subscriptions on its managed clusters #subscriptions: # example-subscription: # name: example-operator # namespace: example-namespace # channel: example-channel # csv: example-operator.v1.0.0 subscriptions: Important: Ensure that you commit the changes and push them to GitHub so that GitOps can fetch your changes and apply them.
Deploying a managed cluster Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select OpenShift -> Clusters -> Create cluster. To join the managed cluster to the management hub, you can:
Deploying a managed cluster Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. To join the managed cluster to the management hub, you can:
Use the Red Hat Advanced Cluster Management (RHACM) web console Use the cm tool Use the clusteradm tool Using Red Hat Advanced Cluster Management web console to set up managed cluster After RHACM is installed, a message regarding a “Web console update is available” might be displayed. Click the “Refresh web console” link.
In the left navigation panel of web console, click local-cluster. Select All Clusters. The RHACM web console is displayed with Cluster* on the left navigation panel.
On the Managed clusters tab, click Import cluster.
Expand Down Expand Up @@ -608,7 +608,7 @@
namespaces: - config-demo projects: - config-demo applications: config-demo: name: config-demo namespace: config-demo project: config-demo path: charts/all/config-demo #Subscriptions can be added too - multicloud-gitops at present does not require subscriptions on its managed clusters #subscriptions: . # example-subscription # name: example-operator # namespace: example-namespace # channel: example-channel # csv: example-operator.v1.0.0 subscriptions: Ensure that you commit the changes and push them to GitHub so that GitOps can fetch your changes and apply them.
Deploying a managed cluster by using Red Hat Advanced Cluster Management Prerequistes An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShiftClusters → Create cluster.
Select ServicesContainers → Create cluster.
Red Hat Advanced Cluster Management (RHACM) web console to join the managed cluster to the management hub
After RHACM is installed, a message regarding a Web console update is available" might be displayed. Follow the instructions and click the Refresh web console link.
Procedure In the left navigation panel of web console, click local-cluster. Select All Clusters. The RHACM web console is displayed with Cluster* on the left navigation panel.
Expand All @@ -617,7 +617,7 @@
Now that RHACM is no longer deploying the managed cluster applications everywhere, you must indicate that the new cluster has the managed cluster role.
Optional: Deploying a managed cluster by using cm-cli tool Prerequistes An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShift -> Clusters -> Create cluster.
Select Services -> Containers -> Create cluster.
The cm-cli tool
Procedure Obtain the KUBECONFIG file from the managed cluster.
Open a shell prompt and login into the management hub cluster by using either of the following methods:
Expand All @@ -626,7 +626,7 @@
cm attach cluster --cluster <cluster-name> --cluster-kubeconfig <path-to-path_to_kubeconfig> Next steps Designate the new cluster as a managed cluster site
Optional: Deploying a managed cluster by using the clusteradm tool Prerequistes An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShiftClusters → Create cluster.
Select ServicesContainers → Create cluster.
The clusteradm tool
Procedure To deploy an edge cluster, you must to get the token from the management hub cluster. Run the following command on the existing management hub or datacenter cluster:
clusteradm get token The command generates a token and shows you the command to use on the managed cluster.
Expand Down
14 changes: 7 additions & 7 deletions blog/2022-03-23-acm-mustonlyhave/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@
[source,javascript]
`,url:"https://validatedpatterns.io/contribute/contribute-to-docs/",breadcrumb:"/contribute/contribute-to-docs/"},"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 OpenShift -> Clusters -> Create cluster.
Select Services -> Containers -> Create cluster.
The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster.
Optional: A second OpenShift cluster for multicloud demonstration.
Install the tooling dependencies.
Expand Down Expand Up @@ -403,7 +403,7 @@
Uninstalling We currently do not support uninstalling this pattern.
`,url:"https://validatedpatterns.io/patterns/industrial-edge/getting-started/",breadcrumb:"/patterns/industrial-edge/getting-started/"},"https://validatedpatterns.io/patterns/medical-diagnosis/getting-started/":{title:"Getting Started",tags:[],content:`Deploying the Medical Diagnosis pattern Prerequisites An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShiftClusters → Create cluster.
Select ServicesContainers → Create cluster.
The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster.
A GitHub account and a token for it with repositories permissions, to read from and write to your forks.
An S3-capable Storage set up in your public or private cloud for the x-ray images
Expand Down Expand Up @@ -465,7 +465,7 @@
$ oc scale deploymentconfig/image-generator --replicas=0 Watch the dashboard stop processing images.
You can also simulate the change of the AI model version - as it’s only an environment variable in the Serverless Service configuration.
$ oc patch service.serving.knative.dev/risk-assessment --type=json -p '[{"op":"replace","path":"/spec/template/metadata/annotations/revisionTimestamp","value":"'"$(date +%F_%T)"'"},{"op":"replace","path":"/spec/template/spec/containers/0/env/0/value","value":"v2"}]' This changes the model version value, and the revisionTimestamp in the annotations, which triggers a redeployment of the service.
`,url:"https://validatedpatterns.io/patterns/medical-diagnosis/getting-started/",breadcrumb:"/patterns/medical-diagnosis/getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops-portworx/getting-started/":{title:"Getting Started",tags:[],content:`Deploying the Multicloud GitOps pattern Prerequisite An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select OpenShift -> Clusters -> Create cluster. The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster. Optional: A second OpenShift cluster for multicloud demonstration. The git binary and podman. For details see Installing Git and Installing Podman The use of this pattern depends on having at least one running Red Hat OpenShift cluster. It is desirable to have a cluster for deploying the GitOps management hub assets and a separate cluster(s) for the managed cluster(s).
`,url:"https://validatedpatterns.io/patterns/medical-diagnosis/getting-started/",breadcrumb:"/patterns/medical-diagnosis/getting-started/"},"https://validatedpatterns.io/patterns/multicloud-gitops-portworx/getting-started/":{title:"Getting Started",tags:[],content:`Deploying the Multicloud GitOps pattern Prerequisite An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. The cluster must have a dynamic StorageClass to provision PersistentVolumes. See sizing your cluster. Optional: A second OpenShift cluster for multicloud demonstration. The git binary and podman. For details see Installing Git and Installing Podman The use of this pattern depends on having at least one running Red Hat OpenShift cluster. It is desirable to have a cluster for deploying the GitOps management hub assets and a separate cluster(s) for the managed cluster(s).
If you do not have a running Red Hat OpenShift cluster, you can start one on a public or private cloud by using Red Hat’s cloud service.
Procedure For installation tooling dependencies, see link:https://validatedpatterns.io/learn/quickstart/[Patterns quick start].
{% include prerequisite-tools.md %}
Expand Down Expand Up @@ -645,7 +645,7 @@
By default the clusterGroup applications are deployed on all clusters that RHACM manages. In the value-hub.yaml, file add a managedClusterCgroup for each cluster or group of clusters that you want to manage as one.
managedClusterGroups: - name: region-one helmOverrides: - name: clusterGroup.isHubCluster value: false clusterSelector: matchLabels: clusterGroup: region-one The above YAML file segment deploys the clusterGroup applications on managed clusters with the label clusterGroup=region-one. Specific subscriptions and Operators, applications and projects for that clusterGroup are then managed in a value-region-one.yaml file. For example:
namespaces: - config-demo projects: - config-demo applications: config-demo: name: config-demo namespace: config-demo project: config-demo path: charts/all/config-demo #Subscriptions can be added too - multicloud-gitops at present does not require subscriptions on its managed clusters #subscriptions: # example-subscription: # name: example-operator # namespace: example-namespace # channel: example-channel # csv: example-operator.v1.0.0 subscriptions: Important: Ensure that you commit the changes and push them to GitHub so that GitOps can fetch your changes and apply them.
Deploying a managed cluster Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select OpenShift -> Clusters -> Create cluster. To join the managed cluster to the management hub, you can:
Deploying a managed cluster Prerequisites An OpenShift cluster To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console. Select Services -> Containers -> Create cluster. To join the managed cluster to the management hub, you can:
Use the Red Hat Advanced Cluster Management (RHACM) web console Use the cm tool Use the clusteradm tool Using Red Hat Advanced Cluster Management web console to set up managed cluster After RHACM is installed, a message regarding a “Web console update is available” might be displayed. Click the “Refresh web console” link.
In the left navigation panel of web console, click local-cluster. Select All Clusters. The RHACM web console is displayed with Cluster* on the left navigation panel.
On the Managed clusters tab, click Import cluster.
Expand Down Expand Up @@ -678,7 +678,7 @@
namespaces: - config-demo projects: - config-demo applications: config-demo: name: config-demo namespace: config-demo project: config-demo path: charts/all/config-demo #Subscriptions can be added too - multicloud-gitops at present does not require subscriptions on its managed clusters #subscriptions: . # example-subscription # name: example-operator # namespace: example-namespace # channel: example-channel # csv: example-operator.v1.0.0 subscriptions: Ensure that you commit the changes and push them to GitHub so that GitOps can fetch your changes and apply them.
Deploying a managed cluster by using Red Hat Advanced Cluster Management Prerequistes An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShiftClusters → Create cluster.
Select ServicesContainers → Create cluster.
Red Hat Advanced Cluster Management (RHACM) web console to join the managed cluster to the management hub
After RHACM is installed, a message regarding a Web console update is available" might be displayed. Follow the instructions and click the Refresh web console link.
Procedure In the left navigation panel of web console, click local-cluster. Select All Clusters. The RHACM web console is displayed with Cluster* on the left navigation panel.
Expand All @@ -687,7 +687,7 @@
Now that RHACM is no longer deploying the managed cluster applications everywhere, you must indicate that the new cluster has the managed cluster role.
Optional: Deploying a managed cluster by using cm-cli tool Prerequistes An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShift -> Clusters -> Create cluster.
Select Services -> Containers -> Create cluster.
The cm-cli tool
Procedure Obtain the KUBECONFIG file from the managed cluster.
Open a shell prompt and login into the management hub cluster by using either of the following methods:
Expand All @@ -696,7 +696,7 @@
cm attach cluster --cluster <cluster-name> --cluster-kubeconfig <path-to-path_to_kubeconfig> Next steps Designate the new cluster as a managed cluster site
Optional: Deploying a managed cluster by using the clusteradm tool Prerequistes An OpenShift cluster
To create an OpenShift cluster, go to the Red Hat Hybrid Cloud console.
Select OpenShiftClusters → Create cluster.
Select ServicesContainers → Create cluster.
The clusteradm tool
Procedure To deploy an edge cluster, you must to get the token from the management hub cluster. Run the following command on the existing management hub or datacenter cluster:
clusteradm get token The command generates a token and shows you the command to use on the managed cluster.
Expand Down
Loading

0 comments on commit 92e9477

Please sign in to comment.