Reprovisioning a managed controller to enable or disable HA does not update Ingress sticky session configuration

Last Reviewed:2026-11-02()
1 minute readKnowledge base

Issue

If you are using Ingress and use the Reprovision button to enable or disable High Availability (active/active) on an existing managed controller, the Ingress resource is not re-created. The Ingress resource is left without the sticky session annotations required for HA when HA is enabled, or with stale sticky session annotations when HA is disabled. This issue does not affect deployments that use Gateway API, because the HTTPRoute resource is re-created in both situations.

Environment

Resolution

This issue is resolved in CloudBees CI version 2.580.2.38434.

Workaround

If you are using Ingress and are enabling or disabling HA on an existing managed controller, do not use the Reprovision button. Instead, use Deprovision and then Start to ensure the Ingress resource is re-created with the correct sticky session annotations.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.