Skip to main content
DeploymentsVirtual applianceAdministration

Networking

Configure the appliance's network settings.

Network Requirements​

The Appliance uses k3s default subnets (see: https://docs.k3s.io/cli/server#networking)

  • cluster-cidr "10.42.0.0/16" IPv4/IPv6 network CIDRs to use for pod IPs-
  • service-cidr "10.43.0.0/16" 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:

Port/ProtocolDescription
22/TCPSSH access
80/TCPUsed for the Management API to manage the Appliance, and for submitting jobs 1
443/TCPUsed for HTTPS communication with the above services
9000/TCPUsed for the websocket connection to the realtime transcription service 2
9004/TCPUsed for the secure websocket connection to the realtime transcription service 2
9001/TCPPrometheus metrics
3100/TCPLoki logs endpoint

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.

Footnotes​

  1. Websocket service only available in realtime mode. ↩

  2. Jobs service only available in batch mode. ↩ ↩2