Add edit helmfile for branch sandboxing blog & Change recommended volume size in k3s deploy blog

Author: kirilldorr

adminforth/documentation/blog/2025-11-04-k3s-ec2-deployment/index.md

@@ -205,7 +205,7 @@ resource "aws_instance" "ec2_instance" {
   }
 
   root_block_device {
-    volume_size = 10 // Size in GB for root partition
+    volume_size = 20 // Size in GB for root partition
     volume_type = "gp2"
 
     # Even if the instance is terminated, the volume will not be deleted, delete it manually if needed

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

@@ -324,7 +324,7 @@ resource "aws_launch_template" "worker" {
   block_device_mappings {
     device_name = "/dev/sda1"
     ebs {
-      volume_size           = 10
+      volume_size           = 20
       volume_type           = "gp3"
       delete_on_termination = true
     }
@@ -802,6 +802,30 @@ jobs:
 
 This file is responsible for creating a new isolated environment when pushing to a new branch. Please note the comments in the code that indicate variables you will most likely need to replace with your own.
 
+## Configure your deployment
+
+This section of the guide specifically focuses on using a Helmfile as a package manager. If you are using a different deployment method, such as vanilla Helm or native Kubernetes manifests, the code implementation will differ. 
+The point of this change is to pass the sandbox domain and its unique namespace to the deployment. If your main application is deployed following the instructions from one of our [previous blog posts](https://adminforth.dev/blog/k3s-ec2-deployment/), you can simply add the corresponding code to `helmfile.yaml`.
+
+```yaml title="/deploy/helm/helmfile.yaml"
+releases:
+  - name: '{{ requiredEnv "APP_NAMESPACE" }}'
+    namespace: '{{ requiredEnv "APP_NAMESPACE" }}'
+    createNamespace: true
+    chart: .
+    values:
+      - values.yaml
+      - ecrImageFull: '{{ requiredEnv "IMAGE_FULL_TAG" }}'
+      //diff-add
+      - appNameSpace: '{{ requiredEnv "APP_NAMESPACE" }}'
+//diff-add
+{{ if env "APP_HOST" }}
+//diff-add
+      - host: '{{ env "APP_HOST" }}'
+//diff-add
+{{ end }}
+```
+
 ## Deploying a Sandbox
 
 Now, to ensure that a new environment is created whenever you push to a new branch, all you need to do is run the script `deploy/sandboxing/manage-autoscaler.sh`. Once it finishes, a new sandbox and a DNS record for the domain you specified will be created, and all of this will be automatically deleted when the branch is deleted. Simply run the following in the terminal: