Steps

Author a crossplane.yaml manifest in the package root (apiVersion: meta.pkg.crossplane.io/v1, kind: Configuration) listing required Providers/Functions under spec.dependsOn with apiVersion, package, and a version constraint (e.g. ">=v0.36.0").
Place the Configuration's CompositeResourceDefinition and Composition YAML files alongside crossplane.yaml in the package root.
Build the package with `crossplane xpkg build --package-root=<dir>` (add -o/--package-file to name the output .xpkg), producing a local OCI-image-format package artifact.
Authenticate to the target OCI registry if required, e.g. `docker login <REGISTRY>`.
Push the built package with `crossplane xpkg push -f <path/to/package>.xpkg <REGISTRY>/<REPO>:<TAG>`, using a fully-qualified registry/repo:tag destination.
Verify the publish by installing it on a test cluster with a Configuration resource (apiVersion: pkg.crossplane.io/v1, kind: Configuration, spec.package: <REGISTRY>/<REPO>:<TAG>) and confirming it reaches INSTALLED: True, HEALTHY: True.

Known gotchas

Since Crossplane v1.20 the CLI's default package registry changed from index.docker.io to xpkg.crossplane.io, so omitting a registry host in push/install commands from older tutorials resolves to a different registry than expected.
xpkg push requires the fully-qualified <registry>/<repo>:<tag> destination as a separate argument from -f; leaving off the tag or registry host can silently push to an unintended location or the default registry.
spec.dependsOn version constraints are resolved when the Configuration is installed, not when it's built — a loose or missing constraint can pull in a newer, incompatible Provider or Function version long after the Configuration package itself was published.

Implement Crossplane ProviderConfig with selector-based references for multi-account AWS access without hardcoding account IDs in Compositions

docs.crossplane.io · 6 steps · unrated

Configure Crossplane ProviderConfig for multi-account AWS access using IAM role assumption per composite resource with selector-based config references

crossplane.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Package and publish a Crossplane Configuration package to an OCI registry

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?