Summary
Support namespace-scoped IP pools to enable multi-tenancy, allowing different teams or environments to manage their own isolated IP address pools.
Benefits
- Teams can self-service their own IP pools without conflicts
- RBAC can be scoped per namespace for fine-grained access control
- Supports organizational separation (dev/staging/prod, team A/team B)
- Prevents accidental cross-team IP allocation
Suggested Approach
- Make
NetworkConfig CRs namespace-scoped (currently cluster-scoped or single-namespace)
- Add namespace filtering to gRPC queries
- Support cross-namespace views for platform admins
- Helm chart updates for multi-namespace RBAC
🤖 Generated with Claude Code
Summary
Support namespace-scoped IP pools to enable multi-tenancy, allowing different teams or environments to manage their own isolated IP address pools.
Benefits
Suggested Approach
NetworkConfigCRs namespace-scoped (currently cluster-scoped or single-namespace)🤖 Generated with Claude Code