Skip to content
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

Open
p4pentest opened this issue Sep 18, 2024 · 3 comments
Open

Local Dump Clustername Error #271

p4pentest opened this issue Sep 18, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@p4pentest
Copy link

p4pentest commented Sep 18, 2024

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.

image

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

@p4pentest p4pentest changed the title Offline Local Dump Cluster Name Error dump core: create dumper: create dump result: Invalid clustername Sep 18, 2024
@p4pentest p4pentest changed the title dump core: create dumper: create dump result: Invalid clustername Local Dump Clustername Error Sep 18, 2024
@jt-dd jt-dd added the bug Something isn't working label Sep 18, 2024
@jt-dd jt-dd self-assigned this Sep 18, 2024
@jt-dd
Copy link
Contributor

jt-dd commented Sep 18, 2024

Hello @p4pentest ,

Thanks for reporting the issue. We check the name of the cluster name with a regexp which does not include the @ symbol yet. Will push a fix today and new release.

@p4pentest
Copy link
Author

p4pentest commented Sep 19, 2024

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.

Minosity-VR added a commit that referenced this issue Sep 20, 2024
@jt-dd
Copy link
Contributor

jt-dd commented Oct 1, 2024

Can you confirm the issue has been fixed in v1.5.3 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants