Kubernetes (kind / minikube) Integration Guide

Overview

Developers frequently run local Kubernetes clusters using kind or minikube. Cup’n’String scans local clusters, identifies active ingress controllers, and resolves service maps for secure policy management.

Support level

Auto-Discovered

What Cup’n’String detects

• Local clusters running under kind or minikube
• Active Kubernetes service endpoints
• Ingress configurations and namespace metadata

What it governs

• Local cluster ingress and egress policy routing
• Workstation access controls to the local cluster API
• Port-forwarding and service relay mapping

Recommended policies

• Audit local cluster endpoint exposures
• Restrict kind/minikube cluster access to authorized local agents
• Log all API port-forwarding activities

Setup outline

1. Ensure the Cup’n’String agent is active.
2. Spin up your local cluster using kind create cluster or minikube start.
3. The agent scans default Kubeconfig files (~/.kube/config) to discover cluster contexts.

Verification

Run a sample service inside the cluster and verify that it appears in your local agent dashboard under discovered services.

Troubleshooting

Verify KUBECONFIG environment variable points to the correct config location and that local clusters are reachable.

Known limitations

Does not enforce pod-level network policy internally; acts at the cluster boundary on the host network.