DirectorySecurity AdvisoriesPricing
Sign in
Directory
crossplane-function-extra-resources logo

crossplane-function-extra-resources

packaged by Chainguard

Last changed
Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Container for crossplane-function-extra-resources

This composition function retrieves existing cluster resources by name or label selector and adds them to the Crossplane composition pipeline context.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/crossplane-function-extra-resources:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard crossplane-function-extra-resources container image is a drop-in replacement for the upstream function-extra-resources Crossplane package published at xpkg.upbound.io/crossplane-contrib/function-extra-resources. The image ships the function binary together with the Crossplane package metadata and the Input CRD in /package.yaml, so you can reference it directly in a Function resource. Like the upstream image, it uses /function as the entrypoint and runs as the nonroot user with UID 65532.

Prerequisites

You need a Kubernetes cluster with Crossplane v2.0 or later installed. If Crossplane is not installed yet, install it with Helm:

helm repo add crossplane-stable https://charts.crossplane.io/stable
helm repo update
helm install crossplane --namespace crossplane-system --create-namespace crossplane-stable/crossplane

Getting Started

Create a Function resource that points at the Chainguard image:

cat > function.yaml <<EOF
apiVersion: pkg.crossplane.io/v1
kind: Function
metadata:
  name: function-extra-resources
spec:
  package: cgr.dev/ORGANIZATION/crossplane-function-extra-resources:latest
EOF
kubectl apply -f function.yaml

Wait for Crossplane to install the function and report it as healthy:

kubectl wait --for=condition=Healthy function.pkg.crossplane.io/function-extra-resources --timeout=300s

Configuration

function-extra-resources does not change resources itself. It fetches existing resources and places them in the pipeline context under the apiextensions.crossplane.io/extra-resources key, where a later step such as function-go-templating can read them.

The following Composition step selects every EnvironmentConfig labeled type: cluster and stores the matches under the clusters key:

pipeline:
  - step: pull-extra-resources
    functionRef:
      name: function-extra-resources
    input:
      apiVersion: extra-resources.fn.crossplane.io/v1beta1
      kind: Input
      spec:
        extraResources:
          - kind: EnvironmentConfig
            apiVersion: apiextensions.crossplane.io/v1beta1
            into: clusters
            type: Selector
            selector:
              minMatch: 1
              maxMatch: 5
              matchLabels:
                - key: type
                  type: Value
                  value: cluster

Set minMatch so the composition fails fast when a required resource is missing, and maxMatch to bound how many resources the step passes on. To fetch a single resource by name instead, use type: Reference together with ref.name. Matches are sorted by metadata.name unless you set selector.sortByFieldPath.

A downstream go-templating step can then read the selected resources from the context. This step writes their names into the status of an XLookup composite resource:

  - step: render
    functionRef:
      name: function-go-templating
    input:
      apiVersion: gotemplating.fn.crossplane.io/v1beta1
      kind: GoTemplate
      source: Inline
      inline:
        template: |
          {{- $clusters := index (index .context "apiextensions.crossplane.io/extra-resources") "clusters" }}
          apiVersion: example.io/v1alpha1
          kind: XLookup
          status:
            matched: {{ len $clusters }}
            names: "{{ range $i, $c := $clusters }}{{ if $i }},{{ end }}{{ $c.metadata.name }}{{ end }}"

Documentation and Resources

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.

Licenses

Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:

  • MIT

  • MPL-2.0

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

Chainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.

SLSA compliance at Chainguard

This image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.

PCI DSS at Chainguard

A FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.


Related images
crossplane-function-extra-resources-fips logoFIPS

crossplane-function-extra-resources-fips


Category
Application

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.