Official Providers

    Upbound creates, maintains and supports a set of Crossplane providers called official providers.

    Find official providers

    Identify official providers in the marketplace with the by Upbound gold seal.

    example official provider with a by Upbound seal
    example official provider with a by Upbound seal

    Also find official providers by filtering a search in the marketplace to just Official.

    a marketplace search filter with Providers and Official filters set
    a marketplace search filter with Providers and Official filters set

    Install an official provider

    The Upbound Marketplace hosts official providers.

    Install the provider resource

    Install a provider with the creating a Provider Kubernetes resource with the Up command-line or manually.

    Install the provider directly into Kubernetes using the Up command-line.
    Provide the package source of the provider to install. This example installs the AWS official provider version 0.17.0.

    1
2
3

    up controlplane \
provider install \
xpkg.upbound.io/upbound/provider-aws:v0.17.0

    Create a kind: Provider Kubernetes manifest.

    Provide the spec.package location of the official provider from the Upbound Marketplace listing.

    This example installs the AWS official provider version 0.17.0.

    1
2
3
4
5
6
7
8

    apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
    name: provider-aws
spec:
  package: xpkg.upbound.io/upbound/provider-aws:v0.17.0
  packagePullSecrets:
    - name: package-pull-secret

    Find provider specific instructions and configurations in their individual documentation pages within the Upbound Marketplace.

    Versions and releases

    Official providers have two relevant release numbers:

    • Provider release, for example, provider-aws:v0.17.0
    • Custom Resource Definition (CRD) API version, for example v1beta1

    Provider releases

    Upbound releases new providers to provide bug fixes and enhancements. Provider versions follow standard semantic versioning (semver) standards of <major>.<minor>.<patch> numbering.

    Major version changes have significant changes to provider behavior or breaking changes to general availability CRD APIs.

    Minor version changes expand provider capabilities or create breaking changes to alpha or beta CRD APIs. Minor versions never change general availability CRD APIs.

    Patch version changes are bug fixes. Provider capabilities and CRD APIs aren’t changed between patch versions.

    Support

    Official providers are available to all paid Upbound customers. Support for official providers follows the same support model for other Upbound components.

    More information is available on the support page.