Manage any infrastructure your applications need directly from Kubernetes (by crossplane)


Basic crossplane repo stats
6 days ago

crossplane/crossplane is an open source project licensed under Apache License 2.0 which is an OSI approved license.

Crossplane Alternatives

Similar projects and alternatives to crossplane based on common topics and language

  • GitHub repo OpenFaaS

    OpenFaaS - Serverless Functions Made Simple

  • GitHub repo kubefed

    Kubernetes Cluster Federation

  • GitHub repo spec

    Container Storage Interface (CSI) Specification. (by container-storage-interface)

  • GitHub repo Pulumi

    Pulumi - Modern Infrastructure as Code. Any cloud, any language 🚀

  • GitHub repo Openshift Origin

    Conformance test suite for OpenShift

  • GitHub repo gloo

    The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better crossplane alternative or higher similarity.


Posts where crossplane has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-02-24.
  • Why Is Kubernetes So Hard - 4 Reasons Why And What to do About it
    If your managing it as a one man show there can be a steep curve for sure if your new to everything. It's getting easier and easier as the ecosystem grows. Something I'm keeping an eye on is which turns all your cloud provider stuff into k8s resources, I suspect something like this will be the future eventually. Good luck!
  • Manage any infrastructure your applications need directly from Kubernetes | 2021-03-02
  • Crossplane: GKE Installation | 2021-02-24
    ..Crossplane is an open source Kubernetes add-on that supercharges your Kubernetes clusters enabling you to provision and manage infrastructure, services, and applications from kubectl.* (
  • Infrastructure Engineering — Deployment Strategies | 2021-02-13
    Thinking of hybrid deployments brings us to workload portability because unless you have a portable workload, it may not be feasible to have hybrid deployment strategies. This also means that you have to reduce the dependence on proprietary services from your cloud providers as much as possible since you might have to end up doing cross-cloud or cross-region API calls otherwise if your other cloud provider or on-premise systems don't support it. Or sometimes you might even have to build out abstractions within your applications since not all the same service across multiple cloud providers does not often have the same APIs adding more complexity especially with hybrid architectures or you might have to use something like Crossplane to enable this for you to some extent.
  • Getting sick of AWS, anyone have anything else they like? | 2021-02-04
  • Blazingly fast app deployment on AWS with Heroku like experience | 2021-01-31
    I understood that part, but it's somewhat reinventing this like: OAM (, and some of it's implementations like Crossplane (, which at the end of the day focus on git-ops, application centric, moving things to prod without care about the underlying provider, as in this case they're very upfront on Using Kubernetes as Infra.