🔌 Plugin: Komodor integration

[TalFrum]

🔖 Summary

Komodor is a dev-first, kubernetes platform, that lets the developer operate, troubleshoot and optimize their kubernetes apps.
The plugin requires installing of the Komodor backend plugin in and an API key of Komodor in order to make it work.

🌐 Project website (if applicable)

https://komodor.com

✌️ Context

The plugin lets the user monitor their clusters by showing them crucial information about their workload statuses.
It shows up as a tab in the component window.

👀 Have you spent some time to check if this plugin request has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

Yes I am willing to submit a PR!

[tudi2d]

Welcome @TalFrum to the community 🎉 Sounds great - heads up that we are at the moment thinking about alternative ways to host the plugins of Backstage as it became hard for us to maintain backstage/backstage#20266.

Would you be open to create this plugin in a seperate repository in the Komodor Organisation or your personal profile? You could still add it to the Open Source Directory (https://backstage.io/plugins/) later. Good examples of plugins that have done that recently are the LimusChaos Plugin or the Pulumi Plugin

[TalFrum]

Sounds good @tudi2d but I'd like to know what it takes to do it.
In the traditional way I had to sumbit a PR first, and once it is accepted you create the packages so it is downloadable. Choosing the 'local repo' way, should I just add the plugin yaml file to the open source directory?
Should I create an issue for that and submit the file to PR on master branch?
Do you test the plugin yourself before publishing it in backstage.
Seems a little unclear, I need more details.
Thanks in advance!

[camilaibs]

Hi @TalFrum , just replying on behalf of @tudi2d :

Choosing the 'local repo' way, should I just add the plugin yaml file to the open-source directory?

Adding the plugin yaml to the open-source directory is the way to go in the local repo case 🙂

Should I create an issue for that and submit the file to PR on master branch?

You can reference this issue on the pull request, here we have enough context on the comments 🙌🏻 .

Do you test the plugin yourself before publishing it in backstage.

Yes, we usually do try to install and play with it.

[hamzisco]

Hi there! Has there been any progress/update on this plugin? Is there anywhere I can go to see the progress? I am very interested to know the capabilities of a Komodor plugin for Backstage, thanks!

[freben]

Not that I know, this is waiting for someone to contribute a plugin. 🙏