This document describes the infrastructure and the application setup for integrating TDM with AI.
Keep the default values for the rest of the parameters.
kubectl config current-context # Check the kubectl is connected to your cluster
kubectl get ns # Check that you can see the namespaces of the cluster
An admin token enables Fabric to interact with the Kubernetes API server using an HTTP/HTTPS interface.
apiVersion: v1
kind: ServiceAccount
metadata:
name: full-admin-user
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: full-admin-user
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: full-admin-user
namespace: kube-system
---
apiVersion: v1
kind: Secret
type: kubernetes.io/service-account-token
metadata:
name: full-admin-user-secret
namespace: kube-system
annotations:
kubernetes.io/service-account.name: full-admin-user
kubectl apply -f admin-user.yaml
token=$(kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep "full-admin-user-secret" | awk '{print $1}')| grep token: |awk '{print $2}')
echo $token
# Alternative way to see the token
kubectl describe secrets/full-admin-user-secret -n kube-system
Click here for TDM-AI project implementation guidelines.
The cleanup process, AICleanUp.flow, is located under the TDM LU with the inputs CleanALL (boolean data type), and TrainingExecutionIDs (array data type). If CleanALL is true, the flow deletes all the data in the AI_execution and AI_DB, else you shall populate TrainingExecutionIDs. For example, if you have 2 training models that hold the IDs 1551,1660, you should pass them to the flow as [1551,1660]. The flow extracts all generations done by these training models and deletes all their related data.
AI Training Results:
AI Generation Results:
This document describes the infrastructure and the application setup for integrating TDM with AI.
Keep the default values for the rest of the parameters.
kubectl config current-context # Check the kubectl is connected to your cluster
kubectl get ns # Check that you can see the namespaces of the cluster
An admin token enables Fabric to interact with the Kubernetes API server using an HTTP/HTTPS interface.
apiVersion: v1
kind: ServiceAccount
metadata:
name: full-admin-user
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: full-admin-user
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: full-admin-user
namespace: kube-system
---
apiVersion: v1
kind: Secret
type: kubernetes.io/service-account-token
metadata:
name: full-admin-user-secret
namespace: kube-system
annotations:
kubernetes.io/service-account.name: full-admin-user
kubectl apply -f admin-user.yaml
token=$(kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep "full-admin-user-secret" | awk '{print $1}')| grep token: |awk '{print $2}')
echo $token
# Alternative way to see the token
kubectl describe secrets/full-admin-user-secret -n kube-system
Click here for TDM-AI project implementation guidelines.
The cleanup process, AICleanUp.flow, is located under the TDM LU with the inputs CleanALL (boolean data type), and TrainingExecutionIDs (array data type). If CleanALL is true, the flow deletes all the data in the AI_execution and AI_DB, else you shall populate TrainingExecutionIDs. For example, if you have 2 training models that hold the IDs 1551,1660, you should pass them to the flow as [1551,1660]. The flow extracts all generations done by these training models and deletes all their related data.
AI Training Results:
AI Generation Results: