Running Crossplane?

Crossplane compositions stuck or providers unreachable? We ship it properly.

Crossplane turns Kubernetes into a multi-cloud control plane, which is powerful and occasionally baffling. A composition that renders fine locally fails inside the cluster because the ProviderConfig name does not match; a managed resource shows Synced=False with a terse ReconcileError and no hint about the IAM policy that is missing. We trace it from the XR to the provider log and stop the Not-Ready backlog from growing.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

crossplane-provider.log

still failing

What it is

Crossplane at a glance

Crossplane is a Kubernetes-native control plane that extends the API with custom resources for cloud infrastructure. Providers for AWS, Azure, GCP and many other systems expose managed resources (databases, queues, buckets, networks) as Kubernetes objects, and Compositions bundle those resources into higher-level offerings a platform team can publish.

The project is a Cloud Native Computing Foundation incubating project under the Apache 2.0 licence, with Upbound offering commercial support and a hosted control-plane service. Typical uses include internal developer platforms, multi-cloud estates that want one API surface, and teams moving from Terraform runs to a continuously reconciled control plane.

Type
Kubernetes-based control plane for cloud infrastructure
First released
2018
License
Apache 2.0
Maintained by
The Crossplane community and Upbound, under the CNCF
Typically used for
Internal developer platforms, multi-cloud provisioning, declarative infrastructure through Kubernetes

The honest version

Crossplane pros and cons

No technology is all upside. This is where Crossplane earns its place and where it tends to cause trouble.

Where Crossplane is strong

  • Infrastructure as Kubernetes objectsManaged resources and composite resources live alongside your workloads in the same cluster, which means RBAC, GitOps and observability tools already in use cover infrastructure too.
  • Compositions let a platform team publish offeringsA developer can request a Database claim and get an RDS instance, a Kubernetes service, an IAM role and a secret in one request, which is a real improvement over a ticket queue.
  • Continuous reconciliationDrift that a human introduced outside the control plane is corrected on the next reconcile, which keeps the declared state honest rather than relying on an occasional Terraform run.
  • Multi-cloud through one APIProviders for all major clouds, plus Helm, Kubernetes, SQL and more, mean one surface covers mixed estates instead of three different tools and languages.
  • Composition Functions extend renderingProgrammable composition through Go, Python or KCL lets complex rendering live in code rather than in YAML gymnastics, which clears up the worst templating pain.
  • GitOps-shaped out of the boxArgo CD or Flux can drive Crossplane manifests alongside workloads, which keeps the operating model consistent for teams already doing GitOps.

Where Crossplane bites

  • The learning curve is steepXRDs, XRCs, XRs, Compositions, Providers and ProviderConfigs are many moving parts, and the vocabulary alone slows new engineers for weeks before anything feels familiar.
  • Error messages are often terseA broken ProviderConfig reference, a missing IAM permission or a schema mismatch all surface as short reconcile errors, and the real cause lives in the provider pod log rather than the CRD.
  • Upgrades across majors need careThe move from v1 to v2 reshaped how namespaced resources and ProviderConfigs work, and teams that upgraded without rehearsing hit server-side apply schema errors in production.
  • Compositions can become a second codebaseWhat starts as one Database XR grows into a library of compositions with their own tests and reviews, which is real engineering work that platform teams sometimes underestimate.
  • Provider pods are heavyRunning providers for every cloud and service you use adds CPU, memory and restart risk, and an OOMKilled provider can leave reconciles stuck longer than operators expect.
  • Terraform is still better at some thingsOne-shot provisioning, drift detection on resources you did not create, and a very wide module ecosystem are places where Terraform has not yet been equalled, and insisting on Crossplane for them costs weeks.

Sound familiar?

Common Crossplane problems we fix

The Crossplane problems that bring people to us, and what you have once each one is fixed.

ProviderConfig 'default' not found

Managed resources cannot find a ProviderConfig

A resource that references ProviderConfigRef.name 'default' when no ProviderConfig with that name has been created, or a Composition that hard-coded the name across environments.

