search

5GSEC / 5G-Spector

An O-RAN compliant runtime intrusion detection system (xApp) for layer-3 (L3) celluar attack detection
https://www.5gsec.com
Apache License 2.0
40 stars 7 forks source link

The K8S cluster is not working #10

Open HUAYAN999 opened 3 days ago

HUAYAN999 commented 3 days ago

I am experiencing the following problem when using, the K8S cluster cannot run normally, and the following error is displayed, how can I continue the configuration?

屏幕截图 2024-11-19 112945

Then I checked the operation of the K8S cluster, and it was indeed not running, how to solve this situation? 屏幕截图 2024-11-19 113335

I looked up the previous issue page and there was one guy who had a similar issue to me, he solved the apt update issue by importing the GPG key, I used the same method but I still can't use the K8S cluster. How do I continue working?

onehouwong commented 3 days ago

Could you provide more information here? For example, what's the error after you run apt update and what's the output of the GPG key import command.

Due to these compatibility reasons, we won't recommend using the artifact anymore since it's based on an old ubuntu version. Instead we recommend to instantiate a fresh ubuntu 20.04 vm and follow this guide (https://github.com/5GSEC/5G-Spector/wiki/O%E2%80%90RAN-SC-RIC-Deployment-Guide) to deploy the 5G network and RIC from scratch.

HUAYAN999 commented 2 days ago

The result of the run is as shown in the image, but the K8S cluster still doesn't work, even though I've tried importing the GPG key 屏幕截图 2024-11-20 104456 屏幕截图 2024-11-20 105012 Also, my goal is to try to build this system as well as reproduce the attack detection process, if I try to deploy from scratch using the link you gave, can I successfully get similar results to deploying that artifact, how do I successfully reproduce the attack detection process?

onehouwong commented 1 day ago

It seems your apt update was running successfully so it's not likely the issue of GPG keys. The kubectl connection refused can have many causes, you may want to further debug this through existing solutions, such as https://discuss.kubernetes.io/t/the-connection-to-the-server-host-6443-was-refused-did-you-specify-the-right-host-or-port/552/4.