-
Notifications
You must be signed in to change notification settings - Fork 138
Description
What happened:
When kubeedge opens in-cluster-config to access api-server, the edge cannot access the cloud, and the cloud can access the edge
What you expected to happen:
expected: edge has access to the cloud
How to reproduce it (as minimally and precisely as possible):
deployment kubeedge:v1.18, edgemesh:v.17,open in-cluster-config configuration
link: https://release-1-18.docs.kubeedge.io/zh/docs/advanced/inclusterconfig
Anything else we need to know?:
Environment:
-
EdgeMesh version: v1.17
-
Kubernetes version (use
kubectl version): v29.6 -
KubeEdge version(e.g.
cloudcore --versionandedgecore --version): v1.18 -
Cloud nodes Environment:
- Hardware configuration (e.g.
lscpu): - OS (e.g.
cat /etc/os-release): ubuntu 20.04.6 LTS (Focal Fossa) - Kernel (e.g.
uname -a): Linux edge1 5.4.0-170-generic use const instead the string #188-Ubuntu SMP Wed Jan 10 09:51:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux - Go version (e.g.
go version): - Others:
- Hardware configuration (e.g.
-
Edge nodes Environment:
-
edgecore version (e.g.
edgecore --version): -
Hardware configuration (e.g.
lscpu): -
OS (e.g.
cat /etc/os-release): ubuntu 20.04.6 LTS (Focal Fossa) -
Kernel (e.g.
uname -a): Linux 957AAC8F230FC8616ED92D55AE65E878 5.10.104-tegra Add ci and makefile #2 SMP PREEMPT Thu Apr 13 21:09:10 CST 2023 aarch64 aarch64 aarch64 GNU/Linux -
Go version (e.g.
go version): -
Others:
-