Requirements
Requirements for Arize On-Prem Installation
- Kubernetes v1.21+ (Important: Recommend containerd runtime)
- Namespace for Arize Deployment
- Storage - 2x storage buckets
- Credentials for Platform to Read/Write Storage
In the case of a Proof of Concept (POC) deployment our team recommends a minimum of 5 nodes, each with at least:
- 16 CPU
- 64Gi of Ram
Sizing is based on your expected volume, access patterns, and expected shape of data, please reach out to our team to discuss what best cluster sizing for your needs.
The distribution includes deployment manifests for running a blob storage implementation with one of the three major clouds:
- Google Cloud Storage
- Amazon S3
- Azure Storage
Examples of Blob Storage Credentials:
Amazon S3
config
[profile default]
region=us-east-1
...
credentials
[default]
aws_access_key_id=ACCESS_KEY
aws_secret_access_key=SECRET_KEY_123
...
aws role
annotations:
iam.amazonaws.com/role: <cluster-storage-access-role>
Google Cloud
service-account.json
{
"type": "service_account",
"project_id": "<<PROJECT ID>>",
"private_key_id": "<<PRIVATE KEY ID>>",
"private_key": "<<PRIVATE KEY>>",
...
}
Azure
service-principal-id: <id>
service-principal-password: <id>
storage-account-name: <id>
storage-account-key: <id>
The person running installation is assumed to have administrator privileges on the cluster.
kubectlinstalled and configured with user to create Workloads, ClusterRoles, and ClusterRoleBindings- permissions to create storage buckets, service accounts, and modify IAM roles
- TCP port 443 for the application
- TCP port 443 for record receivers
NAT access to the following images:
Note: Alternatively, you can mirror these images on your private container images registry.
Egress to an SMTP server with email send permissions is required for full platform functionality.
Last modified 4mo ago