Camio Flex uses components that require outbound network connections for installation and updates. In case you have firewall restrictions on outbound network traffic, review the Network Requirements below.
Components
- MicroK8s - the default Kubernetes platform on which Camio Flex runs, installed using Snap.
- Rancher - the Kubernetes Cluster orchestrator created by SUSE.
- Camio Flex - the Camio containers orchestrated to manage video workloads and tasks.
- In-Cluster Resources - the packages used inside the Kubernetes cluster that don't require outbound connections since they communicate within the cluster:
- MongoDB - Database for task management
- NATS - Queues, Fast Communication between containers.
- Prometheus, Alert Manager, Grafana - Monitoring and alerting.
- KEDA - Automatic scaling of components (e.g. multiple concurrent uploads)
Network Requirements
Summary
| host:port | notes |
|
api.snapcraft.io:443 |
Snap requirements https://snapcraft.io/docs/network-requirements for installation of MicroK8s. |
|
*.camio.com:443 |
Camio Flex communicates with the Camio Rancher service and registration servers at: |
|
*.docker.io:443 *.docker.com:443 *.us-west2-docker.pkg.dev:443 *.quay.io:443 *.registry.k8s.io:443 *.ghcr.io:443 *.k8s.gcr.io:443 prod-registry-k8s-io-us-west-1.s3.dualstack.us-west-1.amazonaws.com:443 pkg-containers.githubusercontent.com:443 |
Container registries for both MicroK8s and Camio Flex, required to pull the images used by the containers in the cluster. |
NOTE: During the conversion period from Camio Box to Camio Flex, you must also retain the same network rules you enabled for Camio Box described in the article:
Which servers does Camio Box access in its outbound network requests?
Comments