[Feature] CI image test
- Dominant language
- Java
- Stars
- 7
- Forks
- 5
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 34
Description
### Relevant component
refarch-gateway, refarch-integrations
### Problem description (optional)
Often errors in the gateway-image are only detected after the release and when somebody else testes them.
This makes the gateway unstable.
This behavior could occur for all images.
### Desired solution
Test created images in the ci.
### Considered alternatives (optional)
- Manual testing i.e. CAP
- Kubernetes in CI (see helm-charts kind cluster)
### Additional context (optional)
_No response_
### No duplicate
- [X] I confirm that this issue is not a duplicate
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the CI configuration for refarch-gateway and refarch-integrations, then review the helm-charts kind cluster setup mentioned in the issue. The work is complete when images created in CI are tested before release and errors in the gateway image are detected for the named components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100