Installing the Core Components
PreviousInstalling the Infrastructure ComponentsNextVirtual Services and Gateways Command Script (GCP)
Last updated
Last updated
Before proceeding with these steps, you must first install the Aizen infrastructure components. See Installing the Infrastructure Components.
To install the Aizen core components, follow these steps:
Create the namespace aizen for the Aizen core components by running this command:
Using the Docker Hub credentials that you obtained for the Aizen microservice images (see ), create a Kubernetes Secret for accessing the Aizen images in the core namespace:
Customize the settings (see the Default Core Configuration Settings below) in the Aizen core Helm chart based on your environment and preferred configuration:
Update the STORAGE_CLASS, INGRESS_HOST, BUCKET_NAME, CLOUD_ENDPOINT_URL, CLOUD_ACCESSKEY_ID, CLOUD_SECRET_KEY, IMAGE_REPO_SECRET, MLFLOW_ACCESSKEY_ID, MLFLOW_SECRET_KEY, and MLFLOW_ENDPOINT_URL values.
For the MLFLOW_ENDPOINT_URL, use either an S3 bucket or a local MinIO bucket, but remember to create the bucket. If you are using local MinIO as an object store, make sure to set up MinIO first and then create buckets. See MinIO.
Change the default persistence size, which is hardcoded in the deployment of the various components, according to your environment.
For an Azure AKS cluster, add these properties to both infrastructure and core deployments: global.s3.azure.enabled=true
For a cloud-based deployment, add these properties to both infrastructure and core deployments:
For AUTH_TYPE, choose the authentication type that you would like to use when accessing the Aizen Jupyter console. You can specify one of these authentication types:
dummy (no authentication): This setting uses only predefined users like admin, aizenai, aizendev, <deployed namespace name> with password aizen@321.
native: This setting allows users to sign up by creating the admin user first and then additional users.
oauth: This setting uses OAuth-based authentication, such as GitHub, Google, GitLab, and so on.
ldap (default): This setting uses the Lightweight Directory Access Protocol (LDAP) and Active Directory.
Add these properties to the Aizen core Helm chart based on your chosen authentication type:
Use | to separate multiple Bind DNs, groups, and hosts. Use , to separate multiple allowed users and admin users.
For LDAP authentication:
For OAuth authentication:
If you are using github as the oauth_authenticator, set these properties:
Consider adding these optional properties for OAuth authentication:
Install the Aizen core components by running this command:
If you installed the Aizen core components on a GCP cluster, create the gateways and virtual services for the console, MLflow, dataexplorer, prediction, and explorer by using the Virtual Services and Gateways Command Script (GCP).
Check the status of all the core components by running this command:
If any of the components are not in a Running state, see Installation Issues.