Internet Facing NLB not working returning empty response.

Hi Team,

I am using Altinity Operator to install Clickhouse on EKS. I am using internet facing NLB to expose the cluster.

When I run curl -v -k https://{host_name}.elb.us-west-2.amazonaws.com:8443, the host is getting resolved, but I receive empty response.

> User-Agent: curl/8.7.1
> Accept: */*
> 
* Request completely sent off
* TLSv1.2 (IN), TLS alert, close notify (256):
* Empty reply from server
* Closing connection
* TLSv1.2 (OUT), TLS alert, close notify (256):
curl: (52) Empty reply from server

These are the setting I am currently using:

<clickhouse>
    <http_port remove="1"></http_port>
    <https_port>8443</https_port>
    <interserver_http_port remove="1"></interserver_http_port>
    <interserver_https_port>9010</interserver_https_port>
    <mysql_port remove="1"></mysql_port>
    <postgresql_port remove="1"></postgresql_port>
    <prometheus>
        <asynchronous_metrics>true</asynchronous_metrics>
        <endpoint>/metrics</endpoint>
        <errors>true</errors>
        <events>true</events>
        <metrics>true</metrics>
        <port>9363</port>
        <status_info>true</status_info>
    </prometheus>
    <tcp_port remove="1"></tcp_port>
    <tcp_port_secure>9440</tcp_port_secure>
</clickhouse>

Can someone please help me what needs to be done to make sure that NLB is working as expected.

Review the EKS internet-facing NLB setup and the ClickHouse port settings shown in the issue, especially HTTPS on 8443 and secure TCP on 9440. Reproduce the curl request and inspect the Kubernetes service and load-balancer behavior; done means the endpoint returns a non-empty HTTPS response.