Skip to content

M2: Implement CiliumNetworkPolicies for namespace isolation #8

@CodeBuildder

Description

@CodeBuildder

Goal

Apply CiliumNetworkPolicies to enforce default-deny ingress and cross-namespace isolation.

Policies to implement

File Policy
default-deny-ingress.yaml Deny all ingress to pods in prod and staging by default
deny-cross-namespace.yaml Deny cross-namespace traffic except from monitoring and argus-system

Tasks

  • Implement security/cilium/default-deny-ingress.yaml
  • Implement security/cilium/deny-cross-namespace.yaml
  • Apply both policies and verify with hubble observe
  • Confirm Prometheus scraping from monitoring namespace still works
  • Confirm argus-system agent can reach pods in prod/staging

Acceptance criteria

  • Cross-namespace traffic blocked by default (visible in Hubble as dropped flows)
  • Explicit allow rules work correctly
  • Prometheus scrape targets remain reachable

Depends on

#4

Metadata

Metadata

Assignees

No one assigned

    Labels

    module-2Security LayerssecuritySecurity policies and tools

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions