Overview

This document contains the consolidated analysis of all Trillium (R1 2026) release notes reviewed against the pipelines-shared-library repository. The goal is to identify deviations from default processes, required configuration changes, and infrastructure adjustments needed in the Rancher environment.

Source: Trillium R1 2026 Release Notes
Jira task: RANCHER-2886
Repository: folio-org/pipelines-shared-library
Last Updated: 2026-04-07 (Complete review including all subpages and links)

Modules Reviewed

#	Module / Area	Source Page	Status

#	Module / Area	Source Page	Status
1	Required manual migrations	Page	✓ Reviewed
2	Modules deployment changes	Page	✓ Reviewed
3	Changes and required actions	Page	✓ Reviewed with all linked pages
4	Platform Changes	Page	✓ Reviewed
5	mod-bulk-operations (Bulk edit)	Notes on functionality	✓ Reviewed
6	mod-orders (Orders)	Notes on functionality	✓ Reviewed
7	mod-eusage (eUsage)	Notes on functionality	✓ Reviewed
8	mod-circulation / ui-requests	Notes on functionality	✓ Reviewed
9	ui-patron-notices	Notes on functionality	✓ Reviewed
10	ui-users	Capability Updates	✓ Reviewed
11	app-serials-management	Capability Updates	✓ Reviewed
12	mod-configuration	Notes on functionality	✓ Reviewed
13	New apps	New apps page	✓ Reviewed
14	Known Issues	Known Issues	✓ Reviewed
15	Important upgrade considerations	Important upgrade considerations	✓ Reviewed
16	Post-Release Hotfixes	Post-Release Hotfixes	✓ Reviewed
17	MARC mapping rules updates	Update details	✓ Reviewed
18	Authority cleanup consortium script	Cleanup script	✓ Reviewed

PRE-MIGRATION ACTIVITIES

Infrastructure Component Upgrades (MUST BE DONE BEFORE MODULE UPGRADES)

1. Opensearch Upgrade (2.x → 3.x) - CRITICAL - P1

Finding: If using Opensearch, upgrade from version 2 to version 3 BEFORE upgrading modules.

Impact: mod-search has been migrated to Opensearch 3.0.0. The new version uses cluster_manager_timeout parameter which is incompatible with older Opensearch versions.

Action Required: 1. Identify current Opensearch version in all environments 2. Plan and execute Opensearch 2.x → 3.x upgrade 3. Verify connectivity and functionality post-upgrade

Action Owner: Infrastructure/DevOps
Priority: P1 (Blocking for Trillium upgrade)
Source: Required manual migrations
Jira: RANCHER-2921

2. MinIO Upgrade to Latest Version - HIGH - P1

WARNING: ***MinIO is deprecated***: https://github.com/minio/minio

Finding: If using MinIO, upgrade to the latest version before module upgrades.

Rationale: MinIO only supports the latest version (support policy).

Action Required: 1. Identify current MinIO version in all environments 2. Upgrade to the latest stable MinIO release 3. Verify S3-compatible storage functionality

Action Owner: Infrastructure/DevOps
Priority: P1 (blocking for Trillium upgrade)
Contact: @Julian Ladisch
Source: Required manual migrations
Jira: RANCHER-2922

3. Kafka Version Verification - MEDIUM - P2

Finding: Kafka must be on a supported version. Apache Kafka supports the latest three minor versions (~1 year support). Amazon MSK supports versions for ~2 years.

Current State: Repository uses Kafka version 4.1.x.kraft in terraform/shared/msk/variables.tf - this appears compliant.

Action Required: 1. Verify Kafka version across all environments (snapshot, testing, production) 2. If any environment uses unsupported Kafka version, upgrade before Trillium deployment

Action Owner: Infrastructure/DevOps
Priority: P2
Contact: @Julian Ladisch
Source: Required manual migrations
Jira: RANCHER-2924

4. Database Permissions for mod-orders-storage Upgrade - CRITICAL - P1

Finding: mod-orders-storage requires temporary cross-module database read access during upgrade from v13 (Sunflower) to v14 (Trillium).

Action Required BEFORE upgrade:

GRANT SELECT ON TABLE ${TENANT}_mod_finance_storage.fiscal_year TO mod_orders_storage_trillium;

Action Required AFTER upgrade:

REVOKE SELECT ON TABLE ${TENANT}_mod_finance_storage.fiscal_year FROM mod_orders_storage_trillium;

Impact: Migration will fail with ERROR: relation "diku_mod_finance_storage.fiscal_year" if not applied.

Action Owner: Database Admin/DevOps
Priority: P1 (blocking for mod-orders-storage upgrade)
Source: Changes and required actions
Reference: MODORDERS-1278

Action item: @Oleksii Petrenko Create Jira for Thunderjet team for triage

Findings Table - Configuration Changes Required

Module	Change Summary	Deviation from Default	Configuration Change Required	Rancher Infra Change Required	Action Owner	Status	Priority

