Skip to content

Commit 6edb771

Browse files
committed
feat: update docs content
1 parent 6daa01f commit 6edb771

File tree

3 files changed

+42
-44
lines changed

3 files changed

+42
-44
lines changed

docs/03-getting-started/02-install-lower-layer-system/02-install-kubernetes.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ sudo apt-mark hold kubelet kubeadm kubectl
4242

4343
This step may occur [Question 1: kube-proxy report iptables problems](/docs/getting-started/install-lower-layer-system/faqs#question-1-kube-proxy-report-iptables-problems), [Question 2: calico and coredns are always in initializing state](/docs/getting-started/install-lower-layer-system/faqs#question-2-calico-and-coredns-are-always-in-initializing-state) and [Question 3:metrics-server keeps unsuccessful state](/docs/getting-started/install-lower-layer-system/faqs#question-3metrics-server-keeps-unsuccessful-state)
4444

45-
### Reset Environment (Skip on first installation)
45+
### Reset environment (Skip on first installation)
4646

4747
```bash
4848
swapoff -a
@@ -141,7 +141,6 @@ kubectl get pods -A
141141

142142
Step 5: Configure calico and kube-proxy.
143143

144-
Edge 节点加入时可能会自动部署 calico-node 和 kube-proxy,kube-proxy 会部署成功(但是 edgecore 的 log 会提示不应该部署 kube-proxy),calico 会初始化失败。为了避免上述情况,做如下操作:
145144

146145
When an Edge node joins, calico-node and kube-proxy may be automatically deployed.
147146
Kube-proxy will deploy successfully (but the edgecore log will prompt that kube-proxy should not be deployed),

docs/03-getting-started/02-install-lower-layer-system/03-install-kubeedge.md

Lines changed: 39 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -6,67 +6,65 @@ custom_edit_url: null
66

77
# Install KubeEdge
88

9-
[TBD]
9+
## Download keadm (both cloud/edge)
1010

11-
## 下载 keadm(云边共用)
11+
keadm is mainly used for kubeedge management, installation, and usage.
1212

13-
keadm主要用于 kubeedge 管理、安装和使用
14-
15-
官方发行版本链接:[Release KubeEdge v1.9.2 release · kubeedge/kubeedge (github.com)](https://github.com/kubeedge/kubeedge/releases/)
13+
Official release version link: [Release KubeEdge v1.9.2 release · kubeedge/kubeedge (github.com)](https://github.com/kubeedge/kubeedge/releases/)
1614

1715
```bash
18-
#查看自己的架构
16+
# Check machine architecture
1917
uname -a
20-
#下载对应版本以及架构
18+
# Download keadm with corresponding version and architecture
2119
wget https://github.com/kubeedge/kubeedge/releases/download/v1.9.2/keadm-v1.9.2-linux-amd64.tar.gz
22-
#解压
20+
# Unzip
2321
tar zxvf keadm-v1.9.2-linux-amd64.tar.gz
24-
#添加执行权限
22+
# Add execution permissions
2523
chmod +x keadm-v1.9.2-linux-amd64/keadm/keadm
26-
#移动目录
24+
# Move to /usr/local/bin/
2725
cp keadm-v1.9.2-linux-amd64/keadm/keadm /usr/local/bin/
2826
```
2927

30-
## 启动 KubeEdge(云端)
28+
## Start KubeEdge (cloud)
3129

32-
可能出现 [问题四:10002 already in use](/docs/getting-started/install-lower-layer-system/faqs#问题四10002-already-in-use)
30+
This step may occur [Question 4:10002 already in use](/docs/getting-started/install-lower-layer-system/faqs#question-410002-already-in-use)
3331

34-
### 重置环境(第一次安装时跳过)
32+
### Reset environment (Skip on first installation)
3533

3634
```bash
3735
keadm reset
3836
```
3937

40-
### 启动 cloudcore
38+
### Start cloudcore
4139

42-
通过 keadm 启动
40+
Start cloudcore by keadm
4341
```bash
44-
#注意修改--advertise-address的ip地址
42+
# Modify the ip address of '--adverse-address'
4543
keadm init --advertise-address=114.212.81.11 --kubeedge-version=1.9.2
4644

47-
#打开转发路由
45+
# Open forwarding route
4846
kubectl get cm tunnelport -n kubeedge -o yaml
49-
#找到10350 或者10351
50-
#set the rule of trans,设置自己的端口
51-
export CLOUDCOREIPS=xxx.xxx.xxx.xxx
47+
# find '10350' or '10351' in the result
5248

53-
# dport的内容对应tunnelport
49+
# set CLOUDCOREIPS
50+
export CLOUDCOREIPS=xxx.xxx.xxx.xxx
51+
# set 'dport' as previously 'tunnelport'
5452
iptables -t nat -A OUTPUT -p tcp --dport 10351 -j DNAT --to $CLOUDCOREIPS:10003
5553

5654
cd /etc/kubeedge/
5755

58-
# 或者从网站下载 https://github.com/kubeedge/kubeedge/blob/master/build/tools/certgen.sh
56+
# or download manually from https://github.com/kubeedge/kubeedge/blob/master/build/tools/certgen.sh
5957
wget https://raw.githubusercontent.com/kubeedge/kubeedge/refs/heads/master/build/tools/certgen.sh
6058

6159
bash certgen.sh stream
6260
```
6361

64-
### cloudcore 配置
62+
### Configure cloudcore
6563

6664
```bash
6765
vim /etc/kubeedge/config/cloudcore.yaml
6866

69-
# 修改 cloudcore.yaml 内容
67+
# modify cloudcore.yaml
7068
modules:
7169
..
7270
cloudStream:
@@ -77,56 +75,56 @@ modules:
7775
enable: true
7876
```
7977

80-
重启 cloudcore:
78+
Restart cloudcore:
8179
```bash
8280
sudo systemctl restart cloudcore.service
8381
```
8482

85-
如果直接重启cloudcore失败,解决方法如下:
83+
If restarting cloudcore fails, the solution is as follows:
8684
```bash
87-
# 将生成的cloudcore.service放到systemctl管理的文件夹下
85+
# Place the generated 'cloudcore.service' under the folder managed by systemctl
8886
cp /etc/kubeedge/cloudcore.service /etc/systemd/system
8987
```
9088

91-
使用 `journalctl -u cloudcore.service -xe` 查看cloudcore是否正常运行且没有报错
89+
Use `journalctl -u cloudcore.service -xe` to check if cloudcore is running normally and there are no errors reported.
9290

93-
## 加入KubeEdge集群(边端)
91+
## Join KubeEdge cluster (edge)
9492

95-
可能出现 [问题五:edgecore-符号链接已存在](/docs/getting-started/install-lower-layer-system/faqs#问题五edgecore-符号链接已存在)
93+
This step may occur [Question 5:edgecore file exists](/docs/getting-started/install-lower-layer-system/faqs#question-5edgecore-file-exists)
9694

97-
如果 `keadm join` 失败可以从 `keadm reset` 开始重新尝试
95+
If `keadm join` fails, you can retry from `keadm reset`.
9896

99-
### 重置环境(第一次安装时跳过)
97+
### Reset environment (Skip on first installation)
10098
```bash
101-
# 重启
99+
# reset
102100
keadm reset
103101

104-
# 重新加入时,报错存在文件夹,直接删除
102+
# When rejoining, if an error was reported that there was a folder, just deleted directly.
105103
rm -rf /etc/kubeedge
106104

107-
# docker容器占用(通常是mqtt)
105+
# Possible docker container occupancy (usually 'mqtt')
108106
docker ps -a
109107
docker stop mqtt
110108
docker rm mqtt
111109
```
112110

113-
### 启动 edgecore
111+
### Start edgecore
114112

115-
启动edgecore时,需要在云端获取token:
113+
To start edgecore, you need to get token on the master node (cloud) first:
116114
```bash
117115
keadm gettoken
118116
```
119117

120-
在边端执行:
118+
Execute on the edge:
121119
```bash
122-
# 注意这里是要加入master的IP地址,token是master上获取的
120+
# Add IP address of the master here. The token here is obtained from the master
123121
keadm join --cloudcore-ipport=114.212.81.11:10000 --kubeedge-version=1.9.2 --token=9e1832528ae701aba2c4f7dfb49183ab2487e874c8090e68c19c95880cd93b50.eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MTk1NjU4MzF9.1B4su4QwvQy_ZCPs-PIyDT9ixsDozfN1oG4vX59tKDs
124122
```
125123

126-
可能出现 [问题二十五:边端join报错](/docs/getting-started/install-lower-layer-system/faqs#问题二十五边端join报错)
124+
This step may occur [Question 25:keadm join error on edge nodes](/docs/getting-started/install-lower-layer-system/faqs#question-25keadm-join-error-on-edge-nodes).
127125

128126
```bash
129-
# 加入后,先查看信息
127+
# Check for logs
130128
journalctl -u edgecore.service -f
131129
```
132130

docs/03-getting-started/02-install-lower-layer-system/08-faqs.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -594,9 +594,10 @@ client tries to connect global manager(address: gm.sedna:9000) failed, error: di
594594

595595
原因:docker国内无法访问,新加入的edge没有做对应配置,导致拉取不到 kubeedge/edgemesh-agent 镜像。配置后重启docker和edgecore即可。
596596

597+
597598
### Question 25:keadm join error on edge nodes
598599

599-
边端执行`keadm join`报错
600+
Execution of `keadm join` on edges reported errors.
600601

601602
Solution: Check the `edgecore.yaml` file
602603
```bash

0 commit comments

Comments
 (0)