Create config map for all variables and secrets, update ingress-service.yaml to use config map, update yaml files to include persistent volume if recommended or necessary, update nginx-proxy-deployment to use latest nginx proxy manager and proxy for ghost-blog-deployment, add resource limits for nginx-proxy-deployment, add mysql-pv and mysql-pvc yaml files, and update yaml files to reference latest changes.

README.md

@@ -21,4 +21,21 @@ This configuration is using a Persistent Volume to store the Ghost blog data, th
 ingress-service.yaml
 In this example, $(VAR_HOST) and $(SECRET_NAME) are variables that are stored in a configMap and a Secret, respectively. These variables can be managed and updated separately from the YAML files, making it easier to update and maintain your configuration.
 
-To use variables in your YAML files, you'll first need to create a configMap and a Secret that contains the variables you need. You can do this using the kubectl
+To use variables in your YAML files, you'll first need to create a configMap and a Secret that contains the variables you need. You can do this using the kubectl
+
+
+kubectl apply -f nginx-pv.yaml
+kubectl apply -f nginx-pvc.yaml
+kubectl apply -f mysql-pv.yaml
+kubectl apply -f mysql-pvc.yaml
+kubectl apply -f blog-pv.yaml
+kubectl apply -f blog-pvc.yaml
+
+kubectl apply -f ghost-blog-deployment.yaml
+kubectl apply -f mysql-deployment.yaml
+kubectl apply -f nginx-proxy-deployment.yaml
+kubectl apply -f ghost-blog-service.yaml
+kubectl apply -f ingress-service.yaml
+kubectl apply -f mysql-service.yaml
+kubectl apply -f nginx-proxy-service.yaml
+kubectl apply -f blog-config-map.yaml