知识卡片
卸载顺序须处理遗留代理
卸载网格不能只删除控制面而留下自动注入配置和无人管理的代理。原书指出这种残留可能影响集群 API 访问;应采用对应版本的受支持清理过程,而非把删命名空间当作通用卸载命令。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 渐进采用与演进架构 · 查看原书依据
While testing various service mesh deployments, installing and uninstalling the mesh, do not uninstall by deleting the control plane first. Using Istio as an example, deleting the istio-system namespace without applying manifests to uninstall the mesh could cause you some grief because you might be left with a nonfunctional Kubernetes cluster where kubectl times out when communicating with the Kubernetes API server. When Istio isn’t cleaned up properly, especially when
参考来源
- 位置:《The Enterprise Path to Service Mesh Architectures, 2nd Edition》第03章《渐进采用与演进架构》(来源项目book-sources;源文件:extracted/The Enterprise Path to Service Mesh Architectures, 2nd Edition/_epub-src/OEBPS/ch03.xhtml)
- 结论依据:原文在此说明该机制、范围或取舍;本卡保留其历史语境,不将预测、产品状态或命令作为当前已核验事实。
- 原始内容:While testing various service mesh deployments, installing and uninstalling the mesh, do not uninstall by deleting the control plane first. Using Istio as an example, deleting the istio-system namespace without applying manifests to uninstall the mesh could cause you some grief because you might be left with a nonfunctional Kubernetes cluster where kubectl times out when communicating with the Kubernetes API server. When Istio isn’t cleaned up properly, especially when