agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/compute-plane-services/image-credential-helper/AGENTS.md

nvcf / image-credential-helper

AGENTS.md261 starsChanged 9 days agoApache-2.0View on GitHub

Native Go service for Kubernetes image pull credential management in NVCF bring-your-own-compute clusters. - cmd/image-credential-helper/: main binary entrypoint - vendor/github.com/dsx-ai-factory/nvcf/src/libraries/go/lib/pkg/imagecredential/: vendored shared registry credential logic - examples/: sample Kubernetes manifests - docker/: local Dockerfile Registry-provider logic is owned in the monorepo shared library at src/libraries/go/lib/pkg/imagecredential. Make provider changes there first, then update this subtree's module/vendor state. Useful focused checks: CI subproject id: image-credential-helper. Follow the root RELEASE.md and docs/dev/github-release-process.md for source versioning and publication handoffs. Inspect .github/workflows/ for current public…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 1 is common, 0 are distinctive, and 0 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Common:

    Never commit real registry credentials or kubeconfigs.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md - image-credential-helper

Native Go service for Kubernetes image pull credential management in NVCF bring-your-own-compute clusters.

Layout

  • cmd/image-credential-helper/: main binary entrypoint
  • vendor/github.com/dsx-ai-factory/nvcf/src/libraries/go/lib/pkg/imagecredential/: vendored shared registry credential logic
  • examples/: sample Kubernetes manifests
  • docker/: local Dockerfile

Registry-provider logic is owned in the monorepo shared library at src/libraries/go/lib/pkg/imagecredential. Make provider changes there first, then update this subtree's module/vendor state.

Build and Test

make build
make test
make lint
make vendor-update

Useful focused checks:

go test ./cmd/image-credential-helper
go test ./cmd/image-credential-helper -run Test_runGlobal
make shellcheck

CI subproject id: image-credential-helper. Follow the root RELEASE.md and docs/dev/github-release-process.md for source versioning and publication handoffs. Inspect .github/workflows/ for current public validation.

Local Gotchas

  • Dependency changes require make vendor-update, then root license attribution refresh via ./tools/scripts/update-license.
  • AWS ECR private registries match *.dkr.ecr.*.amazonaws.com.
  • AWS ECR Public uses public.ecr.aws and is treated as public.
  • Volcengine regions are parsed from *.cr.volces.com hostnames.
  • Pull secret names follow workload-{id}-regcred-{index} or worker-{id}-regcred-{index}.
  • Never commit real registry credentials or kubeconfigs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free