Network Configuration
- The ingress behind which AI Center will be installed needs to be able to connect to the Orchestrator machine (domain and port).
- The ingress behind which AI Center will be installed needs to be able to connect to the SQL Server (domain/IP and port).
- Robots/Studio that will make use of AI Center need connectivity to the AI Center Ingress.
Connectivity Requirements - Online Install
The AI Center Online install refers to an on-premises installation that downloads AI Center application and all related artifacts (e.g. machine learning models) from the internet.
Endpoints the Installer Connects
The AI Center installer downloads container images and machine learning models to populate your AI Center instance with ready-to-use machine learning (this includes Document Understanding models). For this reason, at installation time, the K8s Ingress needs access to these endpoints over https (port 443):
Host Name | Purpose |
|---|---|
registry.replicated.com | Upstream Docker images are pulled via registry.replicated.com. This domain is owned by Replicated, Inc which is headquartered in Los Angeles, CA |
proxy.replicated.com | Upstream Docker images are pulled via proxy.replicated.com. The on-prem docker client uses a license ID to authenticate to proxy.replicated.com. This domain is owned by Replicated, Inc which is headquartered in Los Angeles, CA |
replicated.app | Upstream application YAML and metadata is pulled from replicated.app. The current running version of the application (if any) will be sent, in addition to a license ID and an application IDs are sent to replicated.app to authenticate and receive these YAML files. This domain is owned by Replicated, Inc which is headquartered in Los Angeles, CA |
get.replicated.com | Sync artifacts from replicated. This domain is owned by Replicated, Inc which is headquartered in Los Angeles, CA |
api.replicated.com | API requests to infrastructure installer. This domain is owned by Replicated, Inc which is headquartered in Los Angeles, CA |
k8s.kurl.sh | Kubernetes cluster installation scripts and artifacts are served from kurl.sh. An application identifier is sent in a URL path, and bash scripts and binary executables are served from kurl.sh. This domain is owned by Replicated, Inc which is headquartered in Los Angeles, CA |
kurl-sh.s3.amazonaws.com | tar.gz packages are downloaded from Amazon S3 during embedded cluster installations. The IP ranges to whitelist for accessing these can be scraped dynamically from the AWS IP Address Ranges1 documentation. |
*.docker.io | Upstream Docker images are pulled from docker.io. There may be multiple subdomains like registry-1.docker.io thus the pattern to the right should be allowed. |
*.docker.com | Other upstream Docker images are pulled from docker.com. There may be multiple subdomains thus the pattern to the right should be allowed. |
raw.githubusercontent.com | For scripts to create persistent volume claim deployment. |
Endpoints Connected To at Runtime
At runtime, an AI Center that was installed via the online installer connects to these endpoints:
Host Name | Purpose |
|---|---|
du-metering.uipath.com | To account for, and validate Document Understanding licenses. |
registry.replicated.com | Upstream Docker images are pulled via a private docker registry from registry.replicated.com. This domain is owned by Replicated, Inc which is headquartered in Los Angeles, CA. |
raw.githubusercontent.com | For scripts to update OOB models daily. |
custom (optional) | This depends on how the persona using AI Center has chosen to build their ml packages. AI Center dynamically builds a container image. The dependencies for that image can be bundled within the ML Package itself (in which case no extra outbound network calls are done), or can be specified in a requirements.txt file. This file can specify the location from which dependencies will be downloaded. |
Updated 3 months ago