Feature ideas

In scenarios where multiple (and growing) numbers of Kubernetes clusters exist in a customer environment, using one exporter per cluster won't be feasible; therefore, it would be important for the K8s exporter to be able to extend to multiple clusters.

We prefer to deploy through certified marketplace listings for easier deployment and compliance.

Today a delete operation of the file is not deleting the mapped entities from Port in the file kind of Git integrations

We are interested in getting the flag-dependancy of flag-status blueprint I found https://launchdarkly.com/docs/api/feature-flags-beta to get that info, although it in beta for now

Embed the documentation directly in the integration-installation modal. This keeps users in flow, gives them step-by-step guidance without switching tabs, and helps prevent setup or permissions slip-ups.

Provide Monitoring and Sync Status details, which are currently provided for all the Ocean integrations for k8s-exporter and port-agent as well.

As a FinOps team member, I want to ingest data from FinOut to deliver it to developers. Right now, I struggle to deliver FinOps optimization advice to them and doing so in Port is the ideal way.

Today we have a static and strict small schema we bring about users and teams when integrating with an identity provider (user names, mails, team names) The idea here is to have the whole payload coming from the SSO provider (the schema should be known based on the SSO protocol) and for Port builders to be able to decide what they want to map to the user and team blueprints.

Enhance the Azure integration to fetch powerState of virtual machines. The current API response does not include this data