Crossplane project

Next week on Cloud Native Live, we're exploring declarative infrastructure with Crossplane and Modeplane. Join us to see how platform teams standardize model workflows in production using open source patterns—and bring your questions for the live practitioner Q&A. 🛠️ RSVP to tune in live: https://bit.ly/4B6no4E #Crossplane #CloudNative #Kubernetes #OpenSource

Crossplane users have spent years putting cloud infrastructure behind an API. Now more of you are being asked to run AI inference too. 👀 The same control plane patterns apply, and the community is already building there. Modelplane, for one, runs GPU fleets for model inference entirely on Crossplane compositions and functions, with fixes sent back upstream along the way. Crossplane maintainer Nic Cope wrote it up here: https://lnkd.in/g8kzXyr7 If you’re working out where control planes fit in the AI infrastructure stack, Inference Day on November 5 is a good place to hear how other maintainers and practitioners are thinking about it. Bring your questions. 👇

Join us in ~3 hours (10am pac / 1700 UTC) for the Crossplane project community meeting! Jonasz Małecki will be showing off function-wasm, a new incredibly flexible way to run dynamic logic in your composition function pipelines. Calendar: https://lnkd.in/gi8KGTxe

Join us on Thursday Oct 15 for the Crossplane project community meeting! Jonasz Małecki will be showing off a new way to expand the flexibility of your composition logic with function-wasm, which can run WebAssembly modules as part of your function pipelines. It should be cool to see and think about the scenarios that get unlocked with that! register / add to calendar from the Crossplane public calendar: https://lnkd.in/gi8KGTxe

🪶 Crossplane providers just got a lot lighter! Providers used to cache every CRD schema and Secret in the cluster, needed or not. With crossplane-runtime v2.4.0, provider memory drops by roughly 80-95% on clusters with ~2,000 CRDs. Just upgrade your providers. Big thanks to Rafał Jan, who debugged the issue and contributed the fix 🙇 Jonasz Małecki wrote up how it all came together, including the rollout across providers 👇 https://lnkd.in/gDB8fcRf #Crossplane #Kubernetes #OpenSource

🛠️ Introducing the new Crossplane CLI developer experience! Building a platform on Crossplane just got simpler. The new DevEx tools are built around a Project: one standard layout that holds your XRDs, compositions, and function code, built and versioned as one unit. No more inventing your own workflow. The part we love most: you can go from an empty directory to a working platform API on a local control plane with a handful of commands. Generate your XRD from a simple schema, write functions in Go, Python, KCL, or templated YAML with typed bindings, render your composition locally, and run it all with crossplane project run. Adam Wolfe Gordon walks through building one from scratch 👇 https://lnkd.in/gyqgGguw Automated testing and simulations are next. Come share feedback in #sig-cli on the Crossplane Slack! #crossplane #cloudnative

The Crossplane project community meeting on Thursday this week should be a good one! Scott Rosenberg will be showing off his work on a declarative conversion operator, which makes it easier to handle the conversions between versions of your XRDs and CRDs: https://lnkd.in/gBFFu86J This has historically been a challenge for Crossplane users, so this is an interesting project that should spark some great discussion. Come join us on Thursday and learn more from Scott! 🙌 Add to your calendar from https://lnkd.in/gi8KGTxe

we are grateful for all the continued contributions and participation from the crossplane community - thank you to everyone who has helped make the project better! 🙇 as the amount of contributions has increased with the rise of AI tools, we have now published an official policy regarding the usage of AI when contributing to the crossplane ecosystem: https://lnkd.in/grdPVxPU going forward, all contributions across all the crossplane and crossplane-contrib repos are expected to adhere to this policy. the key concepts we've tried to capture here: * AI usage is assumed and does not need to be formally disclosed in any way. * Human contributors own their entire submission and must understand all of it. * We want to engage and collaborate directly with other humans, not with your agent. * Maintainer time is the project's scarcest resource, so use AI tools in a way that makes effective use of that limited time. * Maintainers may close submissions that don't meet the policy, and block contributors who continue to violate it. feel free to let us know if you have any questions about the policy! we're excited to continue engaging in meaningful ways with all of the amazing contributors to this project, thank you so much! 🤩

On the heels of yesterday's v2.4.0 release, a new round of Crossplane patch releases is also ready for your production control planes! 🙌 • https://lnkd.in/geBJ_mCc • https://lnkd.in/gatpQNKd • https://lnkd.in/gznQi_sw The v2.3 and v2.2 patches include a fix to properly generate crossplane binary amd64 checksums, so install scripts and Dockerfiles that verify them no longer fail. This was already included in v2.4.0. All three releases also pick up security fixes in Crossplane's dependencies and matching crossplane-runtime patch releases were also included 💪

Crossplane v2.4.0 is available now for your production control planes! 🎉 Watching required resources: composition functions can require resources they don't compose, but Crossplane didn't watch them, so a change didn't reach the XRs until their next regular poll. Crossplane now tracks what each XR depends on and drives watches from that, so a change to a required resource kicks off an XR reconciliation right away. Scale to Zero for safe-start capable Providers: a provider whose ManagedResourceDefinitions are all inactive now runs with zero replicas, and scales up once its first MRD is activated. Installing a broad set of providers no longer costs you a running pod for each one that has nothing to reconcile yet. Vulnerability-scannable images: our container images now carry their full Go dependency list, so grype and trivy can see CVEs in our third-party dependencies rather than just the main module and the standard library. No more hidden vulnerabilities! ...and also more reliable package runtime management, hardening across the composition and package paths, version-aware docs search, and security fixes in Crossplane's Go toolchain and dependencies. Lots to be excited about! 🚨 v1.20 EOL: this is the final release cycle where v1.20 is maintained. When v2.5 is released in Nov 2026, v1.20 reaches EOL and no longer receives support or maintenance from the project. This applies to the v1.20 release only - v1 legacy workloads like Claims and cluster scoped resources remain supported in v2 via back compat. Full details are in the release notes. And a big congratulations to our Release MVP Rafał Jan, who discovered and drove a critical fix for major memory consumption in providers that are safe-start capable. Thank you very much! 🙇 Full release note details: https://lnkd.in/gHbMb-_Y