Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

KEP-36: HELM driver for KUDO #1777

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

KEP-36: HELM driver for KUDO #1777

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 56 additions & 0 deletions keps/0036-helm-driver-for-kudo.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
kep-number: 36
short-desc: HELM driver for KUDO
title: HELM driver for KUDO
authors:
- "@rishabh96b"
owners:
- TBD
editor: TBD
creation-date: 2021-03-11
last-updated: 2021-03-11
status: provisional
---

# helm driver for kudo proposal

## Table of Contents

* [Summary](#summary)
* [Motivation](#motivation)
* [Goals](#goals)
* [Non-Goals](#non-goals)
* [Proposal](#proposal)
* [Implementation History](#implementation-history)
* [Drawbacks [optional]](#drawbacks-optional)

[Tools for generating]: https://github.com/ekalinin/github-markdown-toc
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove


## 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"helm driver"... what does this mean?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This gives the impression that there is a way to use kudos against helm charts... which is not true


## Motivation

Application operators often want to perform maintenance on an application that is unique to that application. KUDO's ability to define custom operations as part of its definition makes common actions less error prone. This functionality is missing in helm forcing develpers/admins to rely on manual actions for performing administrative tasks. As KUDO possess this powerful capability, a helm driver would aim to fill this gap in helm based deployments.

### Goals

- capability to extend helm packaged applicatins with kudo to write custom plans/tasks.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

applicatins -> applications


### Non-Goals



## Proposal

- TBD


## Implementation History

## Drawbacks

- Could require significant development efforts.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not a proper drawback... this is intended to be drawbacks of one approach over another approach.