2026.36 Infrastructure Changes

1 min read

Changes on Application environment

Change	Environment Variable Name	Application Default Value (if env variable unset)	Example	Required	Applications	Short Description
Added	`UNIQUE_API_URL`	-	`http://unique-api.<namespace>.svc.cluster.local`	true (from `.36`)	`backend-service-chat`	In-cluster base URL of the `unique-api` service. `backend-service-chat` forwards the Unique API domains that are live in the current release to this URL. If it is unset, those requests fail with `502` — they do not fall back to the legacy implementation.
Added	`FEATURE_FLAG_ENABLE_SKILL_VERSION_HISTORY_UN_23881`	`false`	`true`	false	`backend-service-configuration`	Enables version history for skill files.
Added	`FEATURE_FLAG_AGENTIC_TABLE_BULK_ACTIONS_UN_23981`	`false`	`true`	false	`backend-service-configuration`	Enables bulk actions (e.g. status, assignee, re-run and delete) for Agentic Tables
Removed	`FEATURE_FLAG_AGENTIC_TABLE_ERROR_BANNER_UN_11777`	-	-	-	`backend-service-configuration`	Error banner feature is now GA. The sheet now always shows an error banner when the space configuration is invalid or when the agent fails while processing.
Moved	`FEATURE_FLAG_ENABLE_WEB_SEARCH_ARGUMENT_SCREENING_UN_18741`	`false`	`true`	false	`backend-service-configuration` `ai-service-assistants-core`	Web search argument screening now resolves through `backend-service-configuration` instead of environment variable alone in `ai-service-assistants-core`
Removed	`FEATURE_FLAG_USER_API_KEY_GENERATION_UN_11416`	-	-	-	`backend-service-configuration`	The feature flag was converted to the environment setting `USER_API_KEY_GENERATION_ENABLED` set on all frontend applications (`web-app-chat`, `web-app-knowledge-upload`, `web-app-admin`, `web-app-theme`)
Removed	`FEATURE_FLAG_NET_PROMOTER_SCORE_UI_UN_7747`	-	-	-	`backend-service-configuration`	The feature flag was converted to the environment setting `NET_PROMOTER_SCORE_UI_ENABLED` set on `web-app-chat`

Service dependencies

From .36 the Unique API rollout begins enabling one API domain per even release. backend-service-chat continues to receive all /public/chat traffic and forwards the domains that are live to unique-api internally.

unique-api must be deployed and running in every environment from .36 onward. The first domain to move is Identity & access: /users, /groups, /company.
New in-cluster egress path: backend-service-chat → unique-api (service port 80, pod port 8096). Where NetworkPolicies are enforced, this dependency has to be allowed, otherwise the forwarded requests are blocked and the affected routes fail with 502.

Rollout background and per-domain order: Unique API Rollout.