Skip to content

Setup container image publishing#102

Open
SuperQ wants to merge 1 commit intovalkey-io:mainfrom
SuperQ:superq/container_build
Open

Setup container image publishing#102
SuperQ wants to merge 1 commit intovalkey-io:mainfrom
SuperQ:superq/container_build

Conversation

@SuperQ
Copy link
Copy Markdown
Contributor

@SuperQ SuperQ commented Mar 2, 2026

Add a GitHub Actions workflow to build and publish container images.

Add a GitHub Actions workflow to build and publish container images.

Signed-off-by: SuperQ <superq@gmail.com>
# id: meta
# uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
# with:
# images: valkey/valkey-operator
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@stockholmux Is there somewhere we can publish the container images to?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I saw that Valkey has a Docker Hub account. So it should be possible to either add secrets access to this repo via GH org controls.

Or we can create a separate account that has push access to valkey/valkey-operator on Docker Hub.

I did a quick browse of the upstream valkey, I didn't see a GitHub action for publishing official builds there.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The repo handling build & uploads for core Valkey is valkey-release-automation.
You should take a look at the valkey-bundle repo. It seems their steps are applicable to ours

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants