2025.26 Infrastructure Changes

1 min read


Changes on Application environment

Change

Name

Default

Example

Required

Applications

Short Description

Added

FEATURE_FLAG_ENABLE_EXPAND_HIGHLIGHT_RANGE_UN_11265

"false"

”true”

No

node-ingestion-worker

This is used to improve DOCX highlighting accuracy by expanding the highlighted page range by one.

Used especially for contents that spans multiple page.

Added

FEATURE_FLAG_ENABLE_CAN_MANAGE_ACCESS_UN_11608

"false"

"true"

No

  • knowledge-upload

  • node-scope-management

This is used to enable the “Can Manage” access features in knowledge base. See details Folder access management

Removed

FEATURE_FLAG_PERMISSION_PROPAGATION_KB_UN_11168

  • next-knowledge-upload

Replace by FEATURE_FLAG_ENABLE_CAN_MANAGE_ACCESS_UN_11608 (see above)

Added

FEATURE_FLAG_NEW_SOURCE_REFERENCES_UN_10906

"false"

No

next-chat

Improved source reference UI

Changed

FEATURE_FLAG_USER_API_KEY_GENERATION_UN_11416

"true"

No

  • next-chat

  • next-knowledge-upload

  • next-theme

  • next-admin

This feature flag enables a user to generate a personal API key to use across all the apps.

APP_REPOSITORY_BACKEND_API_URL must be set for this feature to work.

New kong-plugins Helm Chart available

This change is mandatory for clients that use the SDK / Public API. A new Unique Helm Chart for kong-plugins has been released, addressing a critical bug related to the use of company-scoped API keys. The bug caused errors when calling any public endpoint with a company-scoped API key. Please ensure this update is applied promptly to avoid disruptions.

Check the changes on Artifact Hub: https://artifacthub.io/packages/helm/unique/kong-plugins

Steps

  1. Upgrade the kong-plugins to 1.2.1.

  2. Deploy the changes.

  3. Verify the fix by calling SDK/public API endpoints using the API key and observing a successful response.

Elasticsearch

For all Elasticsearch related Infrastructure Changes please review Infra Admins Elasticsearch Infrastructure.

Last updated