Add proposal for Crossplane to move to Incubation #620
Conversation
|
@resouer and @rochaporto will be leading things from a TOC sponsor perspective |
| as | ||
| [provider-ssh](https://www.youtube.com/watch?v=CxwmrKi1jtM&list=PL510POnNVaaYFuK-B_SIUrpIonCtLVOzT&index=6) | ||
| as a way to provision, manage, and run scripts against bare metal instances and VMs | ||
| * The following are examples of ecosystem projects that have collaborated and integrated with |
There was a problem hiding this comment.
Hi @jbw976 . Just want to point out two more ecosystem use cases if you want to add them here:
- KubeVela project uses Crossplane as cloud resource provider to provision infrastructure resources and bind to applications: link
- Alibaba internal platforms have adopted Crossplane to model and manage infrastructure resources as well
There was a problem hiding this comment.
Thank you for those details and reminder @hongchaodeng, I will include those in the update tonight. Thank you very much!
There was a problem hiding this comment.
https://github.com/displague/provider-cloudinit is moving forward as a way to manage userdata, it is in a better state than provider-ssh. As a new provider, there are questions around the experience this provides.
I would love to see incubation bring more users and use-cases to the table, offering and exploring solutions.
jbw976
force-pushed
the
crossplane-incubation
branch
from
51c3535
to
e47e2d1
Compare
|
I've updated the proposal in this PR to also include the Due Diligence document and the presentation slide deck for SIG App-Delivery:
|
|
|
||
| ## Incubation Requirements | ||
|
|
||
| ### Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope |
There was a problem hiding this comment.
Could you please separately list out end users according to this definition? https://github.com/cncf/toc/blob/main/FAQ.md#what-is-the-definition-of-an-end-user
There was a problem hiding this comment.
I've now split this production user section into end users and cloud native vendors, as per the CNCF's definition you linked to harry :)
jbw976
force-pushed
the
crossplane-incubation
branch
from
e47e2d1
to
ec15f11
Compare
|
I am in support of this!!! 🚀 |
|
Best of Luck Crossplane! |
|
We use crossplane in staging and strongly support this move. Crossplane providers alone are a big win, and together with crossplane compositions it is awesome. It also works well with other projects in CNCF landscape. |
|
Crossplane is an amazing product and we believe that the cloud native ecosystem will greatly integrate with its approach. |
|
Great to see Crossplane moving to Incubation -- big win for the cloud native community for managing platform/infra from k8s! |
|
For Datalayer (http://datalayer.io), we are pivoting our systems to build on top of Crossplane to create cloud infra as K8S services. We are very happy so far why the Crossplane vision and implementation. Having Crossplane into CNCF incubation definitively makes a lot of sense. |
|
Crossplane will be fundamental in how we consume the cloud going forward. Going into CNCF incubation is definatly the right move. |
|
We @vshn are using Crossplane in production to manage over 1000 services, and it keeps on growing. To connect Crossplane to Cloudfoundry we even developed the crossplane-service-broker. I strongly support Crossplane moving into incubation, it is very well deserved 💯 |
jbw976
force-pushed
the
crossplane-incubation
branch
from
ec15f11
to
9e2da1b
Compare
|
At Squiz we're using Crossplane to provide production-reliability internal services to our product development teams, and are working towards customer-facing production usage. We have spun out and developed provider-cloudflare, as we believe that, in combination with Crossplane's Composition feature, this was the shortest path to providing self-service, curated access to Cloudflare resources for our product teams. We will also continue to work on further contributions back to the Crossplane community. From a feature perspective the Composition mechanism enables a way of describing infrastructure and applications that is uniquely powerful when compared to other IAC / Platform tools and for that reason alone I strongly support it moving into Incubation 🚀 |
|
We have been building self-service portals coding against the SDKs of various cloud providers. With one eye we looked at Terraform but never felt it to be a perfect fit due to its CLI nature and proprietary syntax to describe Infra. The Crossplane idea ist amazing as it is solving several problems. We can stay with a well know interface and syntax, we can run the control plane inside an established an de-facto standard runtime K8s. Same like K8s is the only existing standardised abstraction across cloud providers Crossplane has the potential to enhance it to become the same standardised abstraction to manage Infra As Code and to avoid the proprietary offerings of various cloud providers here. All thumbs up from our team here for Crosssplane to move it out of the sandbox !!! |
jbw976
force-pushed
the
crossplane-incubation
branch
2 times, most recently
from
e74657d
to
1ab0d6e
Compare
|
I fully support this. Crossplane is an incredible product and really helps manage AWS infrastructure. |
|
Crossplane is awesome. Especially the design of provider credentials and the principle of cloud resource fidelity of Crossplane runtime project inspires me a lot to start up Kubernetes Terraform controller. |
|
In our case, it will have a real benefit for wider adoption. Having Crossplane in incubation will make it much easier for those of us who recommend it for projects but, despite being fully mature and stable, keep getting rejected in favor of the usual tool because it is "still" in sandbox. One less reason to break the inertia! +1000 |
|
Best of luck! Crossplane is a incredible product. |
jbw976
force-pushed
the
crossplane-incubation
branch
from
1ab0d6e
to
9f54c5d
Compare
|
Absa Group(South African financial service provider) is actively adopting Crossplane as a backbone of its advanced cloud-native platform. We are using XRD abstraction to simplify the management of multiple cloud resources as well as the complex configuration of Kubernetes operators at scale. We will be definitely happy to see Crossplane reaching the Incubation level, it totally deserves it. |
|
[Update] Hey we're working on this one, slow going with adopter interview but will finish soon. If anyone are also interested in talking with TOC (me or @rochaporto ), feel free to ping us in CNCF slack. |
jbw976
force-pushed
the
crossplane-incubation
branch
from
9f54c5d
to
26bcefa
Compare
amye
moved this from Needs TAG Review & Recommendation
to In Due Diligence
in Incubation Projects Backlog
amye
moved this from In Due Diligence
to In Public Comment Period
in Incubation Projects Backlog
jbw976
force-pushed
the
crossplane-incubation
branch
from
26bcefa
to
17acb54
Compare
amye
moved this from In Public Comment Period
to In TOC Vote
in Incubation Projects Backlog
jbw976
force-pushed
the
crossplane-incubation
branch
from
17acb54
to
f470a17
Compare
Signed-off-by: Jared Watts <jbw976@gmail.com>
jbw976
force-pushed
the
crossplane-incubation
branch
from
f470a17
to
2a0266f
Compare
|
Hi, should this be merged now? |
This PR contains the proposal and supporting evidence to move Crossplane to the Incubation stage. Crossplane was originally accepted into Sandbox in June of 2020 and we believe that the projects growth, maturity, and accomplishments since then justify moving to Incubation.
This proposal contains the following:
We are ready to take next steps with a SIG, perform due diligence, etc. @jbw976 will be the main representative from Crossplane for this process.