1장. Integrating with image registries
Red Hat Advanced Cluster Security for Kubernetes (RHACS) integrates with a variety of image registries so that you can understand your images and apply security policies for image usage.
When you integrate with image registries, you can view important image details, such as image creation date and Dockerfile details (including image layers).
After you integrate RHACS with your registry, you can scan images, view image components, and apply security policies to images before or after deployment.
When you integrate with an image registry, RHACS does not scan all images in your registry. RHACS only scans the images when you:
- Use the images in deployments
-
Use the
roxctlCLI to check images - Use a continuous integration (CI) system to enforce security policies
You can integrate RHACS with major image registries, including:
- Amazon Elastic Container Registry (ECR)
- Docker Hub
- Google Container Registry (GCR)
- Google Artifact Registry
- IBM Cloud Container Registry (ICR)
- JFrog Artifactory
- Microsoft Azure Container Registry (ACR)
- Red Hat Quay
- Red Hat container registries
- Sonatype Nexus
- GitHub container registry (GHCR)
- Any other registry that uses the Docker Registry HTTP API
1.1. Automatic configuration 링크 복사링크가 클립보드에 복사되었습니다!
Red Hat Advanced Cluster Security for Kubernetes includes default integrations with standard registries, such as Docker Hub and others. It can also automatically configure integrations based on artifacts found in the monitored clusters, such as image pull secrets. Usually, you do not need to configure registry integrations manually.
- If you use a Google Container Registry (GCR), Red Hat Advanced Cluster Security for Kubernetes does not create a registry integration automatically.
- If you use Red Hat Advanced Cluster Security Cloud Service, automatic configuration is unavailable, and you must manually create registry integrations.