Score:0

Why do my AKS node have public IP even though "enableNodePublicIP" is set to false?

in flag

I have an AKS cluster where I added a new node pool. While creating the node pool, I set the option "Enable public IP per node" as Disabled. However, I still notice that my nodes in the VMSS have a public IP. I am looking for a possible explanation of where does it come from?

Additional Info:

  1. In the kubectl get nodes -o wide, I only see INTERNAL-IP and there's no EXTERNAL-IP.
  2. When I try to make a connection with the node's public IP on port 443, it is reachable.
Score:0
gr flag

It has been sometime, but have you found the cause? If there is only one IP for all of your nodes then that might just be the outbound IP for your AKS cluster.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.