Portal in Kubernetes

Running VeilNet Portal in Kubernetes #

VeilNet Portals are designed to be lightweight and portable — making them perfect for container orchestration platforms like Kubernetes.

If you’re already using Kubernetes and want to run your Portal there, you can easily convert the provided docker-compose.yaml into a Kubernetes deployment using Kompose, a command-line tool that translates Docker Compose files to Kubernetes manifests.

Step-by-Step Guide #

🧾 1. Download the Docker Compose File #

From the VeilNet Console:

Navigate to your Portal
Click Deploy
Select Docker Compose
Copy or download the docker-compose.yaml file to your local machine

🔁 2. Convert Using Kompose #

Follow the official guide:
👉 Convert Docker Compose to Kubernetes

Install kompose if you haven’t already:

				
					curl -L https://github.com/kubernetes/kompose/releases/latest/download/kompose-linux-amd64 -o kompose
chmod +x kompose
sudo mv kompose /usr/local/bin/

Then run:

				
					kompose convert

🚀 3. Deploy to Your Cluster #

Apply the generated manifests to your cluster:

				
					kubectl apply -f .

Notes #

Your Portal will now run as a Kubernetes-managed deployment.
All environment variables and volumes will be preserved from the Compose file.
You can monitor the Portal using:

				
					kubectl logs -f deployment/veilnet-portal

✅ This method allows full compatibility with Kubernetes environments without writing YAML from scratch.

⚠️ Important: Avoid Subnet Overlaps #

If you are using a private domain (e.g., to connect your local network or internal services through the Portal), you must ensure that the private domain’s subnet does not overlap with the internal Pod CIDR or Service CIDR used by your Kubernetes cluster.

Overlapping IP ranges may cause:

Traffic routing failures
Pod/service reachability issues
Broken or inconsistent VeilNet behavior

To check your cluster’s subnets, run:

				
					kubectl cluster-info dump | grep -i cluster-cidr