Skip to content

Publish vikunja image to Harbor (ETH-2812 registry migration) - #1

Merged
elasticroentgen merged 1 commit into
mainfrom
eth-2812-harbor
Nov 10, 2026
Merged

elasticroentgen merged 1 commit into
mainfrom
eth-2812-harbor

Conversation

@elasticroentgen

Copy link
Copy Markdown
Member

Part of ETH-2812: migrate in-house images from ghcr.io/ethdevops to Harbor.

The image is now published to docker.ethquokkaops.io/ethquokkaops/ethdevops/vikunja and no longer pushed to ghcr.

How

The build job is unchanged except for the registry target and the login, which is now an OpenBao JWT.

Login uses a short-lived JWT from the OpenBao ci scope of this repo's project (JWT role + docker-registry push robot created in internal-stack-iac commit cb87fd757).

Prerequisite

internal-stack-iac cb87fd757 (OpenBao ci scope, JWT role, push robot) must be applied before the first build — until then the workflow's registry login fails.

After merge

  • push to main to re-publish unstable.
  • Consumers switch to the Harbor images in the follow-up PRs (internal-stack-iac / helm-charts, same branch name eth-2812-harbor). All currently-running tags are already backfilled in Harbor.

Swap the ghcr.io GITHUB_TOKEN login for an OpenBao JWT login (role
ethquokkaops-vikunja-ci, bound to this workflow file) and publish to
docker.ethquokkaops.io/ethquokkaops/ethdevops/vikunja with the robot-vikunja
credential.

Also add a bare 7-char short-SHA tag (type=sha,format=short) so
argocd-image-updater can track builds with updateStrategy: newest-build and
allowTags: ^[0-9a-f]{7}$.

Requires: the ethquokkaops-vikunja-ci JWT role and robot-vikunja in
internal-stack-iac.
@elasticroentgen elasticroentgen added the enhancement New feature or request label Nov 10, 2026
@elasticroentgen
elasticroentgen merged commit d9f7a0b into main Nov 10, 2026
36 of 38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant