cleanstart/stakater-reloader repository overview

Container Documentation for Stakater-Reloader

Stakater-Reloader is a Kubernetes controller that automatically triggers updates to deployments, daemonsets, and statefulsets when their configmaps or secrets change. It enhances application configuration management by eliminating the need for manual pod restarts, ensuring applications always run with the latest configuration.

📌 Base Foundation: Security-hardened, minimal base OS designed for enterprise containerized environments from Cleanstart Registry.

Key Features Core capabilities and strengths of this container

• Automatic pod reload on ConfigMap/Secret changes
• Zero-downtime configuration updates
• Support for multiple Kubernetes workload types
• Annotation-based configuration

Common Use Cases Typical scenarios where this container excels

• Dynamic configuration management in Kubernetes
• Automated application updates
• Secret rotation automation
• Zero-downtime configuration updates

Pull Latest Image Download the container image from the registry

docker pull cleanstart/stakater-reloader:latest

docker pull cleanstart/stakater-reloader:latest-dev

Basic Run Run the container with basic configuration

docker run -it --name reloader cleanstart/stakater-reloader:latest

Production Deployment Deploy with production security settings

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

Shell Access Entrypoint Shell Access

   docker run -it --rm --entrypoint sh cleanstart/stakater-reloader:latest-dev

Inspect Environment Inspection of the image

docker inspect cleanstart/stakater-reloader:latest

Environment Variables Configuration options available through environment variables

Security Best Practices Recommended security configurations and practices

• Use RBAC with minimal required permissions
• Enable read-only root filesystem
• Run as non-root user
• Implement network policies
• Regular security updates
• Monitor reloader activities

Kubernetes Security Context Recommended security context for Kubernetes deployments

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

Multi-Platform Images

docker pull --platform linux/amd64 cleanstart/stakater-reloader:latest
docker pull --platform linux/arm64 cleanstart/stakater-reloader:latest

⁠Documentation Resources

Essential links and resources for further information

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.