Why do platform services fail to start after activating or deactivating maintenance mode, resulting in a 503 Service Not Available error and Webhook services in CrashLoopBackOff?
Issue Description:
The platform services fail to start after activating or deactivating maintenance mode
1.) “auth-oauth2-proxy-7d6b7b6c94-kngrh” namespace=uipath-auth
2.) “platform-services-initialize-default-organization-job-xzdz6” namespace=uipath
it looks that is missing from main-gateway.yaml
spec:
selector:
istio: ingressgateway
Resolution:
kubectl edit gateway -A -o yaml
add
spec:
selector:
istio: ingressgateway
Then rollout restart all deployments
kubectl get namespaces --no-headers=true | awk '{print $1}' | xargs -I {} kubectl rollout restart deployment --namespace={}
The issue was resolved by modifying the gateway configuration and restarting deployments across namespaces. This action restored access to the GUIs and resolved the service availability problem. The solution was implemented by the Support Engineer.