Skip to content

Conversation

@lsierant
Copy link
Contributor

@lsierant lsierant commented Jan 22, 2026

Summary

Reverted a change (introduced in #697) leading to not setting the default operator env when the env var is not validated correctly.

This bug has no impact in our tests as we're always setting OPERATOR_ENV to a correct value.

@lsierant lsierant self-assigned this Jan 22, 2026
@github-actions
Copy link

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.7.0 Release Notes

New Features

  • Allows users to override any Ops Manager emptyDir mount with their own PVCs via overrides statefulSet.spec.volumeClaimTemplates.
  • Added support for auto embeddings in MongoDB Community to automatically generate vector embeddings for the vector search data. This document can be followed for detailed documentation
  • MongoDBSearch: Updated the default mongodb/mongodb-search image version to 0.60.1. This is the version MCK uses if .spec.version is not specified.

Bug Fixes

  • Fix an issue to ensure that hosts are consistently removed from Ops Manager monitoring during AppDB scale-down events.
  • Fixed an issue where monitoring agents would fail after disabling TLS on a MongoDB deployment.
  • Persistent Volume Claim resize fix: Fixed an issue where the Operator ignored namespaces when listing PVCs, causing conflicts with resizing PVCs of the same name. Now, PVCs are filtered by both name and namespace for accurate resizing.
  • Fixed a panic that occurred when the domain names for a horizon was empty. Now, if the domain names are not valid (RFC 1123), the validation will fail before reconciling.
  • MongoDBMultiCluster, MongoDB: Fix an issue where the operator skipped host removal when an external domain was used, leaving monitoring hosts in Ops Manager even after workloads were correctly removed from the cluster.
  • Fixed an issue where the Operator could crash when TLS certificates are configured using the certificatesSecretsPrefix field without additional TLS settings.

@lsierant lsierant added the skip-changelog Use this label in Pull Request to not require new changelog entry file label Jan 22, 2026
@lsierant lsierant marked this pull request as ready for review January 22, 2026 12:52
@lsierant lsierant requested a review from a team as a code owner January 22, 2026 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog Use this label in Pull Request to not require new changelog entry file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants