Creating Packages

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

Overview

This guide walks through the full lifecycle of a PackageRevision managed by the PR Controller: creating a package, pushing content, observing rendering, and publishing.

All operations use standard kubectl commands against the PackageRevision CRD (porch.kpt.dev/v1alpha2).

Create a Package (Init)

Create a new package by applying a PackageRevision with spec.source.init:

apiVersion: porch.kpt.dev/v1alpha2
kind: PackageRevision
metadata:
 name: my-repo-my-package-v1
 namespace: default
spec:
 repository: my-repo
 packageName: my-package
 workspaceName: v1
 lifecycle: Draft
 source:
 init:
 description: "My first CRD-based package"
 keywords:
 - example

kubectl apply -f packagerevision.yaml

The CRD is created immediately in etcd. The PR Controller picks it up and executes the init source operation in the background.

User-Facing Differences

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

Overview

This page describes the user-visible differences between the aggregated API architecture and the CRD-based controller architecture. If you have been using the aggregated API (porch.kpt.dev/v1alpha1), this is what changes in your workflow.

API Group and Version

	Aggregated API	CRD-based
API resource	Aggregated API (custom REST storage)	Native CRD in etcd
apiVersion	`porch.kpt.dev/v1alpha1`	`porch.kpt.dev/v1alpha2`
PackageRevisionResources	Same (`porch.kpt.dev/v1alpha1`)	Same (unchanged)

The two API versions are independent. There is no conversion webhook between them. A PackageRevision created via the aggregated API is not automatically visible as a CRD (and vice versa).

Working with CRD-Based PackageRevisions on Porch Documentation

Creating Packages

Overview

Create a Package (Init)

User-Facing Differences

Overview

API Group and Version