Thanks to visit codestin.com
Credit goes to github.com

Skip to content

ci: Publish to quay.io#1492

Merged
Techassi merged 2 commits into
mainfrom
ci/publish-to-quay-io
May 21, 2026
Merged

ci: Publish to quay.io#1492
Techassi merged 2 commits into
mainfrom
ci/publish-to-quay-io

Conversation

@Techassi
Copy link
Copy Markdown
Member

@Techassi Techassi commented May 20, 2026 •
edited
Loading

Part of stackabletech/issues#716, the repository layout is based on https://github.com/stackabletech/decisions/issues/83.

This PR adds quay.io as a publish target for all product container image builds. With that, we can natively push the images to quay.io instead of mirroring them from our Harbor instance.

Test CI run: https://github.com/stackabletech/docker-images/actions/runs/26161872014

@Techassi Techassi self-assigned this May 20, 2026
@Techassi Techassi moved this to Development: In Progress in Stackable Engineering May 20, 2026
@Techassi Techassi mentioned this pull request May 20, 2026
Open
30 tasks
@Techassi Techassi marked this pull request as ready for review May 20, 2026 12:43
@Techassi Techassi moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineering May 20, 2026
@dervoeti dervoeti self-requested a review May 20, 2026 14:46
@dervoeti dervoeti moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering May 20, 2026
dervoeti
dervoeti reviewed May 21, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@dervoeti dervoeti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically LGTM, but:

  • Did you take a look at build_spark-connect-client.yaml? It does not get pushed to quay but it's also in the stackable repository (not sdp) so maybe that's on purpose.

  • It seems like robot accounts on quay.io need to match a certain regex so the current name would fail? I just tested this with my own account:

Image

@Techassi
Copy link
Copy Markdown
Member Author

Techassi commented May 21, 2026

Did you take a look at build_spark-connect-client.yaml? It does not get pushed to quay but it's also in the stackable repository (not sdp) so maybe that's on purpose.

Yeah, I think that is mostly an internal thing. I'm fine not pushing it to quay.io, but I'm also happy to push it - it is basically a decision we have to make.

It seems like robot accounts on quay.io need to match a certain regex so the current name would fail? I just tested this with my own account:

The names should be fine, because I created the robot accounts using these names. Maybe it fails because they already exist?

image

@dervoeti
Copy link
Copy Markdown
Member

dervoeti commented May 21, 2026

Yeah, I think that is mostly an internal thing. I'm fine not pushing it to quay.io, but I'm also happy to push it - it is basically a decision we have to make.

Okay, we can decide later, won't block this PR for this.

The names should be fine, because I created the robot accounts using these names. Maybe it fails because they already exist?

Ah! They get the stackable+ prefix from quay. Then it works.

@Techassi Techassi added this pull request to the merge queue May 21, 2026
@Techassi Techassi moved this from Development: In Review to Development: Done in Stackable Engineering May 21, 2026
Merged via the queue into main with commit c0c0410 May 21, 2026
9 checks passed
@Techassi Techassi deleted the ci/publish-to-quay-io branch May 21, 2026 11:12
@Techassi Techassi mentioned this pull request May 21, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dervoeti dervoeti dervoeti approved these changes

Assignees

@Techassi Techassi

Labels

None yet

Projects

Stackable Engineering
Status: Development: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Techassi @dervoeti