Skip to content

Adding troubleshooting for kerberos #702

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Adding troubleshooting for kerberos #702

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bc9d27d
Adding troubleshooting for kerberos
Maleware Oct 21, 2025
f58f37c
Updating xref references
Maleware Oct 21, 2025
8d8db26
Adding newline eof
Maleware Oct 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/modules/hbase/pages/troubleshooting/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
= Troubleshooting

== Hbase access with kerberos authentication
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
== Hbase access with kerberos authentication
== 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pls separate sentences with newlines (in docs)

Suggested change
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.
Currently, xref:zookeeper:index.adoc[Zookeeper] stacklets can only be secured using mutual TLS.
This means, if an application tries to connect to HBase, it would contact Zookeeper to figure the correct HBase 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
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 )
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To prevent this, you can set a jvm argument like ( again e.g. SparkApplications )
To prevent this, you can set a JVM argument like this (again e.g. SparkApplications) in all Pods which would like to talk to HBase:

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please link to https://docs.stackable.tech/home/stable/concepts/overrides/#jvm-argument-overrides?
Please make sure the docs still build afterwards (you need to build the documentation repo locally for that)


[source,yaml]
----
jvmArgumentOverrides:
add:
- "-Dzookeeper.sasl.client=false"
Comment on lines +13 to +15
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAIK we normally use 2 spaces

Suggested change
jvmArgumentOverrides:
add:
- "-Dzookeeper.sasl.client=false"
jvmArgumentOverrides:
add:
- "-Dzookeeper.sasl.client=false"

----

in all pods which would like to talk to Hbase.
Comment on lines +17 to +18
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
in all pods which would like to talk to Hbase.

1 change: 1 addition & 0 deletions docs/modules/hbase/partials/nav.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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[]
Loading