Added Tags to All Docs

platforms/containerization/docker/custom-containers/container-development.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Containers
+  - Docker
+  - Containerization
+---
+
 **Purpose**:
 This document will outline the general workflow of using Visual Studio Code to author and update custom containers and push them to a container registry hosted in Gitea.  This will be referencing the `git-repo-updater` project throughout.
 

platforms/containerization/docker/custom-containers/git-repo-updater.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Containers
+  - Docker
+  - Containerization
+---
+
 **Purpose**: Docker container running Alpine Linux that automates and improves upon much of the script mentioned in the [Git Repo Updater](../../../../reference/bash/git-repo-updater.md) document.  It offers the additional benefits of checking for updates every 5 seconds instead of every 60 seconds.  It also accepts environment variables to provide credentials and notification settings, and can have an infinite number of monitored repositories.
 
 ### Deployment

platforms/containerization/docker/deploy-portainer.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Docker
+  - Portainer
+  - Containerization
+---
+
 ### Update The Package Manager
 We need to update the server before installing Docker
 

platforms/containerization/kubernetes/deployment/k8s.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - Kubernetes
+  - Containerization
+---
+
 # Deploy Generic Kubernetes
 The instructions outlined below assume you are deploying the environment using Ansible Playbooks either via Ansible's CLI or AWX.
 

platforms/containerization/kubernetes/deployment/rancher-rke2.md

@@ -1,3 +1,11 @@
+---
+tags:
+  - Kubernetes
+  - RKE2
+  - Rancher
+  - Containerization
+---
+
 # Deploy RKE2 Cluster
 Deploying a Rancher RKE2 Cluster is fairly straightforward.  Just run the commands in-order and pay attention to which steps apply to all machines in the cluster, the controlplanes, and the workers.
 

platforms/containerization/kubernetes/migrating-docker-compose-yml-to-k8s.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Kubernetes
+  - Docker
+  - Containerization
+---
+
 # Migrating `docker-compose.yml` to Rancher RKE2 Cluster
 You may be comfortable operating with Portainer or `docker-compose`, but there comes a point where you might want to migrate those existing workloads to a Kubernetes cluster as easily-as-possible.  Lucklily, there is a way to do this using a tool called "**Kompose**'.  Follow the instructions seen below to convert and deploy your existing `docker-compose.yml` into a Kubernetes cluster such as Rancher RKE2.
 

platforms/index.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Platforms
+  - Index
+  - Documentation
+---
+
 # Platforms
 ## Purpose
 Virtualization and containerization platforms, cluster builds, and base OS images.

platforms/virtualization/hyper-v/failover-cluster/deploy-failover-cluster-node.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Documentation
+---
+
 **Purpose**: Deploying a Windows Server Node into the Hyper-V Failover Cluster is an essential part of rebuilding and expanding the backbone of my homelab.  The documentation below goes over the process of setting up a bare-metal host from scratch and integrating it into the Hyper-V Failover Cluster.
 
 !!! note "Prerequisites & Assumptions"

platforms/virtualization/hyper-v/failover-cluster/rebuild-failover-cluster-replication.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Documentation
+---
+
 **Purpose**: If you run an environment with multiple Hyper-V: Failover Clusters, for the purpose of Hyper-V: Failover Cluster Replication via a `Hyper-V Replica Broker` role installed on a host within the Failover Cluster, sometimes a GuestVM will fail to replicate itself to the replica cluster, and in those cases, it may not be able to recover on its own.  This guide attempts to outline the process to rebuild replication for GuestVMs on a one-by-one basis.
 
 !!! note "Assumptions"

platforms/virtualization/hyper-v/kerberos-enabled-vm-migration.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Kerberos
+---
+
 **Purpose**:
 You may find that you want to be able to live-migrate guestVMs on a Hyper-V environment that is not clustered as a Hyper-V Failover Cluster, you will have permission issues.  One way to work around this is to use CredSSP as the authentication mechanism, which is not ideal but useful in a pinch, or you can use Kerberos-based authentication.
 

