The OASF server moved to agntcy/oasf-server, and OASF 0.7.0 is deprecated

[akijakya]

The OASF schema server and its Helm chart now live in their own repository, agntcy/oasf-server. agntcy/oasf keeps the schema, the proto definitions and the docs. A server fix, including a security fix, now ships once as a single server release that every supported schema version uses, instead of being backported and released once per schema version. The rationale and the design decisions are in the RFC discussion.

What changes

Server image. ghcr.io/agntcy/oasf-server is versioned independently of the schema, starting at v2.0.0 (see the changelog). From v2.0.0 on, the image contains no schema: mount one at /app/schema. Without one, the server exits with an error.

Schema images. Every schema version is published as a data-only image, ghcr.io/agntcy/oasf-schema:<schema version> (1.1.0, 1.0.0 and 0.8.0 today), with the schema under /schema. Tags follow the schema version, and future schema releases publish theirs automatically.

docker run --rm -v oasf-schema:/schema ghcr.io/agntcy/oasf-schema:1.1.0 true
docker run --rm -p 8080:8080 -v oasf-schema:/app/schema:ro ghcr.io/agntcy/oasf-server:v2.0.0

Helm chart. The chart moved to oci://ghcr.io/agntcy/oasf-server/helm-charts/oasf, starting at v2.0.0. Chart v2 runs every schema version from one server image, each with its schema mounted from its oasf-schema image, so image.versions is replaced by image.tag and schema.versions. Resource names and URL paths are unchanged, so an existing release upgrades in place:

# Chart v1 (oci://ghcr.io/agntcy/oasf/helm-charts/oasf)
image:
  repository: ghcr.io/agntcy/oasf-server
  versions:
    - server: v1.0.4
      schema: 1.0.0
    - server: v1.1.3
      schema: 1.1.0
      default: true

# Chart v2 (oci://ghcr.io/agntcy/oasf-server/helm-charts/oasf)
image:
  repository: ghcr.io/agntcy/oasf-server
  tag: v2.0.0
schema:
  mount: initContainer # or imageVolume, on Kubernetes 1.35+
  versions:
    - schema: 1.0.0
    - schema: 1.1.0
      default: true

To upgrade the server later, change image.tag; no new chart release is needed. If you deploy with Argo CD or another tool that pins the chart's location, update the chart path as well as the version.

Schema releases. agntcy/oasf no longer has release branches or patch releases. Every release is a new schema version, tagged vX.Y.0 on main, and fixes ship in the next schema version. The existing releases will be consolidated into one release per schema version.

OASF 0.7.0 is deprecated

oasf-server v2 doesn't support schema 0.7.0, and no oasf-schema:0.7.0 image is published. 0.7.0 is no longer served at schema.oasf.outshift.com, and /0.7.0/... returns 404. Please move records to 1.1.0. The oasf-server:v0.7.8 image, which bundles 0.7.0, stays pullable if you need to keep serving it yourself, but it gets no further fixes.

What stays the same

• schema.oasf.outshift.com keeps its URLs for every supported version: /<version>/..., /api/<version>/..., /schema/..., /sample/... and the default-version routes. Only 0.7.0 is gone.
• The bundled ghcr.io/agntcy/oasf-server:vX.Y.Z images up to v1.x, and the v1 charts, stay pullable, but they no longer receive fixes.
• agntcy/oasf keeps its history, tags and links. To preview schema changes locally, task server:up in agntcy/oasf runs the pinned oasf-server release against your schema/ directory.

Where to go

• Server bugs, features and the chart: agntcy/oasf-server issues. Schema changes: agntcy/oasf issues.
• Supported schema versions for each server release: the oasf-server changelog.
• Deploying and running the server: the oasf-server README.

Questions and feedback are welcome in this thread.