-
Notifications
You must be signed in to change notification settings - Fork 50
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.
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
Local Dump Clustername Error #271
Comments
Hello @p4pentest , Thanks for reporting the issue. We check the name of the cluster name with a regexp which does not include the |
Hi, thanks for the prompt response! I am not 100% sure if "@" is the problem here. I tried couple of changes and to me it seemed like "-" is the problem. But yeah I am happy to test it if you can share an updated version. For reference, I was testing the "dump local" against a fresh k8s installation, so pretty much everything is default. |
Can you confirm the issue has been fixed in v1.5.3 ? |
Sorry for the late response, recently used the latest version and did a local dump and ingest, I didn't face any issue. So can confirm its fixed. Thank you! |
Hi, I am struggling to get the offline dump run with the latest version (Also same issue with last couple of releases).
I am trying to do a local dump and I keep getting the invalid cluster name error:
FATA[20:41:49] dump core: create dumper: create dump result: Invalid clustername: "kubernetes-admin@kubernetes"
I tried updating the username to something without the "-" character (For example "kubernetesadmin@kubernetes") but still get the same error. I tried the previous Kubehound release versions and seems like the offline local dump works fine till v1.3.2 and then every version after that has this issue.
I am using the below:
Kubehound Release: v1.5.1 and previous
OS: Linux kali 6.8.11-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.8.11-1kali2 (2024-05-30) x86_64 GNU/Linux
Kubectl: Client Version: v1.31.1, Kustomize Version: v5.4.2
The text was updated successfully, but these errors were encountered: