action #111329
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #81060: [epic] openQA web UI in kubernetes
openQA within kubernetes with tested helm charts size:M
Description
Motivation¶
In #110524 a proof-of-concept has shown that it's feasible to have helm charts for an openQA webui+worker kubernetes cluster. To have something supported and maintainable we should have helm charts within our openQA repo (or a related repo) with at least static helm chart tests
Acceptance criteria¶
- AC1: Tested helm charts for openQA workers in a repo maintained by us
Suggestions¶
- Read https://github.com/os-autoinst/openQA/pull/4650 , try it out, see what's missing
- Add "industry standard" helm chart static tests
- Include at least the parts covering openQA workers
- Create kubernetes cluster inside docker inside GitHub Actions: https://github.com/marketplace/actions/kind-cluster
- Look at chart-testing tool: https://github.com/marketplace/actions/helm-chart-testing
- Try to deploy the chart inside CI
Updated by tinita over 2 years ago
- Subject changed from openQA within kubernetes with tested helm charts to openQA within kubernetes with tested helm charts size:M
- Status changed from New to Workable
Updated by jbaier_cz over 2 years ago
- Description updated (diff)
Updated suggestions according what I found during making the PoC
Updated by jbaier_cz over 2 years ago
- Status changed from Workable to In Progress
I will happily take it :)
Updated by jbaier_cz over 2 years ago
https://github.com/os-autoinst/openQA/pull/4650 is updated to contain some enhanced linting and test installation
Updated by jbaier_cz over 2 years ago
- Status changed from In Progress to Feedback
Features are merged so subsequent tests should also tests the Charts we added in earlier commits.
Updated by jbaier_cz over 2 years ago
- Status changed from Feedback to Resolved
We had a couple of PR after this one, the test seems to be running and passing. We can probably continue with #81060