Isolet is a framework to deploy linux wargames like Bandit. It uses pre-configured templates to provide isolated instance using kubernetes pods for each user.

• Features
• Tech Stack
• Setup
• Installation
• Configuration
  • General
  • Instance
  • Secrets

• Isolated access to each pod
• Kubernetes manages the pods and scaling
• Limited time for each instance
• Instances can be extended
• Run time variables to avoid rebuilding images
• Email verification for registration

• Go
• TypeScript
• ReactJS
• TailwindCSS
• Kubernetes

Clone the repository

git clone https://github.com/TheAlpha16/isolet.git

This setup is specific for Standard GKE cluster. Check out the documentation of your service provider for specifics.

• StorageClass Isolet by default uses standard-rwo which supports only ReadWriteOnce the volume can be mounted as read-write by a single node. To change the StorageClass check the options available in your cluster

kubectl get sc

Choose an appropriate one and replace standard-rwo it in the db-volume.yml file.

metadata:
  name: db-pv-claim
spec:
  storageClassName: standard-rwo
  accessModes:
    - ReadWriteOnce

• NodePort Isolet uses service of type NodePort to expose pods for the user. You might need to configure your cloud services to allow traffic into the instances.

While creating node you need to add network tag to the node. Like in the sample above nodes are being added isolet-node.

gcloud compute firewall-rules create kube-node-port-fw-rule \
    --action allow \
    --target-tags isolet-node \
    --source-ranges 0.0.0.0/0 \
    --rules tcp:30000-32767 \
    --no-enable-logging

• ExternalIP If you have a static IP address to use, especially useful in case you want to setup domain name for your deployment, replace the IP address in the loadBalancerIP field of proxy-service in proxy-main.yml

apiVersion: v1
kind: Service
metadata:
  name: proxy-svc
  labels:
    app: proxy-svc
spec:
  ports:
    - port: 80
  selector:
    app: proxy
  type: LoadBalancer
  loadBalancerIP: 35.23.13.211

To reserve a static external IP address in GCP

gcloud compute addresses create <NAME_OF_THE_IP> --project=<PROJECT_ID> --region=us-central1

1. Install kubectl on your machine
2. Spin up a cluster on your favourite cloud provider or if you wish to test locally, install minikube

Here is a sample gcloud command line for the cluster

gcloud beta container --project <PROJECT_ID> clusters create <CLUSTER_NAME> --no-enable-basic-auth --cluster-version "1.27.7-gke.1121000" --release-channel "regular" --machine-type "e2-medium" --image-type "COS_CONTAINERD" --disk-type "pd-balanced" --disk-size "30" --node-labels app=node --metadata disable-legacy-endpoints=true --scopes "https://www.googleapis.com/auth/devstorage.read_only","https://www.googleapis.com/auth/logging.write","https://www.googleapis.com/auth/monitoring","https://www.googleapis.com/auth/servicecontrol","https://www.googleapis.com/auth/service.management.readonly","https://www.googleapis.com/auth/trace.append" --num-nodes "1" --logging=SYSTEM,WORKLOAD --monitoring=SYSTEM --enable-ip-alias --network "projects/<PROJECT_NAME>/global/networks/default" --subnetwork "projects/<PROJECT_NAME>/regions/<PROJECT_REGION>/subnetworks/default" --no-enable-intra-node-visibility --default-max-pods-per-node "110" --security-posture=standard --workload-vulnerability-scanning=disabled --enable-dataplane-v2 --no-enable-master-authorized-networks --addons HorizontalPodAutoscaling,HttpLoadBalancing,GcePersistentDiskCsiDriver --enable-autoupgrade --enable-autorepair --max-surge-upgrade 1 --max-unavailable-upgrade 0 --binauthz-evaluation-mode=DISABLED --enable-managed-prometheus --enable-shielded-nodes --tags "isolet-node" --node-locations "us-central1-c"

Change the instance configuration of nodes as per your workload requirements

3. Configure kubectl to access the cluster
4. Edit the challs.json file according to your challenges
5. Change the registry variable to your image repository in update.sh

resource=""
registry="docker.io/thealpha"

6. Run the update.sh script to build the images

./update.sh

7. Update the image in the yml files under definition

spec:
  replicas: 1
  selector:
    matchLabels:
      app: api
  template:
    metadata:
      name: api-deployment
      labels:
        app: api
    spec:
      containers:
        - name: api
          image: docker.io/thealpha16/isolet-api
          imagePullPolicy: Always

8. Configure the variable according to your requirements. Check out Configuration
9. Run the init.sh script

./init.sh

You can customize the application using environment variables passed to the deployments. All the options are available in configuration

• CTF_NAME Name of the CTF to be deployed

• PUBLIC_URL URL of the deployed application. Required for email verification

• PROXY_SERVER_NAME Domains and subdomains to be added under server_name directive in nginx proxy.

• INSTANCE_HOSTNAME Domain name for accessing the spawned instances

• IMAGE_REGISTRY Default registry for pulling challenge images. Can be overridden in the challenge configuration for individual challenges

• KUBECONFIG_FILE_PATH Path to the kubernetes config file to access cluster from outside

• UI_URL host for frontend in case it exists. If kubernetes is being used for deployment, you can specify URL to be

<SERVICE_NAME_OF_UI>.<NAMESPACE>.svc.cluster.local

• INSTANCE_NAMESPACE Namespace for deploying the user requested pods.

• CONCURRENT_INSTANCES Number of concurrent pods that user can spawn.

• TERMINATION_PERIOD Time in seconds to be given to the pod for graceful shutdown.

• INSTANCE_TIME Time in minutes to be added in the pod annotations after which ripper will remove the instance

• MAX_INSTANCE_TIME Time in minutes the user can extend the instance

• CPU_REQUEST Number of cores to be reserved for the pod

• CPU_LIMIT Maximum number of cores the pod can consume

• MEMORY_REQUEST Amount of memory to be reserved for the pod

• MEMORY_LIMIT Maximum amount of memory the pod can use

• DISK_REQUEST Disk space to be reserved for the pod

• DISK_LIMIT Maximum disk space the pod can utilize

• SESSION_SECRET Key used for signing jwt token after login

• TOKEN_SECRET Key used for signing verification token sent to mail

• INSTANCE_NAME_SECRET Key used for determining unique instance name for the pods

• EMAIL_ID Email ID to be used when sending verification mails

• EMAIL_AUTH Password for authenticating to use smtp service

• DB_HOST Host name of the database server

• DB_USER Username for the database

• DB_PASSWORD Password to authenticate to the database

• DB_NAME Name of the database