Dermio kubernetes dremio-master-0 deploy problem

[Abdul]

@balaji.ramaswamy dremio is running after removing the below property from extraProperties

   <property>
     <name>fs.s3a.connection.ssl.enabled</name>
     <value>false</value>
   </property>

However, I can access the UI through port forwarding but can’t access using an ingress. I am using apisix as ingress controller. I am getting below error in the UI

Bad Message 431

reason: Request Header Fields Too Large

I have opened a new issue regarding this 6 days back. below is the link. Please check this issue. I used two different helm charts one taken from artifact hub and other taken from dremio github repo. both are giving this same error when deployed dremio behind apisix ingress controller

Dremio UI not accessible when configured with OIDC and placed behind apisix ingress controller

Hello, I have deployed dremio on my kubernetes cluster using helm chart from artifact hub and it is running behind apisix ingress controller. I use keycloak as an OIDC provider which was integrated with apisix. basically, I have a apisixpluginconfig kubernetes resource which contains the information related to keycloak client that is used for OIDC. In the dremio ingress, I pass this apisixpluginconfig name using annotations. When we access the dremio ingress, the keycloak sends some set of head…