diff --git a/docs/modules/hbase/pages/troubleshooting/index.adoc b/docs/modules/hbase/pages/troubleshooting/index.adoc
new file mode 100644
index 00000000..65ae6d0c
--- /dev/null
+++ b/docs/modules/hbase/pages/troubleshooting/index.adoc
@@ -0,0 +1,18 @@
+= Troubleshooting
+
+== Hbase access with kerberos authentication
+
+Currently, xref:zookeeper:index.adoc[Zookeeper] is not secured with authentication. This means, if an application tries to connect to Hbase, it would ask the zookeeper quorum to figure the correct nodes to talk to. In a Java world, you would define a `Client` which would carry the kerberos requirements.
+
+However, those requirements might be passed through and thus your client ( e.g. xref:spark-k8s:usage-guide:operations:applications.adoc[SparkApplications] ) would try to authenticate with kerberos at the corresponding Zookeeper endpoint. This will result in a kerberos ( authentication ) error.
+
+To prevent this, you can set a jvm argument like ( again e.g. SparkApplications )
+
+[source,yaml]
+----
+jvmArgumentOverrides:
+    add:
+        - "-Dzookeeper.sasl.client=false"
+----
+
+in all pods which would like to talk to Hbase.
diff --git a/docs/modules/hbase/partials/nav.adoc b/docs/modules/hbase/partials/nav.adoc
index 06f2167b..262bc3b1 100644
--- a/docs/modules/hbase/partials/nav.adoc
+++ b/docs/modules/hbase/partials/nav.adoc
@@ -25,3 +25,4 @@
 ** xref:hbase:reference/discovery.adoc[]
 ** xref:hbase:reference/commandline-parameters.adoc[]
 ** xref:hbase:reference/environment-variables.adoc[]
+* xref:hbase:troubleshooting/index.adoc[]