ProviderConfig reference resolved for every environment

ReconcileError: AccessDenied

Provider cannot reach the cloud API

IAM credentials in the ProviderConfig that lack the policy a managed resource needs, with the reconcile loop hammering the API and never succeeding until the policy is widened.

IAM policy aligned with resource needs

XRD validation failed

A new XRD will not install

A composite resource definition that omits required schema fields, uses an incompatible OpenAPI construct, or conflicts with an existing claim, so the API server rejects it and the whole offering is unavailable.

XRD schema accepted and installed

composition render failed

Compositions render differently in cluster than in CI

Templating that depended on context only available at runtime, a Composition Function image that cannot pull, or a patchset that collides with server-side apply, so claims hang without producing resources.

Composition rendering deterministic

field 'namespace' not declared in schema

Server-side apply refuses a field

A composition that writes a field to a ProviderConfig v1beta2 that the schema does not know about, which the server-side apply path rejects and the reconcile cannot complete.

Composition and schema reconciled

provider pod OOMKilled

Providers are crash-looping

A provider pod running out of memory because the cluster has thousands of managed resources, or because a hot resource is being reconciled too aggressively, with reconciles backing up and newer claims stalling.

Provider resourced and tuned for the load

composite resource references not updated

A composition change does not reach existing XRs

Editing a composition and expecting older XRs to inherit the change, when in fact the revision is pinned, so new behaviour only appears on new claims unless the policy is updated.

Composition updates propagated intentionally

What we do

Crossplane help, from rescue to a working platform

Reach out for one managed resource stuck Not Ready, or hand over the whole control plane and the compositions on top.

Rescue
Providers crash-looping, XRDs that will not install, or claims that never become Ready. We walk the CRD tree, the provider logs and the cloud API until the reconcile completes.
Composition design
XRDs, Compositions and Composition Functions laid out so a developer can request a database or a service and get something sensible, with tests that prove it still works after a change.
Provider and credential hygiene
ProviderConfigs scoped per account, credentials rotated on a schedule, and policies tightened down to what resources actually need.
GitOps integration
Argo CD or Flux driving Crossplane manifests, with sync waves that install XRDs before compositions and compositions before claims, so a cold start does not race itself.
Migration from Terraform
Moving pieces of an estate off Terraform onto Crossplane without losing state, with a honest split between what belongs under continuous reconciliation and what is better left one-shot.
Managed Tech
Provider upgrades on a schedule, composition reviews each quarter, drift reports, and an engineer available when a provider starts crash-looping unexpectedly.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Crossplane alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Crossplane questions

Something else? Call+1 737 727 7327

Should we use Crossplane or Terraform?

Crossplane earns its keep when you want a control plane, offerings for developers to claim, and continuous reconciliation. Terraform is still ahead for one-shot provisioning, large module ecosystems and drift on resources you did not create. Many teams keep both, each for what it does best, and we will tell you plainly which pieces fit where.

Why is our claim stuck Not Ready?

Usually the provider cannot talk to the cloud API, a managed resource inside the composition is failing its own reconcile, or a reference to a ProviderConfig or secret is wrong. The composite resource status and the provider pod log together name the culprit within minutes once you know where to look.

How do Compositions version and roll out?

Each composition has revisions, and the CompositionRevisionPolicy on an XR decides whether existing claims pick up new revisions automatically or stay pinned. For platform offerings we usually recommend pinned revisions in production and manual promotion, which keeps changes auditable.

Can we run Crossplane across multiple clouds?

Yes, that is one of its strongest cases. Install providers for each cloud, configure ProviderConfigs per account, and compose higher-level resources that span them. The caveat is that a composition reaching into three clouds is three times the ways to fail, so the test discipline matters.

How much does Crossplane help cost?

The quote is at no cost to you. Tell us the scope of the control plane and what is misbehaving, and we return a price before any work is started.

Free estimate

Crossplane giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.