diff --git a/Servers/Containerization/Kubernetes/Migrating Docker-Compose.yml to k8s.md b/Servers/Containerization/Kubernetes/Migrating Docker-Compose.yml to k8s.md
index 8f6656d..65a2cec 100644
--- a/Servers/Containerization/Kubernetes/Migrating Docker-Compose.yml to k8s.md	
+++ b/Servers/Containerization/Kubernetes/Migrating Docker-Compose.yml to k8s.md	
@@ -149,3 +149,27 @@ This will attempt to convert the `docker-compose.yml` file into a Kubernetes man
         requests:
           storage: 100Mi
     ```
+
+## Deploy Workload into Rancher RKE2 Cluster
+At this point, you need to import the yaml file you created into the Kubernetes cluster.  This will occur in four sequential stages:
+
+- Setting up a "**Project**" to logically organize your containers
+- Setting up a "**Namespace**" for your container to isolate it from other containers in your Kubernetes cluster
+- Importing the YAML file into the aforementioned namespace
+- Configuring Ingress to allow external access to the container / service stack.
+
+### Create a Project
+The purpose of the project is to logically organize your services together.  This can be something like `Home Automation`, `Log Analysis Systems`, `Network Tools`, etc.  You can do this by logging into your Rancher RKE2 cluster (e.g. https://rke2-cluster.bunny-lab.io).  This Project name is unique to Rancher and purely used for organizational purposes and does not affect the namespaces / containers in any way.
+
+- Navigate to: **Clusters > `local` > Projects/Namespaces > "Create Project"**
+  - **Name**: <Friendly Name> (e.g. `Home Automation`)
+  - **Description**: <Useful Description for the Group of Services> (e.g. `Various services that automate things within Bunny Lab`)
+  - Click the "**Create**" button
+
+### Create a Namespace within the Project
+At this point, we need to create a namespace.  This basically isolates the networking, credentials, secrets, and storage between the services/stacks.  This ensures that if someone exploits one of your services, they will not be able to laterally move into another service within the same Kubernetes cluster.
+
+- Navigate to: **Clusters > `local` > Projects/Namespaces > <ProjectName> > "Create Namespace"**
+  - The name for the namespace should be named based on its operational-context, such as `prod-ntfy` or `dev-ntfy`.
+
+  
\ No newline at end of file