Skip to content

[Release] Publish multi-architecture UI image with SBOM and provenance #110

Closed

Description

@mohit-nagaraj

Context

The current UI release workflow on main publishes only linux/amd64 and explicitly disables provenance. The currently published ghcr.io/kubeorch/ui:v0.0.3 index was inspected on August 30, 2026 and contains a linux/amd64 image manifest but no linux/arm64 image manifest.

The production image also has no release smoke test proving that the browser receives the Core API URL supplied by the supported runtime. UI client code reads NEXT_PUBLIC_API_URL, while the CLI-generated production Compose file currently supplies that value to the running container. KubeOrch/cli#47 remains open until an ARM64-capable UI image and a working browser-to-Core contract are demonstrated.

Outcome

A versioned UI release publishes one OCI image index for linux/amd64 and linux/arm64, serves the standalone application correctly on both platforms, honors the documented browser API URL contract, and includes verifiable, digest-bound SBOM and provenance evidence.

Scope

  • Build and publish linux/amd64 and linux/arm64 UI image manifests under one versioned OCI index.
  • Validate that architecture-specific Node and frontend dependencies build and run on both targets.
  • Define and verify one production browser API URL contract compatible with CLI-generated Compose.
  • Generate SBOM and build-provenance attestations bound to the released image digest.
  • Preserve the current non-root standalone runtime and health endpoint behavior.
  • Add platform and browser-to-Core smoke coverage to the release path.
  • Expose the release index digest and verification guidance in the GitHub Release.

Out Of Scope

  • Redesigning the UI or changing unrelated frontend behavior.
  • Publishing the Core image.
  • Reworking CLI project discovery or local source-development mode.
  • Defining the cross-repository compatibility manifest.

Acceptance Criteria

  • The versioned image index contains runnable linux/amd64 and linux/arm64 image manifests.
  • The standalone Next.js server starts as the existing non-root user and passes its health check on both platforms.
  • A production browser session uses the configured Core API base URL; it does not depend on an accidental build-machine or localhost default.
  • SBOM evidence is retrievable and resolves to the released image digest.
  • Provenance identifies the source repository, source commit, and release workflow and resolves to the released image digest.
  • A failed platform build, health check, browser API smoke, or evidence verification prevents successful release promotion.
  • Existing AMD64 installations remain compatible.

Verification

  • CI builds the Dockerfile for both target platforms.
  • Automated manifest inspection asserts both required platform manifests.
  • Automated container health tests cover AMD64 and ARM64.
  • A disposable browser-to-Core smoke test verifies the configured API route from the released container.
  • Automated verification checks the SBOM and provenance against the published digest.
  • The release notes record the immutable index digest and supported platforms.

Dependencies

No implementation dependency. This issue blocks the cross-architecture CLI and Community install smoke gate and completion of KubeOrch/cli#47.

Documentation And Observability

Document supported architectures, the production API URL contract, digest and attestation verification, and release failure diagnosis. Release logs must identify the failing platform or smoke step without exposing credentials.

Activity

  1. added
    area/uiNext.js frontend (components, pages, styling)
    sprint/currentCurrently active sprint items
    kind/infraProject skeleton, environment setup
    size/mMedium task (1-2 days)
    on Aug 30, 2026
  2. mohit-nagaraj commented on Sep 1, 2026

    @mohit-nagaraj
    MemberAuthor

    /assign

  3. github-actions commented on Sep 1, 2026

    @github-actions

    ✅ Issue assigned to @mohit-nagaraj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/uiNext.js frontend (components, pages, styling)kind/infraProject skeleton, environment setuppriority/criticalMust be done firstsize/mMedium task (1-2 days)sprint/currentCurrently active sprint items

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions