Design: Addon Management

[stealthybox]

In order for the community to create and maintain addons, we need a shared interface for addon installation and overall lifecycle.

There are a number of considerations regarding packaging, runtime, security, dev tools, ops tools, use-case, and governance.

These concerns are separate from creating operators or other programs concerned with addon specifics such as #3. (ex: How do you install or maintain the coredns-operator?)

This google doc aims to list and weigh various approaches and trade-offs:
https://docs.google.com/document/d/1tpayzZ4teTKOXNUEsA2HK73eWzz9MhZOFTKYz_rRI_8

• Anyone can view and comment
• kubernetes-dev members can edit
• kubernetes-dev members can change permissions
  ( reach out if you are not a member but desire edit access )

This should enable fair, open, async discussion across time-zones.

From this doc, one or more parties may create proposals(KEP's) which can compose or compete.
These new proposals may build on the existing KEP: kubernetes/enhancements#746

Feel free to comment here and/or on the document.

/kind design
/priority important-soon
/sig cluster-lifecycle

[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.

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

[stealthybox]

/lifecycle frozen