Repository navigation
Kroxylicious #113
Description
Please describe the project
Kroxylicious, the snappy open source proxy for Apache Kafka®
URL for the project
https://kroxylicious.io/
Describe current CI/CD setup
Github actions are used to build and test the project.
Describe the primary use case for the Github Action Runner
Pushes to main (and releases) triggers our multi-arch container builds. Currently, this is limited to amd64 and arm64 based container images only. Our use-case for your runners would be to build container images for s390x and ppc64le too.
As the project is Java, the workload for your runners will amount to:
- a docker build stage that pulls in the appropriate UBI base image for the arch
- a docker copy stage that copies JAR artefacts built by earlier (shared) steps workflows
We won't be running tests on your runners(at least initially - we'll raise another onboarding request if that changes).
Paste a link to the existing actions workflow file(s) or directory
https://github.com/kroxylicious/kroxylicious/blob/main/.github/workflows/docker.yaml
https://github.com/kroxylicious/kroxylicious/blob/main/kroxylicious-kubernetes/kroxylicious-operator/src/main/docker/operator.dockerfile
https://github.com/kroxylicious/kroxylicious/blob/main/kroxylicious-kubernetes/kroxylicious-admission/src/main/docker/webhook.dockerfile
How often do you plan on executing the runner?
Every push to main (5-6 events per day) and one each project release (once every two months)
What is the primary programming language for the project?
Please select desired hardware
- Power 9 (ppc64le)
- IBM Z / LinuxONE (s390x)
Account names of the GitHub repo admins that will need access to setting up the runner
ideally https://github.com/orgs/kroxylicious/teams/pms
or if it has to be individuals:
Activity
pleia2 commentedon Sep 17, 2026
Hi @k-wall, thanks for your patience. As we evaluate this one, could you give us an indication of how long each test takes to run and how many tests you'd be running on these architecture-specific runners on each push to main? This will help us with better understanding the capacity requirements.
k-wall commentedon Sep 21, 2026
Hi @pleia2, I'd defined the initial scope above to container build/push only. No tests initially
Execution time ~5 mins
As a follow on step, we will want to run a smoke test on each arch. We haven't defined this at the moment, but it would probably be a handful of tests chosen from our existing system test suite.
Additional Execution time ~5-10 mins
pleia2 commentedon Sep 22, 2026
Thanks @k-wall, we're happy to move forward with on-boarding your project.
Please install the GitHub App from the following link and select your repository:
🔗 Power Z GHA Runner App
For more details on the on-boarding process, please refer to our documentation:
📄 Onboarding Guide
Please let me know in this issue once you have installed the github app on your repos. For security reasons, I will double check it is the correct repos and then approve the repos to use our images. You will not be able to use our images until I approve the repos.
After the repos have been approved, you will be able to use the
ubuntu-24.04-s390xandubuntu-24.04-ppc64leimages in your workflow file. The on-boarding doc linked above will be helpful.Please note: forks will not be able to use this service since those repos will not be in our allow list.
SamBarker commentedon Sep 22, 2026
Thanks @pleia2 I've installed the GitHub app with access to kroxylicious/kroxylicious.
pleia2 commentedon Sep 22, 2026
The repository has now been approved, you can now start using the images in your workflow.