Modifying Automation Suite Deployments, As Istio Excludes Outbound Ports

News Knowledge Base
1

How to modify an Automation Suite deployment, so Istio excludes certain ports?

For situations in which troubleshooting has found that istio is blocking outbound ports, it is required to modify the product's deployment.

  1. Login to the server node
  2. This activity requires sudo access, hence grant the root control to the user performing the same
  3. Create a custom file: 
vim script.sh
  1. Paste the below content:
for deployment in $(kubectl -n uipath get deploy | grep (REPLACE WITH DEPLOYMENT TYPE ORCHESTRATOR,INSIGHTS,etc) | awk '{print $1}'); do
echo "Annotating deployment ${deployment}..."
kubectl -n uipath get deployment $deployment -oyaml > "${deployment}.yaml"
kubectl -n uipath patch deployment $deployment -p '{"spec":{"template":{"metadata":{"annotations":{"traffic.sidecar.istio.io/excludeOutboundPorts":"REPLACE WITH PORT NUMBER"}}}}}'
done

  1. Grant execute permission to the user:
chmod +x script.sh
  1. Execute the following:
./script.sh
  1. The outcome should look like the below,

    image.png