kubero-dev / kubero-dev/kubero

Add a TTL for Review Apps

Open
#422 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature Idea/discussion
Dominant language
TypeScript
Stars
4.4k
Forks
212
PR merge metrics
No merged PRs in 30d

Description

Description

Review Apps are apps that were created by opening a PR. these review Apps should have an optional Time To Live (TTL).

The TTL should be defined by every pipeline. A default should be to let the apps live forever (to keep the backward compatibility). The TTL should be set when creat

Possible solution

Add a new input field here

image

Alternatives

No response

Additional information

This will require changes in the Operator to to handle this field. It is not clear, who or what will remove these apps. Probably a periodic cronjob within the kubero namespace, which calls an API endpoint on the kubero UI container.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Review Apps pipeline input and the Operator handling described in the issue. Determine how the TTL should be stored and enforced, including whether a periodic cronjob in the Kubero namespace should call an API endpoint on the Kubero UI container; done means the optional field preserves apps indefinitely by default and expired apps are removed.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, typescript
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.