Module	Change Summary	Deviation from Default	Configuration Change Required	Rancher Infra Change Required	Action Owner	Status	Priority
mod-bulk-operations	New FQM integration parameters: `FQM_MAX_CHUNK_SIZE` (default: 10000) and `FQM_MAX_PARALLEL_CHUNKS` (default: 10)	Yes — new env vars must be configured at deployment	Yes — add to `extraEnvVars` in all helm profiles	YES	Rancher/DevOps	MISSING in all profiles	P2
mod-notes	New env var `NOTES_TYPES_DEFAULTS_LIMIT` to configure note type limit (default: 25)	Yes — previously configured per tenant in mod-configuration	Yes — add to `extraEnvVars` if default 25 doesn't suit	YES	Rancher/DevOps	MISSING in all profiles	P2
mod-search	New env var `ELASTICSEARCH_SERVER` to distinguish ES vs Opensearch	Yes — required to support both ES 8 and Opensearch 3	Yes — set to `true` if using ES, `false` or omit for Opensearch	YES	Rancher/DevOps	MISSING in all profiles	P2
mod-circulation	`ENABLE_FOR_USE_AT_LOCATION` env var (default: false)	Already configured	No additional action needed	No	N/A	PRESENT (value: "true")	N/A
mod-marc-migrations	S3 subpath configuration env vars added	Yes — new defaults and subpath config	Yes — add `S3_SUB_PATH` and `S3_LOCAL_SUB_PATH` if custom paths needed	YES	Rancher/DevOps	Review defaults	P3
mod-inventory-storage	S3 subpath config + itemLevelCallNumberTypeId breaking change	Yes — new subpath config + API breaking change	Yes — add `S3_LOCAL_SUB_PATH` if custom path needed	YES	Rancher/DevOps	Review defaults + API validation	P3
mod-entities-links	S3 subpath + `AUTHORITY_EXTENDED` env var moved from mod-inventory	Yes — env var relocation	Yes — move `AUTHORITY_EXTENDED` from mod-inventory to mod-entities-links	YES	Rancher/DevOps	Action required	P2
mod-reporting	Report URL whitelist required in config.json	Yes — security requirement	Yes — update `reportUrlWhitelist` in config.json	YES	Rancher/DevOps	Verify config	P2
mod-configuration	Decommission notice	Yes — module flagged for removal	No immediate action — monitor for decommission milestone	YES (pending)	Rancher/DevOps	Monitor	P3
mod-orders	ISBN validation behavior change	No infra impact — app logic only	No	No	N/A	No action	N/A
mod-eusage	Counter 5.1 support, UI changes	No infra impact	No	No	N/A	No action	N/A
ui-patron-notices	New patron notice token, HTML support	No infra impact	No	No	N/A	No action	N/A
ui-users	Capability renamed	No infra impact — permission migration may be needed	No	No	N/A	No action	N/A
app-serials-management	New capabilities added	No infra impact	No	No	N/A	No action	N/A
ui-inventory-import	New app added	New application requires registration	Yes — register and enable new app	YES	Rancher/DevOps	New app	P2

Infrastructure-Impacting Findings Detail

1. mod-bulk-operations — FQM env vars MISSING (Action Required - P2)

Finding: New FQM-based performance parameters must be configured in all helm profiles.

New parameters:

Parameter	Default Value	Recommended Value	Performance Impact

Parameter	Default Value	Recommended Value	Performance Impact
`FQM_MAX_CHUNK_SIZE`	10000	10000	28.4% improvement
`FQM_MAX_PARALLEL_CHUNKS`	10	10	with optimal config

Current state: MISSING from all helm profiles. Only MAX_UPLOADING_RETRIES: "50" is present.

Files affected: - resources/helm/release.yaml — line 837 - resources/helm/testing.yaml — line 837 - resources/helm/development.yaml — line 767 - resources/helm/performance.yaml — line 837

Required change (add under extraEnvVars):

- name: FQM_MAX_CHUNK_SIZE
  value: "10000"
- name: FQM_MAX_PARALLEL_CHUNKS
  value: "10"

Reference:mod-bulk-operations README#fqm-integration
Jira: Part of RANCHER-2923

2. mod-notes — NOTES_TYPES_DEFAULTS_LIMIT MISSING (Action Required - P2)

Finding: New environment variable to configure note type limit (previously per-tenant config in mod-configuration).

Default: 25

Current state: MISSING from all helm profiles. No extraEnvVars section exists for mod-notes.

Files affected: - resources/helm/release.yaml — line 2983 - resources/helm/testing.yaml — similar location - resources/helm/development.yaml — similar location - resources/helm/performance.yaml — similar location

Required change (add extraEnvVars section if default 25 doesn't suit):

mod-notes:
  extraEnvVars:
  - name: NOTES_TYPES_DEFAULTS_LIMIT
    value: "25"

Reference: MODNOTES-274
Jira: Part of RANCHER-2923

3. mod-search — ELASTICSEARCH_SERVER MISSING (Action Required - P2)

Finding: New environment variable required to distinguish between Elasticsearch and Opensearch deployments.

Current state: MISSING from all helm profiles.

Action Required: - If using Elasticsearch 8: Add ELASTICSEARCH_SERVER: "true" - If using Opensearch 3: Add ELASTICSEARCH_SERVER: "false" or omit the variable

Files affected: All helm profiles at mod-search sections

Required change (for Elasticsearch environments):

- name: ELASTICSEARCH_SERVER
  value: "true"

Trillium (R1 2026) Pre-Release notes analysis