cameleer/cameleer-saas
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

Epic: Networking & Tenant Isolation #8

New Issue
Open
opened 2026-03-29 23:17:33 +02:00 by claude · 0 comments
claude commented 2026-03-29 23:17:33 +02:00
Owner
Copy Link

Overview

Network-level tenant isolation on shared infrastructure, plus future VPN connectivity for customer backend access.

Day 1: Namespace Isolation

  • K8s NetworkPolicies per tenant namespace
  • Default deny all ingress/egress between tenant namespaces
  • Allow: tenant namespace → shared PostgreSQL/OpenSearch (with authentication)
  • Allow: tenant namespace → public internet (for Camel app external connectivity)
  • Allow: SaaS platform namespace → all tenant namespaces (management access)
  • Allow: tenant's Camel apps → tenant's cameleer3-server (intra-namespace)

Day 1: External Connectivity

  • Customer Camel apps connect to external systems over public internet
  • TLS required for all external connections
  • Platform-managed secrets for connection credentials (see Secrets epic)

Future: VPN / Private Connectivity

  • VPN gateway per tenant for private network access
  • WireGuard or IPsec tunnels to customer infrastructure
  • Private DNS resolution for customer internal hostnames
  • Split tunneling (only customer-bound traffic through VPN)

Future: Dedicated Tier Networking

  • Dedicated clusters with custom CIDR ranges
  • VPC peering or direct connect options
  • Customer-managed firewall rules

Security

  • No cross-tenant network paths on shared infra
  • Regular NetworkPolicy audit
  • Egress filtering (optional, per-tier)
## Overview Network-level tenant isolation on shared infrastructure, plus future VPN connectivity for customer backend access. ## Day 1: Namespace Isolation - K8s NetworkPolicies per tenant namespace - Default deny all ingress/egress between tenant namespaces - Allow: tenant namespace → shared PostgreSQL/OpenSearch (with authentication) - Allow: tenant namespace → public internet (for Camel app external connectivity) - Allow: SaaS platform namespace → all tenant namespaces (management access) - Allow: tenant's Camel apps → tenant's cameleer3-server (intra-namespace) ## Day 1: External Connectivity - Customer Camel apps connect to external systems over public internet - TLS required for all external connections - Platform-managed secrets for connection credentials (see Secrets epic) ## Future: VPN / Private Connectivity - VPN gateway per tenant for private network access - WireGuard or IPsec tunnels to customer infrastructure - Private DNS resolution for customer internal hostnames - Split tunneling (only customer-bound traffic through VPN) ## Future: Dedicated Tier Networking - Dedicated clusters with custom CIDR ranges - VPC peering or direct connect options - Customer-managed firewall rules ## Security - No cross-tenant network paths on shared infra - Regular NetworkPolicy audit - Egress filtering (optional, per-tier)
claude added the epicnetworking labels 2026-03-29 23:18:02 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auth
Identity, authentication, OIDC, RBAC
 billing
Billing, metering, and Stripe integration
 day-1
Required for initial launch
 epic
Top-level epic grouping related issues
 future
Planned for future release
 infra
Infrastructure, GitOps, K8s orchestration
 licensing
License module and feature gating
 networking
Network isolation, VPN, tenant separation
 observability
Observability integration (cameleer3-server)
 ops
Platform operations and self-monitoring
 phase-1
Phase 1: Foundation + Auth
 phase-2
Phase 2: Tenants + Licensing
 phase-3
Phase 3: Runtime Orchestration + Environments
 phase-4
Phase 4: Observability Pipeline + Inbound Routing
 phase-5
Phase 5: K8s Operational Layer
 phase-6
Phase 6: Billing + Metering
 phase-7
Phase 7: Billing + Metering
 phase-8
Phase 8: Security Hardening + Self-Monitoring
 phase-9
Phase 9: Frontend (React Shell)
 platform
SaaS management platform
 runtime
Camel application runtime
 secrets
Secrets management and vault integration
 security
Security, compliance, SOC 2, audit
 task
Implementation task within a phase
No Label epic networking
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-saas#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?