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

chore: sync local changes

Browse Source
This commit is contained in:
jackyliu
2026-06-16 01:11:46 +00:00
parent 29056822f9
commit cbea46632e
8 changed files with 40 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
AGENTS.md
View File

@ -7,11 +7,11 @@ This file is the execution guide for `ocdp-workload-manifests`.
- Treat this project as a plain app manifests repository.
- Do not store OCDP WorkloadTemplate records here; they belong in `ocdp-server`
PostgreSQL.
- Do not store user WorkloadClaim instances here; they belong in target-cluster
- Do not store user Workload instances here; they belong in target-cluster
CRs created through `ocdp-server`.
- Keep reusable Kubernetes resources under `apps/*/base`.
- Keep optional Kustomize components under `apps/*/components`.
- Keep Helm post-render presets under `packages/*/presets/*`.
- Keep Helm post-renders under `packages/*/post-renders/*`.
- Keep per-deployment runtime values out of this repository. They belong in
temporary source files or runtime specs generated by `ocdp-server`.
- Use `tests/kustomize/*` only for generic validation overlays, never for real
@ -23,19 +23,19 @@ This file is the execution guide for `ocdp-workload-manifests`.
- Do not add a global catalog index unless the server explicitly needs one later.
- `ocdp-server` WorkloadTemplate records may reference Helm charts plus
`source.preset.repositoryUrl/ref/path`.
`source.postRender.repositoryUrl/ref/path`.
- Runtime source generation may render Helm, create Secret, ConfigMap, and patch
files, then run Kustomize.
- Bases should stay template-free YAML.
- App bases should keep Services internally reachable; expose apps from
WorkloadClaim top-level intent such as `exposure=internal` or
Workload 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 should be assigned per claim by Kubernetes, not hard-coded in
- NodePort numbers should be assigned per workload by Kubernetes, not hard-coded in
reusable app bases or components.
## Validation