知识卡片
默认拒绝后逐项开放流量
微分段可先用网络策略默认拒绝 Pod 的入站和出站流量,再按实际依赖逐项开放 DNS、服务调用与入口路径。每条网格路由都要对应底层允许规则,否则控制面可发现目标,实际请求仍会被拦截。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
At this point the service mesh legacy conference service can discover where the attendees are via the sidecar, however the request itself would be blocked. Every routing rule in service mesh needs a corresponding allow rule defined in the network policy adapter. In this final example, we open up the rule for the legacy conference system to communicate with the Attendee service:
参考来源
- 位置:《Mastering API Architecture》第9章《Using API Infrastructure to Evolve Toward Cloud Platforms》之《Role of Service Mesh in Zero Trust Architectures》(源文件:_epub-src/OEBPS/ch09.xhtml)
- 结论依据:原文依次展示默认拒绝、开放 DNS 和服务出站,并要求网格路由对应网络策略允许规则。
- 原始内容:At this point the service mesh legacy conference service can discover where the attendees are via the sidecar, however the request itself would be blocked. Every routing rule in service mesh needs a corresponding allow rule defined in the network policy adapter. In this final example, we open up the rule for the legacy conference system to communicate with the Attendee service: