[Ulmo / Tutor 21.0.6] Exact component versions for production infrastructure planning?

Site Operators
, , ,
1

Hi Everyone,

I am setting up a production Open edX deployment on Microsoft Azure using Tutor tutor[full]==21.0.6 (Ulmo release) on Kubernetes. As part of a formal IT infrastructure review and approval process, I need to document the exact pinned versions of every underlying service and component that ships with this Tutor version — not just approximate ranges (e.g., “MySQL 8.x”).

Services & Components — Version Information Needed

Please help fill in the exact versions for each of the following components:

# Component / Service Category Version Needed
1 MySQL Database Exact version?
2 MongoDB Database Exact version? (or removed in Ulmo?)
3 Redis Cache Exact version?
4 Meilisearch Search Exact version?
5 Caddy Web / Proxy Exact version?
6 Nginx Web / Proxy Exact version? (if applicable)
7 Docker Containerization Exact version?
8 Docker Compose Containerization Exact version?
9 Kubernetes (kubectl) Orchestration Exact / min supported version?
10 Helm Orchestration Exact version? (if applicable)
11 Python Runtime Exact version?
12 Django Framework Exact version?
13 Node.js Runtime Exact version?
14 React.js Frontend Exact version?
15 Azure CLI Cloud Tooling Exact version?
16 tutor[full] plugins LMS Platform All bundled extras & versions

I am aware that some of this can be found by inspecting Tutor’s source or running the commands below:

  • tutor config printroot
  • docker-compose.yml
  • tutor images list

However, since we are going through a formal infrastructure provisioning and security review, we need these versions documented authoritatively rather than inferred at runtime.

If anyone has already gone through a similar enterprise review or compliance process for Ulmo on Kubernetes, I’d also appreciate any guidance or best practices around documenting the infrastructure stack for audit/security teams.

Any pointers to:

  • official Tutor/Open edX release notes,
  • source files containing pinned versions,
  • Helm chart references,
  • or deployment documentation

would be extremely helpful.

Thanks in advance for your help!

2

Hi Mahendra,

A few things to clarify before diving into the table, this will help frame what Tutor can authoritatively answer vs. what’s environment-dependent.

Tutor doesn’t ship a single “version manifest.” Component versions live in three different places, and only the first is owned by Tutor itself:

1. Service images Tutor builds/pulls

This includes MySQL, MongoDB, Redis, Meilisearch, Caddy, Nginx, Elasticsearch, etc.

These are pinned in the Tutor source at the release tag.

For Tutor, the authoritative references are:

2. edx-platform internals

This includes:

  • Django
  • Python runtime inside the LMS/CMS image
  • Node.js used for asset builds
  • React/MFE dependencies

These are pinned by the openedx/edx-platform open-release/ulmo.master branch, not by Tutor.

3. Host-side tooling

This includes:

  • Docker
  • Docker Compose
  • Kubernetes
  • Helm
  • Azure CLI
  • kubectl

These are not pinned by Tutor.

They are whatever you install on your control host or cluster. Tutor documents some minimum supported versions in the requirements doc:

However, the exact version you run is your choice and should be governed by your own infrastructure standards.

For the compliance artifact you need, I’d recommend generating it from a clean checkout/build rather than from this thread. Versions can shift across patch releases.

Happy to clarify any specific row in your table if you hit ambiguity.

3

Thanks @Ahmed_Khalid

This information is very helpful and much appreciated.