Skip to main content


Transcription:Batch   Deployments:Virtual Appliance

Network Requirements


The Appliance uses k3s default subnets (see:

  • cluster-cidr "" IPv4/IPv6 network CIDRs to use for pod IPs-
  • service-cidr "" IPv4/IPv6 network CIDRs to use for service IPs

You need to ensure that any network you use does not have an IP address conflict.

Configure Networking

The Virtual Appliance will attempt to acquire an IP address via DHCP.

If you need to configure a static IP address, you can log into the Appliance and follow the instructions from the official Ubuntu documentation

Firewall Ports

There are several firewall rules that may need to be enabled to ensure the communication can be made to the Virtual Appliance:

22/TCPSSH access
80/TCPUsed for the Management API to manage the Appliance, and for submitting jobs
443/TCPUsed for HTTPS communication with the above services
9001/TCPPrometheus metrics
3100/TCPLoki logs endpoint *

*: External Access blocked by default see Loki

Using Proxies

If the network that you are deploying your Appliance into does not have a direct route to the Internet, you may need to use a proxy server in order to talk to the cloud-based usage reporting service. See the relevant section in Licensing for details on how to set this up.