The K8S cluster is not working

[HUAYAN999]

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?

Then I checked the operation of the K8S cluster, and it was indeed not running, how to solve this situation?

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]

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]

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


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]

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.

[HUAYAN999]

Unfortunately, I tried many things, but none of them worked. Can your team try to run the artifact as provided and how to use it and find a workaround? Thank you very much

[HUAYAN999]

In addition, if the K8S cluster fails to connect properly, if I redeploy the K8S cluster in the virtual image of the artifact, will it have a significant impact on the artifact? Is this possible?

[HUAYAN999]

Unfortunately, I tried many things, but none of them worked. Can your team try to run the artifact as provided and how to use it and find a workaround? Thank you very much

…

-----原始邮件----- 发件人:"Haohuang Wen" ***@***.***> 发送时间:2024-11-21 05:46:40 (星期四) 收件人: 5GSEC/5G-Spector ***@***.***> 抄送: HUAYAN999 ***@***.***>, Author ***@***.***> 主题: Re: [5GSEC/5G-Spector] The K8S cluster is not working (Issue #10) 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. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[onehouwong]

Can you try deploy 5G-Spector from scratch to avoid the k8s issue? We also have provided corresponding attack implementations for that.