crossplane-provider-nop

packaged by Chainguard

Chainguard Container for crossplane-provider-nop

This image contains the Crossplane NOP provider, a no-op provider that simulates managed resources without touching any external system, for testing Crossplane installations.

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-provider-nop: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-provider-nop container image is a replacement for the upstream xpkg.upbound.io/crossplane-contrib/provider-nop package. It is built from source with Go and is licensed under the Apache License 2.0.

Provider NOP is a no-operation Crossplane provider. It exposes the NopResource and ClusterNopResource managed resources, which simulate readiness, connection details, and deletion behavior without touching any external system. This makes it useful for testing Crossplane installations, compositions, and controllers.

The image runs as the nonroot user (UID 65532) by default, uses /home/nonroot as its working directory, and starts the provider-nop binary as its entrypoint. Like the upstream package, the image includes the Crossplane package metadata at /package.yaml.

Getting Started Guide

Install Crossplane

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

Install the Provider

Deploy the Provider to your cluster:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-nop
spec:
  package: cgr.dev/ORGANIZATION/crossplane-provider-nop:latest

Apply this configuration:

kubectl apply -f provider.yaml

Verify the provider is installed and healthy:

kubectl get providers

Create a NOP Resource

Once the provider is healthy, create a resource that becomes Ready shortly after creation:

apiVersion: nop.crossplane.io/v1alpha1
kind: NopResource
metadata:
  name: example
  namespace: default
spec:
  forProvider:
    conditionAfter:
      - conditionType: Ready
        conditionStatus: "True"
        time: 10s
    fields:
      coolField: example-value

Check the resource status:

kubectl get nopresources

Documentation and Resources

• Crossplane Getting Started Guide
• Provider NOP Repository
• Provider NOP Examples

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:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

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.