-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Multi-arch for operators #256
Comments
Needs ADR from stackabletech/documentation#259 |
This is "In Progress" for Refinement. Is that still true? |
No, wanted to look over it this morning. I think it's good now. Should I move it to waiting for? |
When you're done with Refining you can move it to the right, yes. "Refinement Acceptance: Waiting for" |
Ok, done. |
I'll transfer this issue to the issues repository |
There are no issues for Parallel Task Group B yet. As far as I understand the description we should be ready to start those though, right? |
Created a new issue for that! There seemed to be enough work for the people active on this task already, but somebody from the team could join in on this one of course. Good catch. |
Current state of building operator binaries with ubi8-rust-builder: We had a meeting @vsupalov @teozkr and @Maleware and putted our heads together. We were able to proof that the code is working as we expect it to be. This means that arch images contain pure arch environment (base os, other dependencies) and the binary compiled with the rust builder meets the architecture of the baseOS. We still do not understand why those things are working nor where the problems comes from we try to avoid by our fixes. Needs probably further investigation. The open issue suggests the problem we try to avoid. |
I've made a ticket for multi arch testing: #299 as this was raised here stackabletech/kafka-operator#481 (comment) I've added it to the epic as well, in Task Group C @vsupalov pinging you to make sure this seems good to you |
Looks good! I'll go ahead and rephrase "Run test infrastructure for AMD and ARM images which are pushed to stackable-experimental" to aim at multi-arch nightly tests upon "stackable" image pushes. This makes more sense. |
If we revive this, we can use native ARM runners which integrate with GitHub actions. No need to migrate to Circle. |
Replaced |
Closed |
Epic needs re-planning.
Only current milestone: #414
Future Goals
The text was updated successfully, but these errors were encountered: