Configuring sidecar exposure 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

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

EKS

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:

annotations:
  service.beta.kubernetes.io/aws-load-balancer-type: "external"
  service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip"

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

OKE

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: ```yaml annotations: service.beta.kubernetes.io/oci-load-balancer-internal: "true" ```

If needed, you can check their documentation for any special needs for your deployment.

AKS

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