Application Marketplace on Cozystack

Publishing a Repository

Mon, 01 Jan 0001 00:00:00 +0000

This guide is for publishers: developers who package applications and make them available to Cozystack clusters. It covers scaffolding a repository, validating it offline, pushing it as an OCI artifact, and, optionally, listing it in the community index.

For the operator side (connecting a published repository to a cluster), see Connecting a Repository.

Prerequisites

The cozypkg CLI. It ships with Cozystack releases; see the cozypkg Reference.
The flux CLI, which cozypkg push uses to build and push the OCI artifact.
Access to an OCI registry you can push to (for example GitHub Container Registry).
helm on your PATH if you want --helm-lint to run helm lint on the charts.

Scaffold a repository

cozypkg init writes a complete repository skeleton that passes validation as-is:

Connecting a Repository

Mon, 01 Jan 0001 00:00:00 +0000

This guide is for operators: cluster administrators who connect external repositories and install their applications. It covers discovering repositories, connecting them from the CLI or the dashboard, installing applications, and disconnecting.

For the publisher side (packaging and pushing a repository), see Publishing a Repository.

Prerequisites

The cozypkg CLI and a kubeconfig for the target cluster. Creating cluster-scoped resources requires cluster-admin.
Cozystack with the marketplace enabled on the management cluster.

Warning: Connecting a repository runs its charts in your management cluster. Connect only sources you trust, or repositories listed in a curated index whose gate verifies signatures. See the Trust model.

Discover repositories

cozypkg search queries the community index and lists matching repositories without connecting them. Point it at an index with --index or the COZYPKG_INDEX environment variable (a local directory or an oci:// reference):

cozypkg Reference

Mon, 01 Jan 0001 00:00:00 +0000

cozypkg is the CLI for authoring, publishing, and managing Cozystack marketplace repositories. This page is a reference for its commands; for task-oriented walkthroughs see Publishing a Repository and Connecting a Repository.

Commands that create or read cluster resources accept --kubeconfig and otherwise fall back to ~/.kube/config or the KUBECONFIG environment variable. Creating cluster-scoped resources requires cluster-admin.

Environment variables

COZYPKG_INDEX: default index location for search and short-name tap. A local directory or an oci:// reference. Overridden by --index.

Authoring and publishing

`cozypkg init [directory]`

Scaffold a new repository built around the PackageSource model: a PackageSource with one variant and a paired app / -rd component, ready to validate and push. The generated tree passes cozypkg validate as-is.