Isolate full-deployment Kafka and ZooKeeper from tenant action pods on 0.9.0
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 38/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- kubernetes, python
調査の方向性
Start by reading the operator code that applies NetworkPolicies and handles resume and Whisk updates; the payload does not name specific files or tests. Confirm how Kafka and ZooKeeper policies are reconciled, workloads are ordered, and legacy pods are restarted. Done means tenant action pods cannot reach either service while trusted clients, monitoring, and scheduled actions continue to work on a NetworkPolicy-enforcing CNI.
索引モデルが issue の本文から書いたものです。
説明
Problem
In the 0.9.0 full deployment, ordinary tenant action pods can reach the shared Kafka and ZooKeeper endpoints. These are internal control-plane services and should not be accessible to tenant code. The deployment does not install a network boundary restricting those services to their intended clients.
This is an internal multi-tenant isolation problem. It does not establish an unauthenticated Internet-facing entry point, and slim installations without Kafka/ZooKeeper are outside this issue.
Attacker and risk
| Actor / position | Preconditions | Risk |
|---|---|---|
| Anonymous Internet client | Only the public HTTP ingress is exposed | No direct Kafka/ZooKeeper access demonstrated by these checks |
| Ordinary tenant/developer | Can deploy and invoke an action in their own namespace | Reachable unauthenticated shared messaging and coordination endpoints; potential cross-tenant confidentiality, integrity and availability impact |
| Host or Kubernetes administrator | Already controls the cluster | Outside the tenant-isolation boundary |
Expected behavior
Action pods must be denied access to Kafka and ZooKeeper by Service name, pod DNS name and pod IP. Controller/invoker traffic, broker coordination and monitoring must keep working.
Updating the operator on an existing full installation must install the protection automatically, including closing pre-existing messaging connections.
Proposed change
The accompanying operator PR targets 0.9.0 and adds narrow same-namespace ingress NetworkPolicies for Kafka and ZooKeeper. Trusted client selectors exclude every pod carrying user-action-pod, regardless of its value. Metrics access is limited to the installation's Prometheus pods.
The operator applies policies before workloads, rolls legacy messaging pods once, waits for completion, and reconciles enabled ZooKeeper then Kafka during resume and Whisk updates. Failures propagate; disabled components are skipped.
This requires a CNI that enforces NetworkPolicy. A policy object alone is not proof of isolation. The change preserves component versions, protocols and PVC contents; it does not add Kafka SASL/TLS or ZooKeeper authentication.
Validation
Local synthetic K3s lab:
- 16/16 tenant connection attempts were reachable in the legacy fixture and denied after automatic operator resume.
- Legitimate clients, Prometheus, action-labelled spoof checks and foreign-namespace checks passed.
- Repeating operator resume preserved messaging pod identities.
- Alpha/Beta application tests: 15/15; Redis Lua: 84/84; Streamer: 24/24.
- Scheduled actions continued working, and application source remained unchanged.
- Operator unit suite: 66/66, including 19 focused messaging tests.
The lab exercised operator image replacement/restart and the real Kopf resume handler. The exact ops update operator CLI command was not run with the unpublished local image.
Known limitation
Whisk uninstall still relies on owner garbage collection when the process-local saved component spec is absent. Policy-last teardown is therefore not guaranteed during uninstall. This was identified in the targeted review and accepted by the contributor as a non-blocking limitation of this proposal. It remains disclosed for maintainer assessment.
- 主要言語
- Python
- スター
- 577
- フォーク
- 29
- 平均マージ
- 4日 23時間
- マージ済み PR（30日）
- 3
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
apache/openserverless のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
apache/openserverless#269 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
apache/openserverless#267 ·
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 20/100
apache/openserverless#275 ·
-
難易度 5/5 1週間以上 初心者へのやさしさ 20/100
apache/openserverless#274 ·
-
難易度 5/5 1週間以上 初心者へのやさしさ 8/100
apache/openserverless#273 · コメント 2 件 ·
apache/openserverless の issue をすべて見る
似ている issue
-
infrastructure
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
khuisman/mcp-gee-sweet#1152 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
-
backroom bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
ditto-assistant/ditto-subnet#3069 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
open-webui/open-webui#32901 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
0.3.3 bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信