diff --git a/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md b/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md
index 7d5c703..c4eebec 100644
--- a/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md	
+++ b/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md	
@@ -159,9 +159,6 @@ kubectl apply -f krb5-configmap.yml
 kubectl apply -k .
 ```
 
-!!! warning "Be Patient - Wait 20 Minutes"
-    The process may take a while to spin up AWX, postgresql, redis, and other workloads necessary for AWX to function.  Depending on the speed of the server, it may take between 5 and 20 minutes for AWX to be ready to connect to.  You can watch the progress via the CLI commands listed above, or directly on Rancher's WebUI at https://rancher.bunny-lab.io.  
-
 ## Access the AWX WebUI behind Ingress Controller
 After you have deployed AWX into the cluster, it will not be immediately accessible to the host's network (such as your personal computer) unless you set up a DNS record pointing to it.  In the example above, you would have an `A` or `CNAME` DNS record pointing to the internal IP address of the Rancher RKE2 Cluster host.