When following the steps in the Azure Kubernetes Service documentation to update/rotate the Service Principal, one of the steps carried out by the CLI utility involves restarting each Node in the cluster in a rolling fashion, I think twice per node. This caught me out by surprise the first time I rotated the keys on a cluster.
We use AKS to run a platform which relies on persistent TCP connections being formed from customer sites to AKS. If the node running that particular pod reboots (or indeed that pod restarts), the customer sites would automatically (re) connect to another node, but with the side effect of closing all sessions that customer might have open.
Completely appreciate this may not be possible but I'm wondering if there is a method to rotate the Service Principal in AKS without rebooting? Cheers!