How tigera-cs/quickstart-self-service works
Project Type and Purpose
– This is not a traditional codebase but a self-guided workshop repository. Its goal is to teach “identity-aware microsegmentation” in Kubernetes using Calico Cloud. The “modules” folder holds instructional Markdown files; the “manifests” folder contains the YAML you apply against your cluster (apps and policy tiers).
File Structure Highlights
• Root
– README.md (workshop overview)
– quickstart-self-service.code-workspace
• manifests/
– apps/ (sample Kubernetes apps: Bookinfo, HipsterShop, YaoBank, LoadGenerator)
– Policies/ (5 security policy tiers: Default, Security, Platform, Application, AppSec)
– ingress/ (Ingress resource definitions per app)
– basepolicies/ (baseline tiered policy examples)
– securitypolicies/ (stage-by-stage policy snapshots for Steps 3–5)
• modules/
– module-n-intro.md (conceptual introductions)
– deploy-*.md, connect-*.md (lab instructions)
– analyze-*.md (flow analysis, service graphs, network sets)
Key Insights from README
– Workshop is organized into 5 Modules:
1. Lab Setup (cluster onboarding, app + ingress deployment)
2. Policy Constructs (anatomy of a Calico Policy)
3. Security-Tier Framework (Default, Security, Platform, Application, AppSec tiers)
4. Zero-Trust Methodology (Identify → Analyze → Deploy → Enforce → Remediate)
5. (Future content)
Main Components
a. Participant Environment
– CLI workstation (kubectl, Tigera CLI)
– Flow log aggregator (e.g., Elasticsearch/Kibana)
b. Calico Cloud Control Plane
– Policy manager API
– Service Graph engine
c. Kubernetes Cluster
– Control Plane (API Server, etcd, Controller Manager)
– Data Plane: worker nodes with Calico CNI plugin
– Pods running microservices (frontend, adservice, cartservice, etc.)
– Ingress Controller & Ingress resources
d. External Dependencies
– DNS (kube-dns/CoreDNS)
– External networks/third-party services (e.g., AlienVault IP Threat Feed)
Relationships & Interactions
– Participant pushes YAML manifests (apps + policy tiers) to the API Server
– Calico Cloud control plane reconciles policies → distributes to Calico CNI on nodes
– Ingress Controller routes inbound traffic to frontends, flows east-west between services
– Pods query DNS and external services via defined NetworkSets and tiers
– Flow logs & Service Graph telemetry are shipped to Kibana; used to iterate policy rules
Architectural Patterns & Principles
– Microservices pattern: each service in its own namespace/pod, connected via service mesh (network policies)
– Layered security tiers: policies applied in order (Default → Security → Platform → Application → AppSec)
– Zero-Trust: default-deny posture, iterative allow-listing based on observed flows
– Declarative infrastructure: manifests hold entire desired state
Technologies & Frameworks
– Kubernetes (API Server, Controller Manager, etcd, kube-dns)
– Calico Cloud (Cloud Control Plane, Service Graph, Policy APIs)
– Calico CNI plugin (policy enforcement at the data plane)
– Ingress Controller (Kubernetes Ingress resource support)
– Elasticsearch/Kibana (flow log storage, visualization)