Description
Deploy translation-rendered workloads to a managed local k3d cluster and an existing remote Kubernetes context. Keep the BYOO collector authentic while using lightweight stand-ins for non-collector containers. Support local collector builds, explicit image selection, image import, resource isolation, cleanup, and provenance recording.
Definition of Done
- Local mode creates and uses a dedicated k3d cluster without conflicting with existing local resources.
- Remote mode uses an existing Kubernetes context without provisioning or modifying the underlying cluster.
- Both modes use an isolated namespace and identifying labels.
- The authentic collector runs in both the container-sidecar and generated Helm utils-pod shapes.
- Local mode can build the collector from source and import the image into k3d.
- Both modes accept an explicit collector image, and remote mode requires a registry-accessible image.
- Results record the exact image and source revision.
- Resources are removed by default, with an option to retain them for debugging.
- Automated tests cover mode selection, image handling, deployment, and cleanup behavior.
Resources
By submitting this issue, you acknowledge that you are an assigned member of the NVCF development team and agree to follow our code of conduct and our contributing guidelines.
Description
Deploy translation-rendered workloads to a managed local k3d cluster and an existing remote Kubernetes context. Keep the BYOO collector authentic while using lightweight stand-ins for non-collector containers. Support local collector builds, explicit image selection, image import, resource isolation, cleanup, and provenance recording.
Definition of Done
Resources
src/compute-plane-services/byoo-otel-collector/By submitting this issue, you acknowledge that you are an assigned member of the NVCF development team and agree to follow our code of conduct and our contributing guidelines.