From 174c009c1c28e05a6cc901418597b894bcc18862 Mon Sep 17 00:00:00 2001 From: faweizhao26 Date: Mon, 15 Apr 2024 10:00:54 +0800 Subject: [PATCH] fix some blogs' url of images Signed-off-by: faweizhao26 --- content/en/blogs/faas-openfunction.md | 2 +- .../blogs/calico-wireguard-support-with-azure-cni.md | 6 +++--- .../blogs/deploy-kubesphere-v3.4.0-on-arm-openeuler.md | 2 +- content/zh/blogs/kubesphere-devops-pipeline-guide.md | 2 +- content/zh/blogs/kubesphere-log-collection.md | 10 +++++----- .../zh/blogs/kubesphere-v3.3.0-offline-installation.md | 2 -- content/zh/blogs/openelb-arp.md | 2 +- 7 files changed, 12 insertions(+), 14 deletions(-) diff --git a/content/en/blogs/faas-openfunction.md b/content/en/blogs/faas-openfunction.md index a3e4e91208..be92e19a80 100644 --- a/content/en/blogs/faas-openfunction.md +++ b/content/en/blogs/faas-openfunction.md @@ -5,7 +5,7 @@ keywords: Serverless, FaaS, OpenFunction description: This article describes function computing concepts, reference architectures, and the latest trends in the cloud-native Serverless field, and further explains how OpenFunction builds a modern cloud-native serverless computing platform. createTime: '2021-12-03' author: 'Huo Bingjie, Felix' -snapshot: 'https://pek3b.qingstor.com/kubesphere-community/images/serverless-faas-openfunction.png' +snapshot: 'https://pek3b.qingstor.com/kubesphere-community/images/serverless-20211203-cover.png' --- **Serverless computing**, commonly known as Serverless, has become a buzzword in the cloud-native field. It will fuel the next wave of development in cloud computing after IaaS and PaaS. Serverless emphasizes an architecture philosophy and service model that allows developers to focus on implementing business logics in applications rather than on managing infrastructures (e.g., servers). In its paper *Cloud Programming Simplified: A Berkeley View on Serverless Computing*, the University of California at Berkeley presents two key viewpoints on Serverless: diff --git a/content/zh/blogs/calico-wireguard-support-with-azure-cni.md b/content/zh/blogs/calico-wireguard-support-with-azure-cni.md index f4c78ba8dc..efe8d1412e 100644 --- a/content/zh/blogs/calico-wireguard-support-with-azure-cni.md +++ b/content/zh/blogs/calico-wireguard-support-with-azure-cni.md @@ -22,7 +22,7 @@ WireGuard 是一种 VPN 技术，从 linux 5.6 内核开始默认包含在内核 WireGuard 是一种 VPN 技术，通常被认为是 C/S 架构。它同样能在端对端的网格网络架构中配置使用，这就是 Tigera 设计的 WireGuard 可以在 Kubernetes 中启用的解决方案。使用 Calico，所有启用 WireGuard 的节点将端对端形成一个加密的网格。Calico 甚至支持在同一集群内同时包含启用 WireGuard 的节点与未启用 WireGuard 的节点，并且可以相互通信。 -![](/jsDelivr/1.1.png) +![](https://pek3b.qingstor.com/kubesphere-community/images/06581ad7-image1-10-e1628656758212.png) 我们选择 WireGuard 并不是一个折中的方案。我们希望提供最简单、最安全、最快速的方式来加密传输 Kubernetes 集群中的数据，而无需使用 mTLS、IPsec 或其他复杂的配置。事实上，您可以把 WireGuard 看成是另一个具有加密功能的 Overlay。 @@ -35,13 +35,13 @@ WireGuard 是一种 VPN 技术，通常被认为是 C/S 架构。它同样能在 - 为每个节点编写端对端节点 - 使用防火墙标记（fwmark）编写 IP route、IP tables 和 Routing tables，以此正确处理各自节点上的路由 -您仅需指明意图，其他的事情都由集群完成 +您仅需指明意图，其他的事情都由集群完成。 ## 使用 WireGuard 时的数据包流向 下图显示了启用 WireGuard 后集群中的各种数据包流量情况。 -![](/jsDelivr/2.1.png) +![](https://pek3b.qingstor.com/kubesphere-community/images/eb522dd1-image2-8.png) 同一主机上的 Pod： diff --git a/content/zh/blogs/deploy-kubesphere-v3.4.0-on-arm-openeuler.md b/content/zh/blogs/deploy-kubesphere-v3.4.0-on-arm-openeuler.md index 2a94ef2118..d9fbe72f0c 100644 --- a/content/zh/blogs/deploy-kubesphere-v3.4.0-on-arm-openeuler.md +++ b/content/zh/blogs/deploy-kubesphere-v3.4.0-on-arm-openeuler.md @@ -643,7 +643,7 @@ Please check the result using the command: - Etcd 监控 -![](https://opsman-1258881081.cos.ap-beijing.myqcloud.com//ksp-monitor-cluster-Etcd-v340-v126-arm.png) +![](https://pek3b.qingstor.com/kubesphere-community/images/ksp-monitor-cluster-etcd-v340-v126-arm.png) - 应用商店 diff --git a/content/zh/blogs/kubesphere-devops-pipeline-guide.md b/content/zh/blogs/kubesphere-devops-pipeline-guide.md index 2c07026ce7..b151f8499c 100644 --- a/content/zh/blogs/kubesphere-devops-pipeline-guide.md +++ b/content/zh/blogs/kubesphere-devops-pipeline-guide.md @@ -164,7 +164,7 @@ yygh-site 对于 Sentinel，我们直接使用雷丰阳已经制作好的镜像 `leifengyang/sentinel:1.8.2`，然后暴露一个 NodePort 类型的 Service，端口号为 `32636`。 访问 `http://192.168.23.160:32636`，以默认用户 `sentinel` 和默认密码 `sentinel` 登录，可以进入 Sentinel 控制台。 如果一切顺利，应该可以看到类似的页面： -![](htts://pek3b.qingstor.com/kubesphere-community/images/70909f56-0452-4dbc-b716-c47431a53404.png) +![](https://pek3b.qingstor.com/kubesphere-community/images/1776090-20221101110638437-1889863892.png) 对于 MongoDB，我们直接通过应用模版部署它（不勾选登录认证）： diff --git a/content/zh/blogs/kubesphere-log-collection.md b/content/zh/blogs/kubesphere-log-collection.md index ff1f5b5eba..25971b41f9 100644 --- a/content/zh/blogs/kubesphere-log-collection.md +++ b/content/zh/blogs/kubesphere-log-collection.md @@ -16,13 +16,13 @@ snapshot: 'https://pek3b.qingstor.com/kubesphere-community/images/20221128172157 容器日志分为标准输出日志和落盘日志两种。应用将日志打印在容器标准输出 `STDOUT` 中，由容器运行时(Docker 或 Containerd)把标准输出日志写入容器日志文件中，最终由采集器导出。这种日志打印采集是业界推荐方案。但对于不打印标准输出而直接将日志落盘的情况，业界最常用见的方案是，使用 `Sidecar` 采集落盘日志，把落盘日志打印到容器标准输出中，再利用标准输出日志的采集方式输出。 -![](https://p9-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/bb596565862f45f7852421c50d9e88b1~tplv-k3u1fbpfcp-watermark.image?) +![](https://pek3b.qingstor.com/kubesphere-community/images/bb596565862f45f7852421c50d9e88b1~tplv-k3u1fbpfcp-watermark.png) 对于 KubeSphere 用户，只需要两步即可：第一在项目中开启`收集卷上日志`，第二在工作负载中配置落盘文件路径。具体操作见下图所示。 -![](https://p9-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/e0b20d93902f4545826cacbc4541f054~tplv-k3u1fbpfcp-watermark.image?) +![](https://pek3b.qingstor.com/kubesphere-community/images/e0b20d93902f4545826cacbc4541f054~tplv-k3u1fbpfcp-watermark.png) -![](https://p9-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/4d93e799977840628dd45d0a19493d9b~tplv-k3u1fbpfcp-watermark.image?) +![](https://pek3b.qingstor.com/kubesphere-community/images/4d93e799977840628dd45d0a19493d9b~tplv-k3u1fbpfcp-watermark.png) 上述两个步骤，会自动在容器中注入 `Filebeat Sidecar` 作为 logging-agent，将落盘日志打印输出在容器标准输出中。Filebeat 配置可通过 ConfigMap 修改。 @@ -58,7 +58,7 @@ $ kubectl get Output -n kubesphere-logging-system es -o yaml 我们把日志导出到第三方日志服务，那就需要定制 FluentBit 输入输出。使用 `tail` 插件采集 `/var/log/containers/flux-wms-*.log` 文件中的日志，输出到 `Kafka` 中。可参考如下配置： -![](https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/942da92ef0af483687b08b2994bc5d66~tplv-k3u1fbpfcp-watermark.image?) +![](https://pek3b.qingstor.com/kubesphere-community/images/942da92ef0af483687b08b2994bc5d66~tplv-k3u1fbpfcp-watermark.png) ```yaml --- @@ -241,7 +241,7 @@ logging.level: warning 当看到 Kafka 消费者输出完美多行日志块时，脑后传来多巴胺的快感！再看一眼架构图，咱们来做总结！ -![](https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/248b663dfc354e6d860ebd671dd5b5e3~tplv-k3u1fbpfcp-watermark.image?) +![](https://pek3b.qingstor.com/kubesphere-community/images/248b663dfc354e6d860ebd671dd5b5e3~tplv-k3u1fbpfcp-watermark.png) ## 总结 diff --git a/content/zh/blogs/kubesphere-v3.3.0-offline-installation.md b/content/zh/blogs/kubesphere-v3.3.0-offline-installation.md index 13234f35ed..f402a49890 100644 --- a/content/zh/blogs/kubesphere-v3.3.0-offline-installation.md +++ b/content/zh/blogs/kubesphere-v3.3.0-offline-installation.md @@ -596,8 +596,6 @@ https://kubesphere.io 2022-06-30 14:30:19 通过 `http://{IP}:30880` 使用默认帐户和密码 `admin/P@88w0rd` 访问 KubeSphere 的 Web 控制台，进行后续的操作配置。 -![](https://kubesphere.com.cn/images/docs/v3.3/zh-cn/upgrade/air-gapped-upgrade-with-ks-installer/kubesphere-login.PNG) - ## 总结 感谢您完整的阅读完本文，为此，您应该 Get 到了以下技能： diff --git a/content/zh/blogs/openelb-arp.md b/content/zh/blogs/openelb-arp.md index 4fe6572cd1..db01ff7117 100644 --- a/content/zh/blogs/openelb-arp.md +++ b/content/zh/blogs/openelb-arp.md @@ -79,7 +79,7 @@ spec: ## Layer2 模式中的黑客技术 -![](https://files.mdnice.com/user/2166/ff880d68-be25-4def-8cd6-b09a032ae753.png) +![](https://pek3b.qingstor.com/kubesphere-community/images/ff880d68-be25-4def-8cd6-b09a032ae753.webp) > ARP 欺骗技术: 应用程序主动回复路由器 ARP 请求，让路由器以为该应用是合法终端，从而劫持网络流量包。