KEP-36: HELM driver for KUDO #1777
Conversation
Signed-off-by: Rishabh Bohra <[email protected]>
rishabh96b
requested review from
alenkacz,
gerred,
kensipe and
zen-dog
as code owners
There was a problem hiding this comment.
we usually have a low bar in the acceptance of "provisional" status of KEPs.. however there are big concerns with this KEP...
There has been several attempts to provide KUDO enabled packaging around helm charts... essentially to add KUDO plans around helm... they have all had issues and have been abandoned. Is there something different about this request? Is there something imagined on how to handle this? There is a lot of work here and it may be best to discuss / create a POC ahead of this KEP or provide enough detail here in order to evaluate.
| * [Implementation History](#implementation-history) | ||
| * [Drawbacks [optional]](#drawbacks-optional) | ||
|
|
||
| [Tools for generating]: https://github.com/ekalinin/github-markdown-toc |
|
|
||
| ### Goals | ||
|
|
||
| - capability to extend helm packaged applicatins with kudo to write custom plans/tasks. |
| ## Summary | ||
|
|
||
| KUDO enables Operator developers to create Operators and expose features of the underlying applications. KUDO helps in the lifecycle management of the underlying applications by enabling develpers to create custom tasks and plans. | ||
| The goal of this KEP is to facilitate the helm driver for kudo so that developers can define custom tasks and plans for their applications packaged in helm to provide developers/admins can achieve better application lifecycle management. |
There was a problem hiding this comment.
"helm driver"... what does this mean?
There was a problem hiding this comment.
This gives the impression that there is a way to use kudos against helm charts... which is not true
|
|
||
| ## Drawbacks | ||
|
|
||
| - Could require significant development efforts. |
There was a problem hiding this comment.
this is not a proper drawback... this is intended to be drawbacks of one approach over another approach.
Signed-off-by: Rishabh Bohra [email protected]