USER MANUALS

External Access to Denodo Lakehouse Accelerator

The presto.service section of the values.yaml configures how the Denodo Lakehouse Accelerator will be accessed from the Denodo server, based on the Kubernetes service type.

presto:
  service:
    # -- Service type: ClusterIP, NodePort or LoadBalancer
    type: LoadBalancer
    annotations: {
      service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing",
      service.beta.kubernetes.io/aws-load-balancer-type: "external",
      service.beta.kubernetes.io/aws-load-balancer-subnets: "subnet-1,subnet-2"
    }

  • The options for the Kubernetes service type are:

    • LoadBalancer. This is the recommended and default option for cloud deployments. The cloud provider automatically provisions an external network load balancer, which distributes incoming traffic to the Denodo Lakehouse Accelerator.

    • ClusterIP. The service is only reachable from within the Kubernetes cluster. This is why it is usually combined with:

      • Ingress. To expose the service externally via HTTP/HTTPS. See Ingress section for detailed configuration.

      • Route. In OpenShift environments, a Route object provides similar functionality to an Ingress, exposing the service externally. This option needs to be created manually.

    • NodePort. It exposes the service on a static port on each node’s IP address. This means the Denodo Lakehouse Accelerator is accessible on Node_IP:Node_Port from outside the cluster. There is the option to select a custom port, Node_Port by configuring httpnodePort and/or httpsnodePort in the values.yaml. Otherwise, Kubernetes will select a free port within the 30000-32767 range meaning that the port can change each time the Denodo Lakehouse Accelerator is re-deployed.

  • annotations: Service annotations. For LoadBalancer services, the annotations provide additional metadata and configuration to the cloud provider’s load balancer controller on how to provision and configure the external load balancer.

    The specific annotations available and their values are highly dependent on the cloud provider. Always refer to the cloud provider’s official documentation for the most up-to-date list of LoadBalancer annotations:

Add feedback