bridgecrew/cas-image-registry-sync-scheduler repository overview

⁠Private Registry with Disposable Tokens

⁠Introduction

The Private Registry with Disposable Tokens is a project that allows you to securely access private container registries (e.g., AWS Elastic Container Registry - ECR) using disposable tokens. It aims to simplify the authentication process when pulling images from private registries, ensuring that tokens are short-lived and automatically refreshed.

With this project, you no longer need to manage long-lived access keys or tokens manually. Instead, it provides an automated mechanism to generate and manage disposable tokens for seamless integration with Kubernetes clusters, CI/CD pipelines, and other container orchestration tools.

⁠Features

• Automatic pulling of disposable tokens for private registries.
• Secure handling of credentials using Kubernetes Secrets.
• Easy integration with Kubernetes clusters and other container orchestration platforms.
• Short-lived tokens for improved security and reduced risk of misuse.
• Seamless token refresh mechanism for continuous access to private registries.

⁠Getting Started

⁠Prerequisites

Before using the Private Registry with Disposable Tokens, ensure you have the following prerequisites:

• Kubernetes cluster (minikube or other cluster setups).
• Docker or container runtime installed.
• Endpoint and token to produce the registery token

⁠Setup

1. Clone helm chart registrycredsscheduler

2. Update chart values, token and region endpoint

3. Install: helm install registrycredsscheduler .

⁠FAQ

Q: Can I use this project with other container registries besides AWS ECR?

A: Yes, you can configure the project to work with other private registries as well. Customize the token generator and token updater settings accordingly.

Q: How often are the disposable tokens refreshed?

A: The tokens are refreshed automatically every 11h and expierd every 12h.

Q: Are the credentials and tokens stored securely?

A: Yes, the project uses Kubernetes Secrets to handle credentials and tokens securely.

⁠Contributing

Contributions are welcome! If you find any issues or have improvements to suggest, please open an issue or submit a pull request.