Introduce plugin mechanism?

[maciaszczykm]

Starting a discussion here. Plugin mechanism should allow all people using their third party resources to customize Dashboard to their needs.

Things to consider:

• Architecture
• How would it enhance Dashboard functionalities (dynamically added components?)
• How would it connect to external APIs
• Limitations and possibilities (how much can we enhance Dashboard UI with plugins?)

[cheld]

The use case is to replace the generic UI of third-party-resources with a customized, user friendly version. This is just one use case for a plug mechanism. There are others like helm or weave.

Some technical issues to consider:

• Bread crumbs
• Namespace selector
• Error handling
• Automatic refresh (not merged yet)
• cross origin stuff

[aledbf]

@maciaszczykm do you have some estimation when this feature could be available? Or better yet how I can add a feature to the dashboard?
This is what I want to add kubernetes/ingress-nginx#109 as feature

[bryk]

@aledbf I guess this feature is still to be defined and scoped. Can you help here by stating what would be needed from Dashboard to support kubernetes/ingress-nginx#109 case?

[floreks]

I'm not sure if ingress features would be a good example of a plugin. We could just extend our detail page and provide better control over ingress resources. AFAIR our plugin mechanism was supposed to mainly support custom views for third party resources.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close