Creating Kubernetes Assets in Advance¶
The article describe how to mark Kubernetes assets for use by Run:ai
Creating PVCs in advance¶
Add PVCs in advance to be used when creating a PVC-type data source via the Run:ai UI.
Follow the steps below for each required scope:
Cluster scope¶
- Locate the PVC in the Run:ai namespace (runai)
- To authorize Run:ai to use the PVC, label it:
run.ai/cluster-wide: "true”
The PVC is now displayed for that scope in the list of existing PVCs.
Department scope¶
- Locate the PVC in the Run:ai namespace (runai)
- To authorize Run:ai to use the PVC, label it:
run.ai/department: "id"
The PVC is now displayed for that scope in the list of existing PVCs.
Project scope¶
- Locate the PVC in the project’s namespace
The PVC is now displayed for that scope in the list of existing PVCs.
Creating ConfigMaps in advance¶
Add ConfigMaps in advance to be used when creating a ConfigMap-type data source via the Run:ai UI.
Cluster scope¶
- Locate the ConfigMap in the Run:ai namespace (runai)
- To authorize Run:ai to use the ConfigMap, label it:
run.ai/cluster-wide: "true”
-
The ConfigMap must have a label of
run.ai/resource: <resource-name>
The ConfigMap is now displayed for that scope in the list of existing ConfigMaps.
Department scope¶
- Locate the ConfigMap in the Run:ai namespace (runai)
- To authorize Run:ai to use the ConfigMap, label it:
run.ai/department: "<department-id>"
-
The ConfigMap must have a label of
run.ai/resource: <resource-name>
The ConfigMap is now displayed for that scope in the list of existing ConfigMaps.
Project scope¶
- Locate the ConfigMap in the project’s namespace
-
The ConfigMap must have a label of
run.ai/resource: <resource-name>
The ConfigMap is now displayed for that scope in the list of existing ConfigMaps.