gopaddle User Guide
  • πŸ‘‹Welcome to gopaddle
  • Overview
    • πŸ’‘Getting Started
    • Register a Cluster
      • Register Rancher Prime - RKE2
      • Register K3S
      • Register MicroK8s
      • Register Kind
      • Register minikube
      • Register Kubeadm Cluster
      • Register AWS EKS Cluster
        • EKS Cluster with public or public/private access point
        • EKS Cluster with private access endpoint and a bastion host
        • Validate Cluster Connectivity
      • Register Azure AKS Cluster
      • Register Google GKE Cluster
      • Register Huawei Cloud Container Engine
    • Register GitHub Account
    • Register Jira Account
    • Register ChatGPT Assistant
    • πŸ’»Kubernetes IDE
      • Filters
      • Editor
      • Flat vs Tree View
      • Developer Tools
    • πŸ™‹AI Assistant
      • Chat with AI
      • Raise a Jira Ticket from Chat Window
      • Create Runbook from Chat Window
    • πŸ“–Runbook Hub
      • Create Runbook Hub
      • Attach Runbook Hub to Cluster
      • Enhancing contents of Runbooks with AI
      • Detach Runbook Hub from Cluster
      • Syncing Runbook Hub with GitHub
      • Delete Runbook / Runbook Hub
    • ⏱️Installing Community Edition
      • MicroK8s Addon
        • On Ubuntu
        • On MacOS
      • Docker Desktop
      • SUSE Rancher Prime
      • Digital Ocean
      • Akamai Linode
      • Kind Cluster
      • Helm
      • Docker Compose
      • Accessing gopaddle UI
    • πŸ“ˆImproving performance of resource discovery
    • Provision new Cluster
      • Register Cloud Account
        • AWS
          • Quickstart AWS Setup
          • IAM Access Policies
          • AWS Setup Script
        • Azure
          • Create Azure Application
          • Register Azure Cloud Authenticator
          • Register Azure Account
        • Google
      • Provision Clusters on Cloud
        • AWS EKS
          • AWS EKS Reference Architecture
          • Adding an AWS IAM Role (EKS Master / Node Pool)
          • Public EKS Cluster
          • All Private EKS Cluster (beta)
          • Creating a Node Pool
        • Azure AKS
          • Creating a Node Pool
          • Enable Public IP Node Access for Azure Deployments
          • VMSS Autoscaling Rules
        • Google GKE
          • Creating a Node Pool
  • πŸ”ŽTroubleshooting
    • Cluster Resource View Issues
      • Network Error ! ServerError: Response not successful: Received status code 503
      • Network Error ! TypeError: Failed to fetch
      • Network Error ! ServerParseError: Unexpected token 'j', "json: erro"... is not valid JSON
      • Updating Labels and Annotations does not get reflected in resources list
      • Filtered resources are not fully listed
    • Runbook Issues
      • Deleting a runbook from .gp.yaml does not detach annotation in resources
      • Deleting a Code Account from gopaddle UI does not detach annotation in resources
    • Jira Issues
      • Creating, Updating or Appending a Jira issue fails with error INVALID_INPUT
    • EKS Issues
    • Deployment Issues
    • Node Issues
    • Huawei Issues
Powered by GitBook
On this page
  1. Overview
  2. Provision new Cluster
  3. Provision Clusters on Cloud
  4. Azure AKS

Enable Public IP Node Access for Azure Deployments

Steps to enable public IP access to the work loads deployed on Azure AKS Node pools

PreviousCreating a Node PoolNextVMSS Autoscaling Rules

Last updated 1 year ago

The public IP feature has to be enabled for the Azure account before we could set public IP access for a specific node pool.

  1. Download and install Azure CLI by following steps.

  2. Log in to Azure account.

az login
  1. Add aks-preview extension using azure-cli

az extension add --name aks-preview
  1. Register the NodePublicIPPreview feature

az feature register --name NodePublicIPPreview --namespace Microsoft.ContainerService
  1. Check status using the following command if it moved to 'registered' then the NodePublicIPPreview enabled successfully. It takes nearly 20-30 minutes.

az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/NodePublicIPPreview')].{Name:name,State:properties.state}"
  1. While adding NodePools to the Azure cluster, choose the β€œEnable Node Public IP β€œ option in the gopaddle UI.

  2. Open the firewall port from your azure account to access the workloads.

β†’ Login to azure portal.

β†’ In the search bar filter β€œNetwork security”. In that list choose your agent pool.

β†’ On the left side panel, click on the β€˜Inbound rule’ option, in that you have to add the port number which you want to open.

these
Page cover image