Using a Private IP Address When Installing or Upgrading AtScale in Azure Environment

By default, AtScale installation and upgrade procedures use a public IP address.  If a customer wishes to change this approach and use a private IP address, they should read this article first.

By way of example, for an Azure managed environment:

  • If you want to change an existing AtScale deployed installation, you can modify the kubernetes configuration directly.  Create a 'patch file' with the code below and apply it using the following REST API call:  kubectl apply -f <patch filename>
kind: Service apiVersion: v1 metadata: name: kong-proxy namespace: atscale annotations:   service.beta.kubernetes.io/azure-load-balancer-internal: "true"
  • If you are deploying via Helm, make these edits to your 'values.yml' file and reapply: 

helm upgrade atscale <ATSCALE_REPO> --version <ATSCALE_VERSION> -n <NAMESPACE> --values <values.yml>

kongproxy:   metadata: annotations:   service.beta.kubernetes.io/azure-load-balancer-internal: "true"


Was this article helpful?

0 out of 0 found this helpful