Added Tags to All Docs

operations/automation/ansible/awx/awx-kerberos-implementation.md

@@ -1,3 +1,11 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Kerberos
+  - Automation
+---
+
 ## Kerberos Implementation
 You may find that you need to be able to run playbooks on domain-joined Windows devices using Kerberos.  You need to go through some extra steps to set this up after you have successfully fully deployed AWX Operator into Kubernetes.
 

operations/automation/ansible/awx/connect-awx-to-gitea.md

@@ -1,3 +1,11 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Gitea
+  - Automation
+---
+
 **Purpose**: Once AWX is deployed, you will want to connect Gitea at https://git.bunny-lab.io.  The reason for this is so we can pull in our playbooks, inventories, and templates automatically into AWX, making it more stateless overall and more resilient to potential failures of either AWX or the underlying Kubernetes Cluster hosting it.
 
 ## Obtain Gitea Token

operations/automation/ansible/awx/deployment/awx-in-minikube.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Automation
+---
+
 # Deploy AWX on Minikube Cluster
 Minikube Cluster based deployment of Ansible AWX. (Ansible Tower)
 !!! note Prerequisites

operations/automation/ansible/awx/deployment/awx-operator.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Automation
+---
+
 **Purpose**:
 Deploying a Rancher RKE2 Cluster-based Ansible AWX Operator server.  This can scale to a larger more enterprise environment if needed.
 

operations/automation/ansible/awx/deployment/upgrading-issues-past-2-10-0.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Automation
+---
+
 ## Upgrading from 2.10.0 to 2.19.1+
 There is a known issue with upgrading / install AWX Operator beyond version 2.10.0, because of how the PostgreSQL database upgrades from 13.0 to 15.0, and has changed permissions.  The following workflow will help get past that and adjust the permissions in such a way that allows the upgrade to proceed successfully.  If this is a clean installation, you can also perform this step if the fresh install of 2.19.1 is not working yet. (It wont work out of the box because of this bug).  `The developers of AWX seem to just not care about this issue, and have not implemented an official fix themselves at this time).