platforms/virtualization/openstack/ansible-openstack.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - OpenStack
+  - Ansible
+---
+
 !!! warning "Document Under Construction"
     This document is very unfinished and should **NOT** be followed by anyone for deployment at this time.
 

platforms/virtualization/openstack/canonical-openstack.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - OpenStack
+---
+
 # OpenStack
 OpenStack is basically a virtual machine hypervisor that is HA and cluster-friendly.  This particular variant is deployed via Canonical's MiniStack environment using SNAP.  It will deploy OpenStack onto a single node, which can later be expanded to additional nodes.  You can also use something like OpenShift to deploy a Kubernetes Cluster onto OpenStack automatically via its various APIs.
 

platforms/virtualization/proxmox/cloud-init-templates/ubuntu-server.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - Proxmox
+  - Ubuntu
+---
+
 ## Purpose
 You may need to deploy many copies of a virtual machine rapidly, and don't want to go through the hassle of setting up everything ad-hoc as the needs arise for each VM workload.  Creating a cloud-init template allows you to more rapidly deploy production-ready copies of a template VM (that you create below) into a ProxmoxVE environment.
 

platforms/virtualization/proxmox/common-tasks.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Proxmox
+---
+
 **Purpose**: The purpose of this document is to outline common tasks that you may need to run in your cluster to perform various tasks.
 
 ## Delete Node from Cluster

platforms/virtualization/proxmox/configuring-iscsi-based-cluster-storage.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Proxmox
+  - iSCSI
+  - Storage
+---
+
 ## Purpose
 This document describes the **end-to-end procedure** for creating a **thick-provisioned iSCSI-backed shared storage target** on **TrueNAS CORE**, and consuming it from a **Proxmox VE cluster** using **shared LVM**.
 

platforms/virtualization/proxmox/operations/manually-activate-volume-group.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Proxmox
+---
+
 ## Purpose
 Sometimes in some very specific situations, you will find that an LVM / VG just won't come online in ProxmoxVE.  If this happens, you can run the following commands (and replace the placeholder location) to manually bring the storage online.
 

platforms/virtualization/proxmox/operations/upgrade-pve-from-8-to-9.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Proxmox
+---
+
 ## Purpose
 There are a few steps you have to take when upgrading ProxmoxVE from 8.4.1+ to 9.0+.  The process is fairly straightforward, so just follow the instructions seen below.
 

platforms/virtualization/proxmox/proxmoxve.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Proxmox
+---
+
 ## Initial Installation / Configuration
 Proxmox Virtual Environment is an open source server virtualization management solution based on QEMU/KVM and LXC. You can manage virtual machines, containers, highly available clusters, storage and networks with an integrated, easy-to-use web interface or via CLI.
 

platforms/virtualization/proxmox/zfs-over-iscsi.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Proxmox
+  - ZFS
+  - iSCSI
+---
+
 **Purpose**: There is a way to incorporate ProxmoxVE and TrueNAS more deeply using SSH, simplifying the deployment of virtual disks/volumes passed into GuestVMs in ProxmoxVE.  Using ZFS over iSCSI will give you the following non-exhaustive list of benefits:
 
 - Automatically make Zvols in a ZFS Storage Pool

platforms/virtualization/rancher-harvester/harvester.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - Rancher
+  - Harvester
+---
+
 **Purpose**: Rancher Harvester is an awesome tool that acts like a self-hosted cloud VDI provider, similar to AWS, Linode, and other online cloud compute platforms.  In most scenarios, you will deploy "Rancher" in addition to Harvester to orchestrate the deployment, management, and rolling upgrades of a Kubernetes Cluster.  You can also just run standalone Virtual Machines, similar to Hyper-V, RHEV, oVirt, Bhyve, XenServer, XCP-NG, and VMware ESXi.
 
 :::note Prerequisites