DEVPROD-4558 Stop pushing to vectorized and repoint to correct dockerhub - #1807
Merged
Conversation
PrzemekZglinicki
requested review from
RafalKorepta,
andrewstucki,
chrisseto,
gene-redpanda and
hidalgopl
as code owners
September 2, 2026 21:18
|
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
PrzemekZglinicki
requested review from
RafalKorepta
and
a lite review from Copilot
and removed request for
RafalKorepta,
andrewstucki,
chrisseto,
gene-redpanda and
hidalgopl
September 2, 2026 21:22
There was a problem hiding this comment.
🟢 Approval recommended
Only a minor changelog typo/formatting issue was found; the functional changes are consistent and self-contained.
Pull request overview
Removes publishing of the operator image to the private docker.io/vectorized/* namespace and updates in-repo references (CI, kustomize configs, samples, and tests) to use the redpandadata/* Docker Hub namespace instead.
Changes:
- Stop pushing
docker.io/vectorized/redpanda-operatorin thepublish-operator-imageCI task. - Repoint operator kustomize configs and sample manifests from
vectorized/*toredpandadata/*. - Update test fixtures/comments that referenced
vectorized/*Docker Hub tags.
File summaries
| File | Description |
|---|---|
| taskfiles/ci.yml | Drops the vectorized tag from the operator image publish step. |
| operator/pkg/resources/statefulset_test.go | Updates configurator image references from vectorized/redpanda-data to redpandadata. |
| operator/pkg/resources/resource_integration_test.go | Updates configurator base image reference to redpandadata. |
| operator/pkg/resources/featuregates/featuregates_test.go | Updates Docker Hub reference URLs in comments to redpandadata. |
| operator/internal/controller/vectorized/test/suite_test.go | Updates configurator base image reference to redpandadata. |
| operator/config/samples/tls.yaml | Repoints Redpanda sample image to redpandadata/redpanda. |
| operator/config/samples/sasl.yaml | Repoints Redpanda sample image to redpandadata/redpanda. |
| operator/config/samples/one_node_external.yaml | Repoints Redpanda sample image to redpandadata/redpanda. |
| operator/config/samples/mtls.yaml | Repoints Redpanda sample image to redpandadata/redpanda. |
| operator/config/samples/external_connectivity.yaml | Repoints Redpanda sample image to redpandadata/redpanda. |
| operator/config/samples/console.yaml | Repoints Console sample image to redpandadata/console. |
| operator/config/manager/manager.yaml | Updates the manager image reference to redpandadata/redpanda-operator. |
| operator/config/manager/kustomization.yaml | Updates kustomize image name/newName to redpandadata/redpanda-operator. |
| operator/config/e2e-tests/kustomization.yaml | Updates e2e kustomize image match name to redpandadata/redpanda-operator (so localhost override still applies). |
| .changes/unreleased/operator-Changed-20260902-131640.yaml | Adds a changelog entry describing the publishing/reference update. |
Review details
- Files reviewed: 15/15 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
publish-operator-image pushed the release image to both docker.io/vectorized/redpanda-operator and docker.io/redpandadata/redpanda-operator. The vectorized repository is private and nothing has pulled from it since February 2025, so every release has been publishing into a namespace no consumer can reach. redpandadata is the namespace consumers actually pull from. Dropping the tag changes nothing for consumers: every repository in the vectorized namespace is private, so nothing outside CI could pull from there in the first place.
PrzemekZglinicki
force-pushed
the
devprod-4558-stop-pushing-to-vectorized
branch
from
September 2, 2026 21:29
603dc04 to
cedfb9a
Compare
There was a problem hiding this comment.
🟡 Changes recommended
The Console sample changes from a pinned image tag to :latest, which is a semantic change beyond namespace repointing and should be addressed for determinism/reproducibility.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 15/15 changed files
- Comments generated: 1
- Review effort level: Lite
RafalKorepta
reviewed
Sep 3, 2026
RafalKorepta
left a comment
RafalKorepta
left a comment
Contributor
There was a problem hiding this comment.
Drop the change log entry and add no-changelog github PR label
PrzemekZglinicki
force-pushed
the
devprod-4558-stop-pushing-to-vectorized
branch
from
September 3, 2026 08:27
cedfb9a to
a57d95f
Compare
RafalKorepta
approved these changes
Sep 3, 2026
RafalKorepta
enabled auto-merge (rebase)
September 3, 2026 09:45
The kustomize deploy tree, the samples and the configurator test fixtures
still named the vectorized/* Docker Hub namespace, which is private.
config/manager/{kustomization,manager}.yaml and
config/e2e-tests/kustomization.yaml have to move together. Both select the
manager image by name, and kustomize silently ignores an images entry
whose name no longer matches. Renaming the manager default alone leaves
the e2e-tests entry dangling, so e2e stops using the locally built
localhost/redpanda-operator:dev and fails to pull instead.
manager.yaml keeps :latest to match what the images transformer directly
above it produces. That literal is overwritten by the transformer, so its
value never reaches a cluster; pinning a release tag there would go stale
every release for a value nothing reads.
console.yaml pins redpandadata/console:v2.8.16, the newest published v2.x
and the schema this legacy Console CR models. The tag it carried,
master-173596f, was never published under redpandadata, and unlike
manager.yaml this value is the CR's actual image with nothing overriding
it, so it should be deterministic.
Left alone: the vectorized/redpanda strings that remain as tag-parsing
and status fixtures in envtest suites, where nothing pulls, and the
redpanda.vectorized.io API group and internal/controller/vectorized
package, which are unrelated to Docker Hub.
PrzemekZglinicki
force-pushed
the
devprod-4558-stop-pushing-to-vectorized
branch
from
September 3, 2026 12:37
a57d95f to
095a793
Compare
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.
Refs: https://redpandadata.atlassian.net/browse/DEVPROD-4558
Companion: redpanda-data/cloudv2-infra#3816
What
publish-operator-imagepushed every release to bothdocker.io/vectorized/redpanda-operatorand
docker.io/redpandadata/redpanda-operator. Thevectorizedrepo is private, last pulled2025-02-21. This drops that tag and repoints the remaining
config/and sample references.No consumer impact: nothing outside CI could pull from
vectorized, and every released operatoralready defaults to
docker.redpanda.com/redpandadata/redpanda-operator.config/manager/andconfig/e2e-tests/kustomization.yamlhave to move together — both selectthe manager image by name, and kustomize silently ignores an
imagesentry that no longermatches, so renaming one alone makes e2e stop using
localhost/redpanda-operator:dev.Known, accepted
config/defaultrendersredpandadata/redpanda-operator:latest, which isn't published. Not aregression, and nothing consumes that overlay.
vectorized/redpandastrings remain as envtest fixtures — nothing pulls there.ci/scripts/install-task.sh:14usesvectorized-public.s3…— not Docker Hub, out of scope.