Skip to content

Latest commit

 

History

History
39 lines (28 loc) · 1.89 KB

public-load-balancer.md

File metadata and controls

39 lines (28 loc) · 1.89 KB

Exposing a Helm sidecar to the Internet

To expose the sidecar to the Internet, so it's reachable outside the cluster, we use a LoadBalancer type service. This tells your cluster to provision a load balancer. This request has a different behavior depending on the cloud provider of your cluster.

GKE (GCP)

By default, GKE provisions a public IP for any LoadBalancer service. If needed, you can check GKE docs for any special needs for your deployment.

EKS (AWS)

By default, EKS provisions an internal facing load balancer for a LoadBalancer service. To make the load balancer provision a public IP address, you need to add the following annotations on the service.annotations field of the values file:

service:
    annotations:
        service.beta.kubernetes.io/aws-load-balancer-type: "external"
        service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing"

You can view a full list of possible annotations on this page.

OKE (OCI)

By default, OKE provisions a public IP for any LoadBalancer service. You can add the following annotation on the service.annotations field of the values file if you want OKE to provision an internal load balancer:

service:
    annotations:
        service.beta.kubernetes.io/oci-load-balancer-internal: "true"

If needed, you can check OCI docs for any special needs for your deployment.

AKS (Azure)

By default, AKS provisions a public IP for any LoadBalancer service. If needed, you can check AKS docs for any special needs for your deployment.