Add file mode change in branch sandboxing blog

Author: kirilldorr

adminforth/documentation/blog/2026-06-01-branch-sandboxing-k3s/index.md

@@ -436,6 +436,12 @@ docker push "${IMAGE_FULL_TAG}"
 echo "LOG: Sandbox image build and push complete. IMAGE_FULL_TAG=${IMAGE_FULL_TAG}"
 ```
 
+After this
+
+```bash
+chmod +x deploy/sandboxing/build-and-push-sandbox.sh
+```
+
 Here, you should pay attention to the **APP_SOURCE_CODE_PATH** variable and make sure it correctly points to the directory containing your source code and Dockerfile. Also, if necessary, repeat the `docker build` and `docker push` steps for the number of images you need.
 
 Next, we need to configure the autoscaler. In the `deploy/sandboxing` directory, create a file named `deploy/sandboxing/manage-autoscaler.sh`:
@@ -577,6 +583,12 @@ elif [[ "$ACTION" == "uninstall" ]]; then
 fi
 ```
 
+And
+
+```bash
+chmod +x deploy/sandboxing/manage-autoscaler.sh
+```
+
 When running this specific script, we’ll activate the sandbox for our repository with just a single command.
 
 Next is a file designed to address a problem that may seem minor at first glance but is actually very important: resource limits. Since we’re working with Kubernetes and AWS ASG, this is a mandatory requirement. When configuring a Kubernetes manifest or Helm chart, engineers do not always specify resource limits, and this is a common practice. However, because of this, the autoscaler—which is responsible for creating new instances—will not recognize the need for that new instance because it will not know even the approximate amount of resources being used.