cleanstart/kube-proxy repository overview

CleanStart Container for Kube-Proxy

Kube-proxy is a critical Kubernetes networking component that maintains network rules on nodes. It implements part of the Kubernetes Service concept, handling UDP, TCP and SCTP stream forwarding or round-robin TCP/UDP/SCTP forwarding across a set of backend pods. This container provides a hardened, enterprise-ready kube-proxy implementation with enhanced security features, monitoring capabilities, and optimized performance for production environments. It includes built-in support for IPVS mode, iptables mode, and userspace mode, allowing flexible deployment options based on specific networking requirements.

📌 CleanStart Foundation: Security-hardened, minimal base OS designed for enterprise containerized environments.

Key Features

• Advanced network proxy for Kubernetes service abstraction
• Support for IPVS, iptables, and userspace proxy modes
• Integrated service discovery and load balancing
• Enhanced security features with FIPS compliance options

Common Use Cases

• Kubernetes cluster networking and service load balancing
• Internal service discovery and traffic routing
• Cross-cluster service communication
• Network policy enforcement and traffic management

Quick Start

Pull Latest Image Download the container image from the registry

docker pull cleanstart/kube-proxy:latest
docker pull cleanstart/kube-proxy:latest-dev

Basic Run Run the container with basic configuration

docker run -it --name kube-proxy-test cleanstart/kube-proxy:latest-dev

Production Deployment Deploy with production security settings

docker run -d --name kube-proxy-prod \
  --read-only \
  --security-opt=no-new-privileges \
  --user 1000:1000 \
  cleanstart/kube-proxy:latest

Volume Mount Mount local directory for persistent data

docker run -v $(pwd)/data:/data cleanstart/kube-proxy:latest

Port Forwarding Run with custom port mappings

docker run -p 8080:80 cleanstart/kube-proxy:latest

Configuration

Environment Variables

Security & Best Practices

Recommended Security Context

securityContext:
  runAsNonRoot: true
  runAsUser: 1000
  runAsGroup: 1000
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ['ALL']

Best Practices

• Use specific image tags for production (avoid latest)
• Configure resource limits: memory and CPU constraints
• Enable read-only root filesystem when possible
• Run containers with non-root user (--user 1000:1000)
• Use --security-opt=no-new-privileges flag
• Regularly update container images for security patches
• Implement proper network segmentation
• Monitor container metrics for anomalies

Architecture Support

Multi-Platform Images

docker pull --platform linux/amd64 cleanstart/kube-proxy:latest
docker pull --platform linux/arm64 cleanstart/kube-proxy:latest

CleanStart Images: https://images.cleanstart.com/⁠

Community Images:
Docker Hub: https://hub.docker.com/u/cleanstart⁠
GitHub: https://github.com/cleanstart-containers⁠
AWS ECR Public Gallery: https://gallery.ecr.aws/cleanstart/⁠

Presence on Social Media:
Community: https://www.linkedin.com/groups/18324021/⁠
YouTube: https://www.youtube.com/@CleanStartOfficial⁠

Contribute to Container Use Cases: https://github.com/cleanstart-dev/cleanstart-use-cases/⁠

⁠Vulnerability Disclaimer

CleanStart offers Docker images that include third-party open-source libraries and packages maintained by independent contributors. While CleanStart maintains these images and applies industry-standard security practices, it cannot guarantee the security or integrity of upstream components beyond its control.

Users acknowledge and agree that open-source software may contain undiscovered vulnerabilities or introduce new risks through updates. CleanStart shall not be liable for security issues originating from third-party libraries, including but not limited to zero-day exploits, supply chain attacks, or contributor-introduced risks.

Security remains a shared responsibility: CleanStart provides updated images and guidance where possible, while users are responsible for evaluating deployments and implementing appropriate controls.