In UiPath Automation Suite, external transport security and reverse-proxy ingress routing are managed by an Istio-based service mesh. The Istio Ingress Gateway handles incoming HTTPS connections directed to the platform Fully Qualified Domain Name (FQDN). To terminate TLS/SSL traffic, the ingress gateway controller reads the public certificate hierarchy and private key directly from a designated Kubernetes Secret. By default and per technical standards, this Secret is maintained within the `istio-system` namespace under the exact name `istio-ingressgateway-certs`. During post-installation certificate renewals or rotations, administrators replace or update this specific Secret to apply updated certificates across all edge endpoints without requiring downtime. Storing certificates outside `istio-system` or using non-standard naming prevents the ingress gateway pod from mounting the TLS secret volumes, causing ingress handshake terminations. (Reference: UiPath Automation Suite Infrastructure and Network Configuration – Ingress and Istio Certificate Management).
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit