Skip to content

chore: pin mysql-operator source refs to the v0.8.0 tag - #33

Merged
drivebyer merged 3 commits into
mainfrom
chore/pin-operator-ref
Jul 14, 2026
Merged

drivebyer merged 3 commits into
mainfrom
chore/pin-operator-ref

Conversation

@drivebyer

Copy link
Copy Markdown
Contributor

Why

Five Dockerfiles pulled mysql-operator sources from the floating extra_image branch head, so the binaries baked into an image were not traceable to a commit and builds were not reproducible. extra_image is also being retired as the mysql-operator trunk (moving to main, with master restored as the upstream mirror — see ksmartdata/mysql-operator#21).

Per this repo's own policy (scripts/check-dockerfile-source.sh: no code pulls from branch heads), the refs are pinned to the v0.8.0 tag instead of being renamed to the new branch. check-dockerfile-source.sh passes on all Dockerfiles after this change.

What

  • mysql-operator-sidecar-5.7 / mysql-operator-sidecar-8.0 / mysql-operator-sidecar-8.0/Dockerfile.base: introduce ARG OPERATOR_REF=v0.8.0 and download archive/${OPERATOR_REF}.zip (works with tags, branches, and commits; the unzip dir is normalized with a wildcard mv)
  • mysql-operator-sidecar-8.4: ARG OPERATOR_REF default extra_image → v0.8.0 (both stages)
  • mgr-operator: ARG MYSQL_OPERATOR_EXTRA_IMAGE_REF default extra_image → v0.8.0 (ARG name kept for dispatch compatibility)

Releasing a new operator version is now: tag mysql-operator → bump the default here (or pass build-args at dispatch).

The PR CI rebuild of the changed image directories is expected.

@drivebyer
drivebyer merged commit 0960473 into main Jul 14, 2026
15 checks passed
@drivebyer
drivebyer deleted the chore/pin-operator-ref branch July 14, 2026 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant