Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QUARKUS-3249 | Configurable init containers #159

Merged
merged 1 commit into from
Mar 19, 2024
Merged

QUARKUS-3249 | Configurable init containers #159

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions QUARKUS-3249.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# QUARKUS-3249 Configurable init container

This document is a high level test plan for options to configure init containers in Quarkus

JIRA link: https://issues.redhat.com/browse/QUARKUS-3249

## Scope of the testing
* Check, that flyway task can be disabled
mjurc marked this conversation as resolved.
Show resolved Hide resolved
* Check, that we can use custom image for the run and change its pull strategy
* I suppose, we should build the image ourselves, so a Docker file should be provided
mjurc marked this conversation as resolved.
Show resolved Hide resolved

### Current test coverage
* Upstream coverage for Kubernetes, but without runs on the cluster

### Impact on test suites and testing automation
* Several new tests (probably, one or two new test classes) in `sql-db/panache-flyway` module

### Impact on resources
* No impact on maximum consumed cluster resources
* Openshift JVM run will take five or ten more minutes for databases scenario, Openshift Native run will take twice as much
* Databases scenario is still shorter, than http-scenario, so no effect on total run time

## Future considerations
* Check, that Quarkus uses better image (no image agreed in upstream yet)
mjurc marked this conversation as resolved.
Show resolved Hide resolved

## Contacts
* Tester: Fedor Dudinsky <[email protected]>

## References
* Feature JIRA: [QUARKUS-3249 Make the init container image configurable and find a A+ image](https://issues.redhat.com/browse/QUARKUS-3249)
* Upstream docs: https://quarkus.io/guides/init-tasks
* Upstream issue: https://github.com/quarkusio/quarkus/issues/35455