Merge pull request redhat-edge-computing#6 from danmacpherson/content-migration

Bulk migration of content

Author: danmacpherson

config.yaml

@@ -18,6 +18,9 @@ markup:
     startLevel: 1
     endLevel: 2
     ordered: false
+  goldmark:
+    renderer:
+      unsafe: true
 
 taxonomies:
   industry: 'industries'

content/blog/2021-12-31-medical-diagnosis.md

@@ -1,13 +1,12 @@
 ---
-layout: post
 date: 2021-12-31
 title: Medical Diagnosis
-excerpt: A validated pattern for the medical field
-published: true
+summary: A validated pattern for the medical field
 blog_tags:
 - medical-diagnosis
 - xray
 - validated-pattern
+aliases: /2021/12/31/medical-diagnosis/
 ---
 
 # Validated Pattern: Medical Diagnosis

content/blog/2022-03-23-acm-mustonlyhave.md

@@ -1,11 +1,10 @@
 ---
-layout: post
 date: 2022-03-23
 title: To musthave or to mustonlyhave
-excerpt: ACM has multiple enforcement strategies, be careful which one you use
-published: true
+summary: ACM has multiple enforcement strategies, be careful which one you use
 blog_tags:
 - acm
+aliases: /2022/03/23/acm-mustonlyhave/
 ---
 
 Recently a user reported an issue when using the multicloud-gitops pattern: Namely, after testing changes in a feature branch (adding a helm application), said changes were not appearing on the remote clusters.

content/blog/2022-03-30-multicloud-gitops.md

@@ -1,13 +1,12 @@
 ---
-layout: post
 date: 2022-03-30
 title: Multi-Cloud GitOps
-excerpt: A validated pattern for multi-cluster and/or multi-cloud gitops
-published: true
+summary: A validated pattern for multi-cluster and/or multi-cloud gitops
 blog_tags:
 - multi-cloud gitops
 - xray
 - validated-pattern
+aliases: /2022/03/30/multicloud-gitops/
 ---
 
 # Validated Pattern: Multi-Cloud GitOps

content/blog/2022-06-30-ansible-edge-gitops.md

@@ -1,12 +1,11 @@
 ---
-layout: post
 date: 2022-06-30
 title: Ansible Edge GitOps
-excerpt: A validated pattern that introduces Ansible and Virtualization to the framework
-published: true
+summary: A validated pattern that introduces Ansible and Virtualization to the framework
 blog_tags:
 - ansible-edge-gitops
 - patterns
+aliases: /2022/06/30/ansible-edge-gitops/
 ---
 
 # Validated Pattern: Ansible Edge GitOps

content/blog/2022-07-15-push-vs-pull.md

@@ -1,13 +1,12 @@
 ---
-layout: post
 date: 2022-07-15
 title: Push or Pull?
-excerpt: Considerations on Push and Pull in change management systems
-published: true
+summary: Considerations on Push and Pull in change management systems
 blog_tags:
 - ansible-edge-gitops
 - patterns
 - GitOps
+aliases: /2022/07/15/push-vs-pull/
 ---
 
 # Push or Pull? Strategies for Large Scale Technology Change Management on the Edge

content/blog/2022-08-24-clustergroups.md

@@ -1,11 +1,10 @@
 ---
-layout: post
 date: 2022-08-24
 title: Using clusterGroups in the Validated Patterns Framework
-excerpt: Defining what we mean by clusterGroups in the Validated Pattern Framework (and how to use them)
-published: true
+summary: Defining what we mean by clusterGroups in the Validated Pattern Framework (and how to use them)
 blog_tags:
 - validated-pattern
+aliases: /2022/08/24/clustergroups/
 ---
 
 # What Is a clusterGroup?

content/blog/2022-09-02-route.md

@@ -1,13 +1,12 @@
 ---
-layout: post
 date: 2022-09-02
 title: Using subdomain in your OpenShift route definitions
-excerpt: When to use subdomain when defining a Route in OpenShift
-published: true
+summary: When to use subdomain when defining a Route in OpenShift
 blog_tags:
 - validated-pattern
 - openshift
 - route
+aliases: /2022/09/02/route/
 ---
 
 # What Is a route in OpenShift?

content/blog/2022-10-12-acm-provisioning.md

@@ -1,14 +1,13 @@
 ---
-layout: post
 date: 2022-10-12
 title: Multi-cluster GitOps with Provisioning
