[48h Knative] Kamelet Sinks

[rhuss]

👋 Hello awesome contributor!

Are you excited about Knative and open-source development? You're in the right place! This is a mini-project for the upcoming 48h Knative event—a 48-hour hackathon designed to boost contributions to the Knative Client project. For more details, check out Issue #1842.

🎯 Project Description

The Kamelet plugin for kn currently only supports sources, but not sinks. The task of this project is to create the foundation for CRUD managing sinks in a similar fashion as sources, so that they can be easily connected to a Knative Eventing broker.

🌟 Benefits

Sink are pre-factored consumer of events to e.g. export CloudEvents to backends like AWS S3 or Telegram. It is very helpful to not reinvent the wheel for just exporting a CloudEvent to a well-known backend. Kamelets and Camel-K support sinks out of the box, so we should support them with kn as well.

🛠 Difficulty Level

Intermediate, some Camel-K knowledge would be helpful but is not mandatory.

👥 Recommended Team Size

1

🎉 Expected Outcome

At the end a skeleton for sink management with Camel-K should be implemented. It can be easily mimic the way how Kamelet sources are handled, i.e. many of the existing code can be used as a blueprint.

At least a kn kamelet binding create sink should be implemented.

🤝 Mentor

@rhuss / @christophd

📝 Additional Information

tbd

🌐 Entrypoints

tbd

---

📋 Organizer Checklist

• Added to Project Board
• Proposal Reviewed
• Assigned a Mentor
• Expected Outcome define

[Nageshbansal]

/assign

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.