cleanstart/trust-manager repository overview

Container Documentation for Trust-Manager

Trust Manager is a Kubernetes operator that automates X.509 certificate management and rotation for cloud-native applications. It provides automated certificate lifecycle management, integration with popular certificate authorities, and secure key storage capabilities for enterprise environments.

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

Key Features Core capabilities and strengths of this container

• Automated X.509 certificate lifecycle management
• Integration with multiple certificate authorities
• Secure key storage and rotation
• Kubernetes-native architecture

Common Use Cases Typical scenarios where this container excels

• TLS certificate automation in Kubernetes clusters
• PKI infrastructure management
• Secure service-to-service communication
• Zero-trust security implementations

Pull Latest Image Download the container image from the registry

docker pull cleanstart/trust-manager:latest

docker pull cleanstart/trust-manager:latest-dev

Basic Run Run the container with basic configuration

docker run -it --name trust-manager-test cleanstart/trust-manager:latest-dev

Production Deployment Deploy with production security settings

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

Volume Mount Mount local directory for persistent data

docker run -v $(pwd)/data:/data cleanstart/trust-manager:latest

Port Forwarding Run with custom port mappings

docker run -p 8080:80 cleanstart/trust-manager:latest

Environment Variables Configuration options available through environment variables

Security Best Practices Recommended security configurations and practices

• Use specific image tags for production deployments
• Implement proper RBAC policies
• Enable audit logging
• Regular certificate rotation
• Secure storage of private keys
• Network policy implementation
• Regular security scanning
• Backup of certificate data

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/trust-manager:latest
docker pull --platform linux/arm64 cleanstart/trust-manager: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.