-excerpt: With validated patterns, you can easily create and configure complex cluster topologies
-published: true
+summary: With validated patterns, you can easily create and configure complex cluster topologies
 blog_tags:
 - acm
 - provisioning
 - patterns
 - GitOps
+aliases: /2022/10/12/acm-provisioning/
 ---
 
 # Multi-cluster GitOps with Provisioning
@@ -32,21 +31,25 @@ Let’s walk through an example using the Multi-Cloud GitOps pattern as an examp
 
 ## Preparation
 
-Start by [deploying](https://hybrid-cloud-patterns.io/multicloud-gitops/getting-started/) the Multi-cloud GitOps pattern on AWS.
-
 If you've never deployed OpenShift before, you could try [ROSA](https://cloud.redhat.com/learn/getting-started-red-hat-openshift-service-aws-rosa/deploy-rosa-cluster)
 the pay-as-you-go OpenShift managed service.
 
-Next, you'll need to create a fork of the
-https://github.com/hybrid-cloud-gitops/multicloud-gitops/ repo.  Go there in a
-browser, make sure you’re logged in to GitHub, click the “Fork” button, and
-confirm the destination by clicking the big green "Create fork" button.
+| Installing a validated pattern |
+| ------------------------------ |
+| [![Installing a validated pattern](https://img.youtube.com/vi/N6XPh-9XZAM/mqdefault.jpg "Installing a validated pattern")](https://youtu.be/N6XPh-9XZAM) |
+
+Start by [deploying](https://hybrid-cloud-patterns.io/multicloud-gitops/getting-started/) the Multi-cloud GitOps pattern on AWS.
+
+Next, you'll need to create a fork of the [multicloud-gitops](https://github.com/hybrid-cloud-patterns/multicloud-gitops/)
+repo.  Go there in a browser, make sure you’re logged in to GitHub, click the
+“Fork” button, and confirm the destination by clicking the big green "Create
+fork" button.
 
 Now you have a copy of the pattern that you can make changes to.  You can read
 more about the Multi-cloud GitOps pattern on our [community
 site](https://hybrid-cloud-patterns.io/multicloud-gitops/)
 
-Next, [install the Validated Patterns operator]([https://hybrid-cloud-patterns.io/infrastructure/using-validated-pattern-operator/](https://youtu.be/AHLam3u8eKM)) from Operator Hub.
+Next, [install the Validated Patterns operator](https://hybrid-cloud-patterns.io/infrastructure/using-validated-pattern-operator/) from Operator Hub.
 
 And finally, click through to the installed operator, and select the `Create
 instance` button and fill out the Create a Pattern form.  Most of the defaults
@@ -68,17 +71,20 @@ credentials.  To do this you can either manually load the secrets into the
 vault via the UI, or make use of the following process for loading them from a
 machine you control.
 
+| Loading provisioning secrets |
+| ---------------------------- |
+| [![Loading provisioning secrets](https://img.youtube.com/vi/LSDUTfZvcyA/mqdefault.jpg "Loading provisioning secrets")](https://youtu.be/LSDUTfZvcyA) |
 
 First clone your fork of the repository onto your local machine, and copy the template to a location not controlled by Git (to avoid accidentally committing the contents)
 
-```
+```sh
 git clone [email protected]:{yourfork}/multicloud-gitops.git
 cp values-secret.yaml.template ~/values-secret.yaml
 ```
 
 You will need to uncomment and provide values for the following keys in order to make use of the provisioning functionality:
 
-```
+```yaml
 secrets:
   aws:                                       [1]
     access_key_id: AKIAIOSFODNN7EXAMPLE
@@ -89,32 +95,33 @@ files:
   openshiftPullSecret: ~/.dockerconfigjson   [3]
 ```
 
-_[1]_ A guide to finding the relevant AWS values can be found at
-https://docs.aws.amazon.com/powershell/latest/userguide/pstools-appendix-sign-up.html
+_[1]_ A guide to finding the relevant AWS values can be found [here](https://docs.aws.amazon.com/powershell/latest/userguide/pstools-appendix-sign-up.html)
 You might even have them in a `~/.aws/credentials` file.
 
 _[2]_ The public key is used to allow access to OpenShift nodes for triage purposes.
 
-_[3]_ The openshiftPullSecret is how Red Hat knows you’ve got a licence to install
-OpenShift.  To obtain one, go to
-https://console.redhat.com/openshift/install/pull-secret, save the contents, and
-provide that path in the secrets file.  The contents should start with something
-like: `{"auths":{"cloud.openshift.com":{"auth":"...`.
+_[3]_ The openshiftPullSecret is how Red Hat knows you’ve got a licence to
+install OpenShift.  To obtain one, go
+[here](https://console.redhat.com/openshift/install/pull-secret), save the
+contents, and provide that path in the secrets file.  The contents should start
+with something like: `{"auths":{"cloud.openshift.com":{"auth":"...`.
 
 Obtain the login command for your cluster and run it locally.
-![console login](/images/provision/console-login.png)
+![console login](/images/console-login.png)
 
 Ensure `podman` is installed, and load the secrets with:
 
-```
+```sh
 ./common/scripts/pattern-util.sh make load-secrets
 ```
 
-[![Loading provisioning secrets](https://img.youtube.com/vi/zagNOk21RPo/default.jpg "Loading provisioning secrets")](https://youtu.be/zagNOk21RPo)
-
 These values will be used to create a number of secrets that ACM expects in
 order to provision clusters.
 
+| Loading Secrets into the Cluster |
+| ------------------------- |
+| [![Loading secrets into the cluster](https://img.youtube.com/vi/LSDUTfZvcyA/mqdefault.jpg "Loading secrets into the cluster")](https://youtu.be/LSDUTfZvcyA) |
+
 ## Define a Managed Cluster Group
 
 Managed cluster groups are sets of clusters, grouped by function, that share a
@@ -124,7 +131,7 @@ of approximately 1000 clusters in total.
 
 The following is the example we will use today:
 
-```
+```yaml
   managedClusterGroups:
     myFirstGroup:
       name: group-one
@@ -156,8 +163,13 @@ on-demand and at scale.
 
 You can read more about cluster pools in the [ACM documentation](https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html/multicluster_engine/multicluster_engine_overview#managing-cluster-pools)
 
+| Defining the cluster pool | Defining clusters |
+| ------------------------- | ----------------- |
+| [![Defining and scaling the cluster pool](https://img.youtube.com/vi/FaomChtlUE4/mqdefault.jpg "Defining and scaling the cluster pool")](https://youtu.be/FaomChtlUE4) | [![Defining clusters](https://img.youtube.com/vi/IJk3vTjMPCo/mqdefault.jpg "Defining clusters")](https://youtu.be/IJk3vTjMPCo) |
+
 Each managed cluster group can have multiple pools, here is an example:
-```
+
+```yaml
       clusterPools:
         myFirstPool:
           name: aws-ap
@@ -185,17 +197,21 @@ If `.size` is omitted, the pool will automatically resize based on the number of
 clusters specified.  Specifying no clusters will define the pool, but not
 provision any clusters.
 
-[![Defining and scaling the cluster pool](https://img.youtube.com/vi/FaomChtlUE4/default.jpg "Defining and scaling the cluster pool")](https://youtu.be/FaomChtlUE4)
-
-[![Defining clusters](https://img.youtube.com/vi/M-BJrEeoNd4/default.jpg "Defining clusters")](https://youtu.be/M-BJrEeoNd4)
-
 ## Delivering Applications and Configuration to Clusters
 
-[![Updating the managed cluster configuration](https://img.youtube.com/vi/emn_Coqp5jQ/default.jpg "Updating the managed cluster configuration")](https://youtu.be/emn_Coqp5jQ)
+| Delivering Configuration Changes |
+| -------------------------------- |
+| [![Updating the managed cluster configuration](https://img.youtube.com/vi/oorZnch-ggY/mqdefault.jpg "Updating the managed cluster configuration")](https://youtu.be/oorZnch-ggY) |
 
 ## Deprovisioning Clusters
 
-[![Deprovisioning clusters](https://img.youtube.com/vi/F_-sne3U5ew/default.jpg "Deprovisioning clusters")](https://youtu.be/F_-sne3U5ew)
+As the provisioning data only exists on the ACM hub cluster, it is important to ensure any managed clusters are deprovisioned _before_ the hub itself is destroyed.  In general this involves scaling down the pool(s), and removing the entries in the `clusters:` list.
+
+You can see the process in action below:
+
+| Deprovisioning clusters |
+| ----------------------- |
+| [![Deprovisioning clusters](https://img.youtube.com/vi/ik5LR-ouPdo/mqdefault.jpg "Deprovisioning clusters")](https://youtu.be/ik5LR-ouPdo) |
 
 ## Conclusion