mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Fix: change forum url to ask.kubesphere.io
Signed-off-by: Zhengyi Lai <zheng1@kubesphere.io>
This commit is contained in:
Zhengyi Lai
parent
0f44f056a6
commit
fe634ebb52
|
|
@ -378,7 +378,7 @@ name = "开源社区"
|
|||
[[languages.zh.menu.main]]
|
||||
weight = 6
|
||||
name = "用户论坛"
|
||||
URL = "https://kubesphere.com.cn/forum"
|
||||
URL = "https://ask.kubesphere.io/forum"
|
||||
|
||||
|
||||
# [languages.tr]
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ KubeSphere project gateways and Routes provide a method for aggregating Services
|
|||
|
||||
Project gateways are used to aggregate Services. Therefore, we can understand the project gateway architecture from the perspective of Services. The following figure shows the architecture of a project gateway in a typical production environment.
|
||||
|
||||
|
||||
|
||||
|
||||
The architecture contains four parts:
|
||||
|
||||
|
|
@ -48,13 +48,13 @@ Therefore, Routes and API gateways such as Spring Cloud Gateway and Ocelot provi
|
|||
|
||||
Overall, each type of gateway has its own advantages and disadvantages. In the initial phase of a project, the gateway architecture should be considered. In cloud-native scenarios, Routes are an ideal choice. If your team depends on a specific technology stack, the API gateway of the technology stack is preferred. However, this does not necessarily mean you can only use one type of gateway. In some complex scenarios, you can use different types of gateways to utilize their advantages. For example, developers can use API gateways that they are familiar with to implement features such as service aggregation and authentication, and use Routes to expose these API gateways to implement features such as logging, monitoring, load balancing, and HTTPS offloading. For example, Microsoft's microservice architecture demo [eShopOnContainers](https://docs.microsoft.com/en-us/dotnet/architecture/cloud-native/introduce-eshoponcontainers-reference-app "eShopOnContainers") uses this hybrid architecture.
|
||||
|
||||
|
||||
|
||||
|
||||
## Hands-on Practice
|
||||
|
||||
So far we have discussed the application scenarios and overall architecture of Routes. In the following we will demonstrate how to configure a project gateway and Route in KubeSphere. The following uses SockShop as an example, which is a microservice demo project of Weaveworks. SockShop uses an architecture where the front-end and back-end are separated. It consists of the `front-end` Service and back-end Services such as `catalogue`, `carts`, and `orders`. In the architecture, the `front-end` Service not only provides static pages, but also functions as a proxy that forwards traffic to back-end APIs. Assume that asynchronous service blocking occurs when Node.js forwards traffic to APIs, which deteriorates page performance. To address this problem, we can use Routes to directly forward traffic to the `catalogue` Service. The following describes the configuration procedure.
|
||||
|
||||
|
||||
|
||||
|
||||
### Preparations
|
||||
|
||||
|
|
@ -84,11 +84,11 @@ After the preceding preparations are complete, go to the **Workloads** page of t
|
|||
|
||||
2. After the Route is created, click `front-end` in the Route list to view its details. On the **Resource Status** tab, click **Access Service**. If the Route functions properly, the following web page will be displayed.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Open the debugging console of your web browser (for example, press **F12** for Chrome) to check the network requests of the SockShop web page. The following figure shows an API request sent to `catalogue`.
|
||||
|
||||
|
||||
|
||||
|
||||
`X-Powered-By: Express` in `Response Headers` shows that the request is forwarded by the `front-end` Node.js application.
|
||||
|
||||
|
|
@ -98,7 +98,7 @@ After the preceding preparations are complete, go to the **Workloads** page of t
|
|||
|
||||
5. Refresh the SockShop web page (the page shows no changes) and check the network requests in the debugging console, as shown in the following figure.
|
||||
|
||||
|
||||
|
||||
|
||||
`X-Powered-By: Express` does not exist in `Response Headers`, which means that the API request is directly sent to the `catalogue` Service according to the new routing rule without being forwarded by the `front-end` Service. In this example, two routing rules are configured in the Route. The `/catalogue` routing rule is preferred to the `/` routing rule because the path of the former is longer and therefore more accurate.
|
||||
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@ Check if your computer browser's local clock is in sync with the Internet time a
|
|||
|
||||
Check your network plugin and make sure that there is no IP Pool overlap between your hosts and Pod network CIDR. It is strongly recommended that you install Kubernetes with [KubeKey](https://github.com/kubesphere/kubekey).
|
||||
|
||||
Chinese readers may refer to [the discussion](https://kubesphere.com.cn/forum/d/2027/16) in the KubeSphere China forum for more information.
|
||||
Chinese readers may refer to [the discussion](https://ask.kubesphere.io/forum/d/2027/16) in the KubeSphere China forum for more information.
|
||||
|
||||
## Prometheus produces an error log: opening storage failed, no such file or directory
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ KubeSphere 2.1.1 was released on Feb 23rd, 2020, which has fixed known bugs and
|
|||
- Fix the paging issue in DevOps pipelines' branches list page #[1517](https://github.com/kubesphere/kubesphere/issues/1517)
|
||||
- Fix the issue of failing to display pipeline configuration after modifying it #[1522](https://github.com/kubesphere/kubesphere/issues/1522)
|
||||
- Fix the issue of failing to download generated artifact in S2I job #[1547](https://github.com/kubesphere/kubesphere/issues/1547)
|
||||
- Fix the issue of [data loss occasionally after restarting Jenkins]( https://kubesphere.com.cn/forum/d/283-jenkins)
|
||||
- Fix the issue of [data loss occasionally after restarting Jenkins]( https://ask.kubesphere.io/forum/d/283-jenkins)
|
||||
- Fix the issue that only 'PR-HEAD' is fetched when binding pipeline with GitHub #[1780](https://github.com/kubesphere/kubesphere/issues/1780)
|
||||
- Fix 414 issue when updating DevOps credential #[1824](https://github.com/kubesphere/kubesphere/issues/1824)
|
||||
- Fix wrong s2ib/s2ir naming issue from B2I/S2I #[1840](https://github.com/kubesphere/kubesphere/issues/1840)
|
||||
|
|
|
|||
|
|
@ -167,7 +167,7 @@ You can now enable KubeEdge in your cluster and manage edge nodes on the KubeSph
|
|||
- Fixed the workload deployment failure in DevOps pipelines. ([#3112](https://github.com/kubesphere/kubesphere/issues/3112))
|
||||
- Fixed an issue where the account with the `admin` role in a DevOps project could not download artifacts. ([#3088](https://github.com/kubesphere/kubesphere/issues/3083))
|
||||
- Fixed an issue of DevOps pipeline creation failure. ([#3105](https://github.com/kubesphere/kubesphere/issues/3105))
|
||||
- Fixed an issue of triggering pipelines in a multi-cluster architecture. ([#2626](https://kubesphere.com.cn/forum/d/2626-webhook-jenkins))
|
||||
- Fixed an issue of triggering pipelines in a multi-cluster architecture. ([#2626](https://ask.kubesphere.io/forum/d/2626-webhook-jenkins))
|
||||
- Fixed an issue of data loss when a pipeline was edited. ([#1270](https://github.com/kubesphere/console/issues/1270))
|
||||
- Fixed a display issue of **Docker Container Register Credentials**. ([#1269](https://github.com/kubesphere/console/issues/1269))
|
||||
- Fixed a localization issue of Chinese unit in the code analysis result. ([#1278](https://github.com/kubesphere/console/issues/1278))
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ snapshot: 'https://pek3b.qingstor.com/kubesphere-community/images/DevOps.png'
|
|||
|
||||
## 测试环境描述
|
||||
|
||||
安装非 Docker 集群可以参考[文档](https://kubesphere.com.cn/forum/d/3054-dockerkubernetes) ，执行如下命令, 查看 Kubernetes 版本:
|
||||
安装非 Docker 集群可以参考[文档](https://ask.kubesphere.io/forum/d/3054-dockerkubernetes) ，执行如下命令, 查看 Kubernetes 版本:
|
||||
|
||||
```bash
|
||||
kubectl version
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ snapshot: '../../../images/blogs/aws-kubernetes/aws.png'
|
|||
对于生产环境，我们需要考虑 Kubernetes 集群的高可用性。本文教您部署如何在多台 AWS EC2 实例快速部署一套高可用的生产环境。要满足 Kubernetes 集群服务需要做到高可用，需要保证 kube-apiserver 的 HA ，可使用下列两种方式：
|
||||
|
||||
* AWS ELB（推荐）
|
||||
* [keepalived + haproxy](https://kubesphere.com.cn/forum/d/1566-kubernetes-keepalived-haproxy) 对 kube-apiserver 进行负载均衡，实现高可用 Kubernetes 集群。
|
||||
* [keepalived + haproxy](https://ask.kubesphere.io/forum/d/1566-kubernetes-keepalived-haproxy) 对 kube-apiserver 进行负载均衡，实现高可用 Kubernetes 集群。
|
||||
|
||||
本教程重点介绍配置 AWS ELB 服务高可用安装。
|
||||
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ KubeSphere 内置的基于 Jenkins 的 DevOps 流水线非常适合我们，并
|
|||
|
||||
### 连环坑：线下访问线上数据库
|
||||
|
||||
为了将应用的镜像从线下环境上传到线上生产环境的镜像仓库，我们踩了个连环坑，先是折腾了好久镜像仓库的 https 登陆。登陆的坑填平了，又掉到 push 镜像的坑里。最后，发现就是一个小小的配置导致的 push 镜像到线上环境失败。这两个坑折腾了我们很长的时间，不过好在最终都解决了，这些解决方法的细节，我们记录在了 KubeSphere 开发者论坛，可以在 KubeSphere 论坛找到：`https://kubesphere.com.cn/forum/d/294-docker-login-https-harbor`。
|
||||
为了将应用的镜像从线下环境上传到线上生产环境的镜像仓库，我们踩了个连环坑，先是折腾了好久镜像仓库的 https 登陆。登陆的坑填平了，又掉到 push 镜像的坑里。最后，发现就是一个小小的配置导致的 push 镜像到线上环境失败。这两个坑折腾了我们很长的时间，不过好在最终都解决了，这些解决方法的细节，我们记录在了 KubeSphere 开发者论坛，可以在 KubeSphere 论坛找到：`https://ask.kubesphere.io/forum/d/294-docker-login-https-harbor`。
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -260,7 +260,7 @@ Kubernetes 作为一个具有良好移植和扩展性的开源平台，用于管
|
|||
- https://learnk8s.io/setting-cpu-memory-limits-requests
|
||||
- https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/
|
||||
- https://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionX.html
|
||||
- https://kubesphere.com.cn/forum/d/1155-k8s
|
||||
- https://ask.kubesphere.io/forum/d/1155-k8s
|
||||
- https://kubernetes.io/docs/tasks/administer-cluster/out-of-resource/
|
||||
- https://kubernetes.io/docs/concepts/policy/limit-range/
|
||||
- https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ KubeSphere 项目网关与应用路由提供了一种聚合服务的方式，将
|
|||
|
||||
用户的服务和应用路由的架构密不可分，因此我们需要结合用户服务来理解项目网关的整体架构。一个典型生产环境中，项目网关架构如下图所示：
|
||||
|
||||
|
||||
|
||||
|
||||
图中组件共分为四个部分:
|
||||
|
||||
|
|
@ -50,13 +50,13 @@ Java、.net Core 的开发人员对 `Spring Cloud Gateway` 或 `Ocelot` 一定
|
|||
|
||||
微软官方微服务架构示例 [eShopOnContainers](https://docs.microsoft.com/en-us/dotnet/architecture/cloud-native/introduce-eshoponcontainers-reference-app "eShopOnContainers") 即采用了该种混合架构。
|
||||
|
||||
|
||||
|
||||
|
||||
## 动手实战
|
||||
|
||||
理解以上应用场景和整体架构后，我们接下来演示如何在 KubeSphere 中配置项目网关和应用路由。以下内容将基于 Weaveworks 的微服务演示项目 SockShop 实现。SockShop 是一个典型的前后端分离架构，它由前端服务 `front-end` 和若干后端服务 `catalogue`、`carts`、`orders` 等组成。在当前架构下，`front-end` 除了承担静态页面服务的功能，还承担了后端 API 代理转发的任务。我们假设以下场景，即由 Nodejs 转发 API 造成服务异步阻塞，从而影响页面性能。因此我们决定使用 ingress 直接转发服务 `catalogue` 用以提升性能。下面我们看一下详细配置步骤。
|
||||
|
||||
|
||||
|
||||
|
||||
### 准备工作
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ kubectl -n sock-shop apply -f https://github.com/microservices-demo/microservice
|
|||
|
||||
执行过后可以进入 `sock-shop` 的`工作负载`页面查看部署的状态，等待所有的部署都正常运行后，我们再进行下一步操作。
|
||||
|
||||
|
||||
|
||||
|
||||
### 项目网关配置
|
||||
|
||||
|
|
@ -82,25 +82,25 @@ kubectl -n sock-shop apply -f https://github.com/microservices-demo/microservice
|
|||
|
||||
1. 首先，我们选择左侧导航栏**应用负载**中的**应用路由**，点击右侧的创建。在基本信息中填写名称 `frontend`。在路由规则中，添加一条新的规则。由于是演示项目，我们使用自动生成模式。KubeSphere 自动以<服务名称>.<项目名称>.<网关地址>.nip.io 格式生成域名，该域名由 nip.io 自动解析为网关地址。在路径、服务、端口上依次选择 "/"、"front-end"、"80"。点击**下一步**后，继续点击**创建**。
|
||||
|
||||
|
||||
|
||||
|
||||
2. 路由创建完成后，可以在应用路由列表页面点击 `frontend` 进入详情。并在规则中可以点击**点击访问**访问按钮。在新的浏览器 tab 下，应该出现如下的网站：
|
||||
|
||||
|
||||
|
||||
|
||||
3. 为了与下面的步骤进行对比，我们在 SockShop 的网站页面打开调试功能查看网络请求，以 Chrome 为例只需点击键盘的**F12**键。刷新一下页面后我们找到如下 `catalogue` API 请求：
|
||||
|
||||
|
||||
|
||||
|
||||
该请求头中的 `X-Powered-By:Express` 表明了这条请求是由前端的 Nodejs 应用转发。
|
||||
|
||||
4. 接下来，在 `frontend` 的详情页面点击左侧的**更多操作**，并选择**编辑规则**。在弹出的编辑规则页面，选择刚刚增加的规则，并点击左侧的编辑图标。新增一条路径，在路径、服务、端口上依次选择"/catalogue"、"catalogue"、"80"。保存该设置。编辑后的规则如下：
|
||||
|
||||
|
||||
|
||||
|
||||
5. 我们再次访问 SockShop 的网站页面，该页面并没有任何变化。我们使用浏览器调试器，再次查看网络请求，`catalogue` 的请求如下：
|
||||
|
||||
|
||||
|
||||
|
||||
我们发现该请求已经没有了 `X-Powered-By:Express` 请求头，这说明了我们上面应用的规则已经生效，`catalogue`相关的 API 请求已经通过应用路由直接转发 `catalogue` 服务了，而不需要再通过 `fron-tend` 服务进行中转。以上的配置我们利用了路由规则的最长匹配规则。“/catalogue”比更路径具有更高的优先级。
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ KubeSphere 在 EdgeWatcher 中提供了用户指定的内网 IP是否被占用
|
|||
|
||||
|
||||
|
||||
之前，笔者也在 KubeSphere 的开发者社区提过这个[问题](https://kubesphere.com.cn/forum/d/4388-kubesphere-31)，同时也和负责边缘模块的社区开发者有过交流，确认了在 KubeSphere 的产品设计上，内网 IP 需要管理员或者用户自行按需进行规划，保证不重复。
|
||||
之前，笔者也在 KubeSphere 的开发者社区提过这个[问题](https://ask.kubesphere.io/forum/d/4388-kubesphere-31)，同时也和负责边缘模块的社区开发者有过交流，确认了在 KubeSphere 的产品设计上，内网 IP 需要管理员或者用户自行按需进行规划，保证不重复。
|
||||
|
||||
## 潜在问题
|
||||
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ snapshot: 'https://pek3b.qingstor.com/kubesphere-community/images/kubesphere-k8s
|
|||
|
||||
1. 查找官方论坛，关键词使用 **Etcd** 找到了以下一篇看着比较接近的文档，打开来看看。
|
||||
|
||||
> [Etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11](https://kubesphere.com.cn/forum/d/1322-etcd-prometheus-2-11 "etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11")
|
||||
> [Etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11](https://ask.kubesphere.io/forum/d/1322-etcd-prometheus-2-11 "etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11")
|
||||
|
||||
|
||||
|
||||
|
|
@ -618,7 +618,7 @@ snapshot: 'https://pek3b.qingstor.com/kubesphere-community/images/kubesphere-k8s
|
|||
|
||||
### **参考文档**
|
||||
|
||||
- [etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11](https://kubesphere.com.cn/forum/d/1322-etcd-prometheus-2-11 "etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11")
|
||||
- [etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11](https://ask.kubesphere.io/forum/d/1322-etcd-prometheus-2-11 "etcd 使用自签名证书，prometheus 报错未知机构签发 #2.11")
|
||||
- https://www.cnblogs.com/lvcisco/p/12575608.html?ivk_sa=1024320u
|
||||
|
||||
### **Get 文档**
|
||||
|
|
|
|||
|
|
@ -324,7 +324,7 @@ INFO: Disabled agent engine reconnects.
|
|||
- [jcli 使用手册](https://www.bookstack.cn/read/jenkins-cli-0.0.29-zh/263348)
|
||||
- [custom-war-packager](https://github.com/jenkinsci/custom-war-packager)
|
||||
- [Jenkins Kubernetes 插件](https://plugins.jenkins.io/kubernetes/)
|
||||
- [KubeSphere DevOps 3.0 流水线开发指南](https://kubesphere.com.cn/forum/d/2393-kubesphere-devops-30)
|
||||
- [KubeSphere DevOps 3.0 流水线开发指南](https://ask.kubesphere.io/forum/d/2393-kubesphere-devops-30)
|
||||
- [Jenkins 基于 Kubernetes 动态创建 pod](https://blog.csdn.net/qq_34556414/article/details/120623844)
|
||||
- [Can I use Jenkins kubernetes plugin when Jenkins server is outside of a kubernetes cluster?](https://stackoverflow.com/questions/40197607/can-i-use-jenkins-kubernetes-plugin-when-jenkins-server-is-outside-of-a-kubernet)
|
||||
- [kubernetes-jenkins-integration](https://stackoverflow.com/questions/48827345/kubernetes-jenkins-integration)
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@ kubectl get ep -n kube-system | grep -E 'kube-scheduler|kube-controller-manager'
|
|||
|
||||
请检查您的网络插件，并确保您的主机和 Pod 网络 CIDR 之间没有 IPPool 重叠。强烈建议您使用 [KubeKey](https://github.com/kubesphere/kubekey) 安装 Kubernetes。
|
||||
|
||||
中文读者可以参考 KubeSphere 开发者社区的[讨论](https://kubesphere.com.cn/forum/d/2027/16)了解更多信息。
|
||||
中文读者可以参考 KubeSphere 开发者社区的[讨论](https://ask.kubesphere.io/forum/d/2027/16)了解更多信息。
|
||||
|
||||
## Prometheus 产生错误日志：打开存储失败、没有此文件或目录
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ weight: 3510
|
|||
|
||||
对于生产环境，我们需要考虑集群的高可用性。如果关键组件（例如 kube-apiserver，kube-scheduler 和 kube-controller-manager）都在同一主节点上运行，一旦主节点出现故障，Kubernetes 和 KubeSphere 将不可用。因此，我们需要通过用负载均衡器配置多个主节点来设置高可用性集群。您可以使用任何云负载平衡器或任何硬件负载平衡器（例如F5）。另外，Keepalived 和 HAproxy 或 NGINX 也是创建高可用性集群的替代方法。
|
||||
|
||||
本教程介绍如何使用 [Keepalived + HAProxy](https://kubesphere.com.cn/forum/d/1566-kubernetes-keepalived-haproxy) 对 kube-apiserver 进行负载均衡，实现高可用 Kubernetes 集群。
|
||||
本教程介绍如何使用 [Keepalived + HAProxy](https://ask.kubesphere.io/forum/d/1566-kubernetes-keepalived-haproxy) 对 kube-apiserver 进行负载均衡，实现高可用 Kubernetes 集群。
|
||||
|
||||
## 前提条件
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ Weight: 3240
|
|||
对于生产环境，我们需要考虑集群的高可用性。本文教您部署如何在多台阿里 ECS 实例快速部署一套高可用的生产环境。要满足 Kubernetes 集群服务需要做到高可用，需要保证 kube-apiserver 的 HA ，可使用以下下列两种方式：
|
||||
|
||||
- 阿里云 SLB （推荐）
|
||||
- keepalived + haproxy [keepalived + haproxy](https://kubesphere.com.cn/forum/d/1566-kubernetes-keepalived-haproxy)对 kube-apiserver 进行负载均衡，实现高可用 kubernetes 集群。
|
||||
- keepalived + haproxy [keepalived + haproxy](https://ask.kubesphere.io/forum/d/1566-kubernetes-keepalived-haproxy)对 kube-apiserver 进行负载均衡，实现高可用 kubernetes 集群。
|
||||
|
||||
## 前提条件
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ KubeSphere 2.1.1 was released on Feb 23rd, 2020, which has fixed known bugs and
|
|||
- Fix the paging issue in DevOps pipelines' branches list page #[1517](https://github.com/kubesphere/kubesphere/issues/1517)
|
||||
- Fix the issue of failing to display pipeline configuration after modifying it #[1522](https://github.com/kubesphere/kubesphere/issues/1522)
|
||||
- Fix the issue of failing to download generated artifact in S2I job #[1547](https://github.com/kubesphere/kubesphere/issues/1547)
|
||||
- Fix the issue of [data loss occasionally after restarting Jenkins]( https://kubesphere.com.cn/forum/d/283-jenkins)
|
||||
- Fix the issue of [data loss occasionally after restarting Jenkins]( https://ask.kubesphere.io/forum/d/283-jenkins)
|
||||
- Fix the issue that only 'PR-HEAD' is fetched when binding pipeline with GitHub #[1780](https://github.com/kubesphere/kubesphere/issues/1780)
|
||||
- Fix 414 issue when updating DevOps credential #[1824](https://github.com/kubesphere/kubesphere/issues/1824)
|
||||
- Fix wrong s2ib/s2ir naming issue from B2I/S2I #[1840](https://github.com/kubesphere/kubesphere/issues/1840)
|
||||
|
|
|
|||
|
|
@ -167,7 +167,7 @@ weight: 18200
|
|||
- 修复 DevOps 流水线中无法部署工作负载的问题 [#3112](https://github.com/kubesphere/kubesphere/issues/3112)
|
||||
- 修复 DevOps 项目管理员无法下载 Artifact 的问题 [#3088](https://github.com/kubesphere/kubesphere/issues/3083)
|
||||
- 修复 DevOps 无法创建流水线的问题 [#3105](https://github.com/kubesphere/kubesphere/issues/3105)
|
||||
- 修复多集群下流水线触发的问题 [#2626](https://kubesphere.com.cn/forum/d/2626-webhook-jenkins)
|
||||
- 修复多集群下流水线触发的问题 [#2626](https://ask.kubesphere.io/forum/d/2626-webhook-jenkins)
|
||||
- 修复某些情况下编辑流水线时导致的数据丢失问题 [#1270](https://github.com/kubesphere/console/issues/1270)
|
||||
- 修复点击 **Docker Container Registry Credentials** 时的报错问题 [#1269](https://github.com/kubesphere/console/issues/1269)
|
||||
- 修复英文控制台显示中文代码质量检查结果的问题 [#1278](https://github.com/kubesphere/console/issues/1278)
|
||||
|
|
|
|||
|
|
@ -88,20 +88,20 @@ section7:
|
|||
profession: 容器解决方案架构师
|
||||
base: 成都/武汉
|
||||
workYears: 3-5 年
|
||||
link: https://kubesphere.com.cn/forum/d/1666-kubesphere-qingcloud
|
||||
link: https://ask.kubesphere.io/forum/d/1666-kubesphere-qingcloud
|
||||
- company: 吉利汽车
|
||||
profession: 云原生工程师
|
||||
base: 杭州
|
||||
workYears: 3-5 年
|
||||
link: https://kubesphere.com.cn/forum/d/6243
|
||||
link: https://ask.kubesphere.io/forum/d/6243
|
||||
- company: 摩尔线程
|
||||
profession: GPU 云原生开发工程师
|
||||
base: 北京
|
||||
workYears: 3-5 年
|
||||
link: https://kubesphere.com.cn/forum/d/6605-gpu
|
||||
link: https://ask.kubesphere.io/forum/d/6605-gpu
|
||||
- company: 青云QingCloud
|
||||
profession: 容器网络开发工程师
|
||||
base: 成都/武汉
|
||||
workYears: 3-5 年
|
||||
link: https://kubesphere.com.cn/forum/d/1666-kubesphere-qingcloud
|
||||
link: https://ask.kubesphere.io/forum/d/1666-kubesphere-qingcloud
|
||||
---
|
||||
|
|
@ -58,7 +58,7 @@ User Group 旨在加强 KubeSphere 用户之间的交流和学习，形式包括
|
|||
|
||||
## KubeSphere 贡献奖励
|
||||
|
||||
KubeSphere 社区在一个月之前上线了论坛（kubesphere.com.cn/forum/），方便社区成员与用户间的技术交流与产品问答反馈。最近两周，我们很欣慰的是，有不少用户在论坛发布了多篇高质量的实践文章或避坑指南，帮助了其他用户更好地理解和上手 KubeSphere。社区欢迎大家在论坛分享记录你们在各种基础设施环境下的安装部署相关的文章，以及使用实践和避坑技巧，也希望大家能够将个人原创的云原生相关的知识或文章发布在 KubeSphere 论坛。对于社区用户发布的优质技术文章，将被同步在 KubeSphere 官网博客下。
|
||||
KubeSphere 社区在一个月之前上线了论坛（ask.kubesphere.io/forum/），方便社区成员与用户间的技术交流与产品问答反馈。最近两周，我们很欣慰的是，有不少用户在论坛发布了多篇高质量的实践文章或避坑指南，帮助了其他用户更好地理解和上手 KubeSphere。社区欢迎大家在论坛分享记录你们在各种基础设施环境下的安装部署相关的文章，以及使用实践和避坑技巧，也希望大家能够将个人原创的云原生相关的知识或文章发布在 KubeSphere 论坛。对于社区用户发布的优质技术文章，将被同步在 KubeSphere 官网博客下。
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ footer:
|
|||
- content: 中国站
|
||||
link: https://kubesphere.com.cn/
|
||||
- content: 中文论坛
|
||||
link: https://kubesphere.com.cn/forum
|
||||
link: https://ask.kubesphere.io/forum
|
||||
- content: 全球站
|
||||
link: https://kubesphere.io
|
||||
|
||||
|
|
|
|||
|
|
@ -333,7 +333,7 @@
|
|||
|
||||
var bindMeet = function () {
|
||||
$('.meet-div').click(function () {
|
||||
window.open('https://kubesphere.com.cn/forum/d/2712-meetup-topic')
|
||||
window.open('https://ask.kubesphere.io/forum/d/2712-meetup-topic')
|
||||
})
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue