Skip to main content
Each deploy records an immutable version. Bump the version, redeploy, and you can roll back to an earlier one without rebuilding.

​
Version on deploy

The version field in AgentCard.json is the image tag — the deployed image is name:version. Pass -v to set it on the command, or -y to accept the suggested version without a prompt.
Agent names are unique per cluster. Deploying the same name creates a new version on that agent. Re-pushing a version that is already in use is rejected.

​
History, reupload, rollback

API: GET /api/agents/{id}/versions, POST /api/agents/{id}/rollback, PUT /api/agents/{id}/update (reupload), DELETE /api/agents/{id}/versions/{version}. nasiko restart recreates the container from the current image and secrets. It does not change versions. Use rollback to change which version is current.

​
Registry artifacts (Enterprise)

Enterprise. This section describes the standalone artifact registry (nasiko-ee), not the built-in image registry at /v2/*. Open-source clusters keep images in that embedded registry; they do not host publish/yank.
Each publish creates a new version row under that artifact’s name. Versions are free-text, not enforced semver. “Latest” means most recently published and non-yanked. Every version starts at preview. An administrator can label it stable or verified — display only. Yanking hides a version from browse, list, and search. Anyone who pinned owner/name/version can still fetch it.
See Registry.

​
Next

Deploy an agent

Push, upload, import.

Operate agents

Logs, scale, writable storage.