OCDP/ocdp-workload-manifests
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update workload runtime integration

Browse Source
This commit is contained in:
jackyliu
2026-06-02 09:48:58 +00:00
parent 80a063a167
commit cb6cf58229
11 changed files with 45 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
AGENTS.md
View File

@ -26,14 +26,15 @@ This file is the execution guide for `ocdp-workload-manifests`.
- Runtime source generation may create Secret, ConfigMap, and patch files, then
run Kustomize.
- Bases should stay template-free YAML.
- App bases should keep Services as `ClusterIP`; expose apps from
WorkloadTemplate values such as `exposure=nodeport` or `exposure=loadbalancer`.
- App bases should keep Services internally reachable; expose apps from
WorkloadClaim top-level intent such as `exposure=internal` or
`exposure=external`, rendered by the agent/template path.
Components such as `service-nodeport`, `service-loadbalancer`, or `ingress`
are implementation building blocks, not the user-facing contract.
- Environment overlays are platform/admin choices for cluster- or site-level
differences such as StorageClass, IngressClass, GPU runtime, registry prefix,
pull secrets, node selectors, tolerations, and site labels.
- NodePort numbers belong in per-claim values handled by `ocdp-server`, not in
- NodePort numbers should be assigned per claim by Kubernetes, not hard-coded in
reusable app bases or components.
## Validation