Repository navigation
chore: point default images and chart distribution at ksmartdata - #25
Merged
Merged
Conversation
…ore/point-defaults-at-ksmartdata
…at-ksmartdata # Conflicts: # README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
After detaching from the bitpoke fork network, several functional defaults still pointed at bitpoke infrastructure: default sidecar images pulled from docker.io/bitpoke (which no longer receives our fixes), the helm chart installed upstream images, the README install instructions deployed the upstream operator, and the Makefile published charts to bitpoke/helm-charts. The README also carried a lot of stale upstream content (marketing paragraphs, ancient upgrade notes, a dead
docs/operator-upgrades.mdlink, an abandoned roadmap).What
pkg/options/options.go): 5.7/8.0 now default toghcr.io/ksmartdata/*, matching the already-migrated 8.4 sidecar.values.yaml, chart metadata (description, keywords, home, sources, artifacthub image list — now including the 8.4 sidecar), and the chart README all point at ksmartdata. The chart is not published anywhere for now; it is installed straight from the repository (helm install mysql-operator deploy/charts/mysql-operator).make .helm.publishis kept as a manual OCI-push path for the future.DOCKER_REGISTRYdefaults toghcr.io/ksmartdata; local e2e image defaults moved off the inaccessibleeu.gcr.io/bitpoke-mysql-operator-testingregistry..drone.yml; our CI is GitHub Actions) and the PR-template checkbox linking to the unmaintained presslabs CHANGELOG.This branch includes #24 (merged in to avoid README conflicts); its diff will disappear from this PR once #24 lands.
Intentionally left unchanged: the Go module path, the
mysql.presslabs.orgCRD API group (changing it would break every existing cluster), FUNDING.yml and bitpoke.io documentation links (attribution / still-valid upstream docs), and historical CHANGELOG references.Verified with
go build ./cmd/... ./pkg/...,helm lint deploy/charts/mysql-operator, and a repo-wide grep for remainingdocker.io/bitpoke/eu.gcr.io/bitpoke/helm-charts.bitpokereferences (none outside vendored/historical content).