Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
liquanzhou authored Apr 6, 2023
1 parent 5fe199d commit 8919681
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,14 +70,19 @@

### 针对k8s使用的一点经验看法:


好多公司运维部门都是积极使用k8s,但没有规划的使用又会引起好多不易维护的难点痛点:


1.缺少自动化,导致繁重的人肉维护大量yaml文件


如果可以,k8s内部的yaml尽量规避任何人肉改动,全部发布系统标准化生成(deployment,service,hpa,inrgess,vs等等)


2.无法统一注册中心,每组k8s有各自的etcd注册,两组k8s中服务互联就会有麻烦,开发可能更喜欢依赖各自的注册发现方式.导致流量接入混乱.流量平滑,维护复杂.


这个情况,要看实际业务场景,如果推动统一注册发现机制,让开发互调流量和运维的流量接入统一


Expand Down

0 comments on commit 8919681

Please sign in to comment.