Skip to content

Conversation

@viveksinghggits
Copy link
Contributor

@viveksinghggits viveksinghggits commented Dec 2, 2025

Summary

We have been getting some request from the customers where they wanted to know the combination of the container images that they require to run a specific version of operator and Mongo DB instance. As part of that work we are going to add a new file (release_info.json) as the assets in the GitHub release.
That file is going to have details about the latest released images. These images are going to be the images that MCK publishes as well as the latest OM and Agent version mappings. To enable that, as part of this PR we are adding a new field in the release.json that has the mapping between OM version and agent version of latest OM releases. This new field in the release.json is going to have the opsManaget to agent image version mapping for every major opsmanager version.
We are adding this information in the release.json so that it can easily be used later (in next PR), to create the release_info.json file.
This PR also updated the precommit hook so that when new version of OM is released, the newly added field of release.json would properly be updated with newly release OM/agent.

Proof of Work

Manual:

  • Mimic new release of OM by adding a new version (8.0.17) to supportedImages.ops-manager.versions and respective entry in mongodb-agent.opsManagerMapping. Run make precommit and verify that the supportedImages.latestOpsManagerAgentMapping has been updated for major version 8 with updated versions.
  • Mimic the new major version release of OM by adding new version (9.0.1) to supportedImages.ops-manager.versions and respective entry in mongodb-agent.opsManagerMapping. Run make precommit and verify that a new entry for major version 9 has been added to supportedImages.latestOpsManagerAgentMapping.

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you added changelog file? (will show up later)

@github-actions
Copy link

github-actions bot commented Dec 2, 2025

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

MCK 1.6.1 Release Notes

Bug Fixes

  • Backed up the agent password in a secret for SCRAM authentication to prevent unnecessary password rotations.

1. Move mapping field in json to root level
2. Change log lever for logs
Copy link
Collaborator

@MaciejKaras MaciejKaras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Member

@mircea-cosbuc mircea-cosbuc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this approach, LGTM!

@viveksinghggits viveksinghggits merged commit c97c7a0 into master Dec 5, 2025
33 of 37 checks passed
"search": {
"version": "0.55.0"
},
"latestOpsManagerAgentMapping": [
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you think we can replace the existing code here to use what you've implemented here?

func newAgentVersionManager(omVersionToAgentVersion map[omv1.OpsManagerVersion]omv1.AgentVersion, cmVersion string) *AgentVersionManager {
omVersionsByMajor := make(map[string]string)
if cmVersion == "" {
zap.S().Warnf("No version provided for Cloud Manager agent")
}
for omVersion := range omVersionToAgentVersion {
majorOmVersion := getMajorVersion(string(omVersion))
if currentVersion, exists := omVersionsByMajor[majorOmVersion]; !exists || isLaterVersion(string(omVersion), currentVersion) {
omVersionsByMajor[majorOmVersion] = string(omVersion)
}
}
return &AgentVersionManager{
omToAgentVersionMapping: omVersionToAgentVersion,
latestOMVersionsByMajor: omVersionsByMajor,
agentVersionCM: cmVersion,
}
}

@viveksinghggits viveksinghggits deleted the latest-om-agent-mapping branch December 5, 2025 13:51
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.

5 participants