mayadata-io / mayadata-io/oep-e2e
Unable to run kubera components on Konvoy
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Since Tuesday(yesterday) after the gitlab came up, when the Konvoy pipeline got triggered the Kubera components took more than expected time(more than 25-30 mins) and still pods weren't up.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Konvoy pipeline triggered after GitLab came up and inspect the Kubera component pod startup logs and timing. Reproduce the delayed run if possible; done means the components reach a running state within the expected window, with the cause and verification recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, kubernetes
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100