Skip to content

Conversation

@jojimt
Copy link
Contributor

@jojimt jojimt commented Jan 27, 2026

Description

Some of the operands viz. cc-manager and sandbox device plugin have their commands hardcoded. This causes problems, e.g. when we move to python or make a command name change for any reason. Instead, we want to let the Dockerfile specify the entrypoint.

Checklist

  • No secrets, sensitive information, or unrelated changes
  • Lint checks passing (make lint)
  • Generated assets in-sync (make validate-generated-assets)
  • Go mod artifacts in-sync (make validate-modules)
  • Test cases are added for new code paths

Testing

Manual testing on a cluster. Verified preStop lifecycle hook as well.

Signed-off-by: Joji Mekkattuparamban <jojim@nvidia.com>
@copy-pr-bot
Copy link

copy-pr-bot bot commented Jan 27, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@jojimt
Copy link
Contributor Author

jojimt commented Jan 27, 2026

@rajatchopra @cdesiniotis @zvonkok fyi

@cdesiniotis
Copy link
Contributor

/ok to test fbcc05a

@jojimt jojimt changed the title fix: eliminate hardcoded command names fix: eliminate hardcoded command names [DO NOT MERGE] Jan 28, 2026
@jojimt jojimt changed the title fix: eliminate hardcoded command names [DO NOT MERGE] fix: eliminate hardcoded command names Jan 28, 2026
@rajatchopra
Copy link
Contributor

LGTM. Thanks Joji.

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.

3 participants