GitOps Quay integration
Integrate Quay with GitOps for image enrichment
Codefresh offers native support for integrating with Quay, enabling seamless pushing, pulling, and deploying of container images.
By adding a Quay integration in Codefresh, you can reference the integration account in external CI tools, such as GitHub Actions, using the integration name instead of managing explicit credentials. This simplifies security and enhances the ease of managing integrations in GitOps.
For general information on container registry integrations for GitOps, see Container registry GitOps integrations.
Prerequisites
- Create a Redhat/Quay account at Quay.
- Optional. For Codefresh integration, create a robot account.
Quay-GitOps integration settings in Codefresh
Setting | Description |
---|---|
Integration name | A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. |
All Runtimes/Selected Runtimes | The runtimes in the account with which to share the integration resource. The integration resource is created in the Git repository with the shared configuration, within resources . The exact location depends on whether the integration is shared with all or specific runtimes:
|
Domain | Set to quay.io . |
Username | The Quay.io username. |
Password | The Quay.io encrypted password, or robot account if you created one. |
For how-to instructions, see Configure container registry integrations for GitOps in Codefresh and Edit/delete container registry integrations for GitOps in Codefresh.
Make sure you have the:
- Quay domain username
- Quay domain-encrypted password or that of the robot account
Related articles
Shared Configuration Repository
Image enrichment with GitOps integrations
GitOps CI integrations
GitOps issue-tracking integrations