Publishing to Upbound Registry

Requirements

This guide works best if you've worked through the build a configuration guide already. You'll need the Docker CLI installed to authenticate, and the Upbound CLI installed to build and push Crossplane packages.

Build a Crossplane Package

Both Providers and Configurations can be built into a Crossplane Package that can be pushed to Upbound Cloud. Follow the build a configuration guide to build a getting-started.xpkg file that you can push to the Upbound Registry. The .xpkg file is your Crossplane Configuration package which can be uploaded to the Upbound Registry.

Create a Repository in Upbound Cloud

Next, before we build the repository we just published, you'll need to create a new Repository in Upbound Cloud. Your repositories will show up in Upbound Registry, an OCI distribution conformant registry, as listings once you push a package to your Repository.

Push to Your Repository

Once you've created your Repository, all you have to do is push the package to it with the following commands.

The Upbound Cloud CLI uses the Docker configuration to authenticate to the Upbound Registry by default, so you'll have to login via the Docker CLI before pushing.

# Your Upbound Cloud Email Address
UBC_EMAIL=jane@example.org
docker login registry.upbound.io -u ${UBC_EMAIL}
# Push the getting started package
UBC_ACCOUNT=exampleorg
UBC_REPO=examplerepo
VERSION_TAG=v0.0.1
up xpkg push ${UBC_ACCOUNT}/${UBC_REPO}:${VERSION_TAG} -f getting-started.xpkg