Skip to content

fix(icms-translate): inject SPOT_ENVIRONMENT into task worker init container#29

Closed
shelleyshen-0 wants to merge 1 commit into
mainfrom
fix/nvbug-6180645-spot-env-injection
Closed

fix(icms-translate): inject SPOT_ENVIRONMENT into task worker init container#29
shelleyshen-0 wants to merge 1 commit into
mainfrom
fix/nvbug-6180645-spot-env-injection

Conversation

@shelleyshen-0
Copy link
Copy Markdown

Summary

Add SpotEnvironment to the task LaunchSpecification type and wire it through to allEnvSet so the worker init container receives SPOT_ENVIRONMENT as a Kubernetes env var.

The field was present in the NATS message payload but absent from the deserialized struct, so SPOT_ENVIRONMENT was never injected and the init container always saw an empty value.

Also adds SpotEnvironmentEnv = "SPOT_ENVIRONMENT" constant to common/env.go to match the pattern used by all adjacent env var assignments.

Note: the function container translate path (translate/function/) has the same gap and needs a follow-up fix.

Testing

Validated end-to-end: SPOT_ENVIRONMENT now appears on the init container and task pods complete successfully.

Related Issues

None

…ntainer

Add SpotEnvironment to task LaunchSpecification and wire it into allEnvSet
so nvcf_worker_init receives SPOT_ENVIRONMENT=ncp and routes ess-init to
the in-cluster ESS. Fixes exit 14 on UPLOAD tasks (NVBug 6180645).

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@shelleyshen-0 shelleyshen-0 requested a review from a team as a code owner May 23, 2026 06:41
@shelleyshen-0 shelleyshen-0 deleted the fix/nvbug-6180645-spot-env-injection branch May 23, 2026 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant