Training and serving need three kinds of tool images.

KindWhat it does
Training runtimeThe training container itself. There is a separate one per framework (YOLO, RF-DETR, Pointcept and so on)
Dataset stagerAn init container that places the dataset inside the training pod before the pod starts
Serving builderA builder that bakes a registered model into a serving image

Baking these images separately for each tenant repeats the same work many times. Shared images are baked once, pushed to the reserved namespace (mlops), and handed out only to the tenants you choose. A tenant that has not been given a shared image can neither see nor pull it.

Shared images

From top to bottom the screen has three parts.

  1. Per-tenant defaults (테넌트별 기본) — collects the tenants and slots (kind and framework) whose default image is empty. Pressing "Fill … (… 채우기)" opens the share-targets dialog of the shared variant to use for that slot directly.
  2. Kind tabs and the shared variant listTraining runtime (학습 런타임) / Dataset stager (데이터셋 스테이저) / Serving builder (서빙 빌더).
  3. Reserved repository (예약 저장소) — a summary of the images actually pushed to the reserved namespace (read-only).

Create and bake a shared variant

  1. Choose a kind tab and press Add shared variant (공유 변형 추가).
  2. Enter the framework (for a training runtime), name, tag, description and build-args, then press Create (만들기). If you leave the build-args empty, the Dockerfile defaults are used.
    Create a shared variant
  3. Press Publish (게시) in the list to bake the image in the cluster. The publish column changes from Publishing (게시 중) to Published (게시됨). While it is in progress you can stop it with Stop (중지).

Hand out to tenants

  1. Press Share targets (공유 대상) on the variant row.
  2. Check the tenants to hand it to, and also check Default (기본) if that tenant should use it as its default.
    Share targets — share and default per tenant
  3. Press Save (저장).
  • The list is replaced as a whole. Sharing is revoked from tenants you uncheck. If a tenant being revoked was using this variant as its default, you are asked to confirm once more before saving.
  • Turning on Default (기본) clears that tenant's existing default (whether its own variant or another shared variant).
  • Tenant administrators see shared variants in their own variant list with a "Shared (공유)" badge, and can only set them as default. Editing, deleting and publishing are done only in the system console.

Written for the platform as of 2026-09-21.

© Geo-MLOps