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.

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

GSOC: add Keptn project ideas for GSoC 23 #832

Merged
merged 4 commits into from
Feb 15, 2023
Merged
Changes from 1 commit
Commits
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
23 changes: 23 additions & 0 deletions summerofcode/2023.md
Original file line number Diff line number Diff line change
Expand Up @@ -187,3 +187,26 @@ If you are a project maintainer and consider mentoring during the GSoC 2023 cycl
- Expected project size: 350h
- Difficulty: Hard
- Upstream Issue (URL): https://github.com/WasmEdge/WasmEdge/issues/2244

### Keptn

#### Keptn Plugin for Backstage

- Description: Backstage is an open platform for building developer portals. As the website states, "powered by a centralized software catalog, Backstage restores order to your infrastructure and enables your product teams to ship high-quality code quickly — without compromising autonomy". It would be nice to provide Keptn integration for this portal so that Keptn can connect as many as other tools. See all Backstage Plugins. A Possible solution could be a specialized plugin for Keptn using Keptn REST API and/or CLI. It might be also possible to create a unified plugin for Keptn and other CI/CD tools, e.g. implemented on the top of the Cloud Events / CDEvents standard.
- Expected outcome: Finding issues blocking multiple control planes, and possibly fixing them.
- Recommended Skills: Typescript, Javascript, React, Backstage
- Mentor(s): [Brad McCoy](https://github.com/bradmccoydev)
- Expected project size: 175h
- Difficulty: Hard
- Upstream Issue (URL): https://github.com/keptn/integrations/issues/19

#### Create additional metrics operators for KLT

- Description: This idea consists of two components, a metrics-operator, and a metrics-adapter. The metrics operator manages CRDs for Metrics and Providers, similar to the approach we used in evaluations. The adapter can query these metrics and present them via the Kubernetes Metrics API.
- Expected outcome: Metrics and Providers can be specified via CRs The values for the metrics are stored in the status of the CRs The metrics adapter is able to fetch these metrics and provide them Limitations
Currently, this approach seems to work only in a namespaced way, therefore metrics have to be provided per namespace (not sure about specifying them on a cluster level) There is no history of the metrics available Further options. We could define an SLO resource that utilizes metrics As this provides a very simple, unified way to present metrics in Kubernetes, we could also provide plugins for Argo and Flagger to query the resources Keptn Evaluations could also use these metrics
- Recommended Skills: Typescript, Javascript, React, Backstage
- Mentor(s): [Thomas Schuetz](https://github.com/thschue)
- Expected project size: 175h
- Difficulty: Hard
- Upstream Issue (URL): https://github.com/keptn/lifecycle-toolkit/issues/525