Amazon Elastic Kubernetes Service (EKS) requirements

Amazon Elastic Kubernetes Service (EKS)¶

This section outlines the supplementary configuration required for the Amazon Elastic Kubernetes Service (EKS) to successfully run the DataRobot platform.

備考

Fulfillment of the generic Kubernetes requirements is mandatory before proceeding.

The services described below are presumed to be part of an EKS deployment since the target environment is an AWS account. While these services are recommended for a standard DataRobot installation on EKS setup, this page does not cover cluster configurations that omit them.

AWS service integration {: aws-service-integration }¶

Amazon service	リファレンス
EKS	See Supported Kubernetes versions.
OIDC	Required for OpenID Connect (OIDC) identity providers.
IRSA	Required for IAM Roles for service accounts.
S3	DataRobot object storage.
ECR	Primary container image registry and Image Build Service repository.

EKS managed add-ons {: eks-managed add-ons }¶

EKS managed add-on	リファレンス
Amazon EBS CSI Driver	See Use Kubernetes volume storage with Amazon EBS
Amazon VPC CNI	See Assign IPs to Pods with the Amazon VPC CNI
CoreDNS	See Manage CoreDNS for DNS in Amazon EKS clusters
kube-proxy	See Manage kube-proxy in Amazon EKS clusters

Amazon Elastic Container Registry (ECR) {: ecr-container-registry}¶

You can install the DataRobot platform by pulling the application images from your private Amazon Elastic Container Registry (ECR). Alternatively, you can use the Docker Hub registry.

備考

Private ECR is mandatory if you intend to use DataRobot's Custom Models functionality.

See the Amazon Elastic Container Registry Documentation AWS documentation for details.

Network policy engine¶

Custom model and custom task features benefit from a Network Policy Engine to enforce Kubernetes Network Policies. It is recommended, but not required, to ensure the security of custom model pods.

See Limit Pod traffic with Kubernetes network policies AWS documentation for details.