openmcp-project / openmcp-project/backlog

Task: Add functionality to GitHub bot for quota and resource increases

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

Nobody has claimed this yet.

Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Understand the Task

Description

Add functionality to the openMCP GitHub bot that reacts in issues of type quota-increase and type resource-increase.

Quota increase

In the issue it has to be clearly specified what the name of the landscape, project, workspace is.
In the issue, a list has to be specified for which kind of resources the quota shall be increased.
Possible values:

  • secrets
  • serviceaccounts
  • ManagedControlPlane
  • ManagedControlPlaneV2
  • Service Providers for V2 ???

The bot then connects to the onboarding cluster and applies the increased quotas to the workspace.
The bot will increase the quota by 25% of the current quota.
The bot will then close the issue.

Resource Increase

In the issue it has to be clearly specified what the name of the landscape, project, workspace, ManagedControlPlane is.
Note: this currently is vor V1 only. We will need a follow up issue for V2.

A human approve has to appove.
The bot then connects to the onboarding cluster and applies a InternalConfiguration with the same name and namespace as of the mcp. The internal configuration applies a preconfigured clusterprofile.
The bot will then close the issue.

Example:

apiVersion: core.openmcp.cloud/v1alpha1
kind: InternalConfiguration
metadata:
  name: <name-of-mcp>
  namespace: <namespace>
spec:
  components:
    apiServer:
      gardener:
        landscapeConfiguration: default/gcp-large
Any further valuable resources.

No response

What is required to accept the Task as done.

Done Criteria

  • Bot can handle quota increases
  • Bot can handle resource increases

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 reviewing the quota-increase and resource-increase requirements in issue #481 and the InternalConfiguration YAML example. Confirm how the GitHub bot connects to the onboarding cluster, handles approval and quota changes, and closes issues; done means both checklist items work.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.