fix: update testkube MongoDB image tag from 8.0.15 to 8.2.5#1641
Merged
zanejohnson-azure merged 1 commit intoci_prodfrom Apr 10, 2026
Merged
fix: update testkube MongoDB image tag from 8.0.15 to 8.2.5#1641zanejohnson-azure merged 1 commit intoci_prodfrom
zanejohnson-azure merged 1 commit intoci_prodfrom
Conversation
The 8.0.15 tag has been removed from the upstream Testkube registry (us-east1-docker.pkg.dev/testkube-cloud-372110/testkube/mongodb), causing ImagePullBackOff on nodes without cached images. Update to 8.2.5 which is the current default for Testkube chart 2.8.3.
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
suyadav1
approved these changes
Apr 10, 2026
22 tasks
zanejohnson-azure
added a commit
to Azure/prometheus-collector
that referenced
this pull request
Apr 11, 2026
[comment]: # (Note that your PR title should follow the conventional commit format: https://conventionalcommits.org/en/v1.0.0/#summary) # PR Description see microsoft/Docker-Provider#1641 [comment]: # (The below checklist is for PRs adding new features. If a box is not checked, add a reason why it's not needed.) # New Feature Checklist - [ ] List telemetry added about the feature. - [ ] Link to the one-pager about the feature. - [ ] List any tasks necessary for release (3P docs, AKS RP chart changes, etc.) after merging the PR. - [ ] Attach results of scale and perf testing. [comment]: # (The below checklist is for code changes. Not all boxes necessarily need to be checked. Build, doc, and template changes do not need to fill out the checklist.) # Tests Checklist - [ ] Have end-to-end Ginkgo tests been run on your cluster and passed? To bootstrap your cluster to run the tests, follow [these instructions](/otelcollector/test/README.md#bootstrap-a-dev-cluster-to-run-ginkgo-tests). - Labels used when running the tests on your cluster: - [ ] `operator` - [ ] `windows` - [ ] `arm64` - [ ] `arc-extension` - [ ] `fips` - [ ] Have new tests been added? For features, have tests been added for this feature? For fixes, is there a test that could have caught this issue and could validate that the fix works? - [ ] Is a new scrape job needed? - [ ] The scrape job was added to the folder [test-cluster-yamls](/otelcollector/test/test-cluster-yamls/) in the correct configmap or as a CR. - [ ] Was a new test label added? - [ ] A string constant for the label was added to [constants.go](/otelcollector/test/utils/constants.go). - [ ] The label and description was added to the [test README](/otelcollector/test/README.md). - [ ] The label was added to this [PR checklist](/.github/pull_request_template). - [ ] The label was added as needed to [testkube-test-crs.yaml](/otelcollector/test/testkube/testkube-test-crs.yaml). - [ ] Are additional API server permissions needed for the new tests? - [ ] These permissions have been added to [api-server-permissions.yaml](/otelcollector/test/testkube/api-server-permissions.yaml). - [ ] Was a new test suite (a new folder under `/tests`) added? - [ ] The new test suite is included in [testkube-test-crs.yaml](/otelcollector/test/testkube/testkube-test-crs.yaml).
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
2 participants
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.
test cluster ci-logs-prod-aks-work-load-identity fails due to testkube mongoDB image pullback error
https://ms.portal.azure.com/#view/Microsoft_Azure_ContainerService/AksK8ResourceMenuBlade/~/overview-Deployment/aksClusterId/%2Fsubscriptions%2F9b96ebbd-c57a-42d1-bbe9-b69296e4c7fb%2FresourceGroups%2Fci-logs-prod-aks%2Fproviders%2FMicrosoft.ContainerService%2FmanagedClusters%2Fci-logs-prod-aks-work-load-identity/resource~/%7B%22kind%22%3A%22Deployment%22%2C%22metadata%22%3A%7B%22name%22%3A%22testkube-mongodb%22%2C%22namespace%22%3A%22testkube%22%2C%22uid%22%3A%22d7bea9b8-caff-4c7b-a377-66ff6b9331bb%22%7D%2C%22spec%22%3A%7B%22selector%22%3A%7B%22matchLabels%22%3A%7B%22app.kubernetes.io%2Fcomponent%22%3A%22mongodb%22%2C%22app.kubernetes.io%2Finstance%22%3A%22testkube%22%2C%22app.kubernetes.io%2Fname%22%3A%22mongodb%22%7D%7D%7D%7D/preloadK8sObjectsO11yContext~/%7B%22useUpgradedTier%22%3Atrue%2C%22isK8sObjectsOverviewO11yEnabled%22%3Atrue%7D
The 8.0.15 tag has been removed from the upstream Testkube registry (us-east1-docker.pkg.dev/testkube-cloud-372110/testkube/mongodb), causing ImagePullBackOff on nodes without cached images. Update to 8.2.5 which is the current default for Testkube chart 2.8.3.
evidence
$ docker manifest inspect us-east1-docker.pkg.dev/testkube-cloud-372110/testkube/mongodb:8.0.15
no such manifest: us-east1-docker.pkg.dev/testkube-cloud-372110/testkube/mongodb:8.0.15
$ docker manifest inspect us-east1-docker.pkg.dev/testkube-cloud-372110/testkube/mongodb:8.2.5
{
"schemaVersion": 2,
"mediaType": "application/vnd.oci.image.index.v1+json",
"manifests": [
{