Manage Container Registries
This guide provides instructions on integrating the container registry with the KubeRocketCI.
Supported Registry Providersβ
The following table displays the registry services supported for both OpenShift and Kubernetes clusters.
Container Registry | OpenShift | Kubernetes |
---|---|---|
AWS ECR | β | β |
DockerHub | β | β |
Harbor | β | β |
Nexus | β | β |
GitHub (GHCR) | β | β |
Add Container Registryβ
Follow a three-step process to integrate a container registry in KubeRocketCI:
-
In the Configuration -> Artifacts storage -> Registry click the + Add Registry button:
-
Select Registry Provider and enter the required details.
-
Confirm settings by clicking the Save button.
The required fields vary depending on which container registry is chosen:
- AWS ECR
- DockerHub
- Harbor
- Nexus
- GitHub
Fields Description Registry Endpoint Format for the (AWS) Elastic Container Registry endpoint: xxxxxxxxxxxx.dkr.ecr.<region>.amazonaws.com. Where xxxxxxxxxxxx
is your AWS account ID and\<region\>
is where your ECR is hosted.Registry Space The suffix project name in registry. AWS Region The geographic area where the (AWS) Elastic Container Registry repository is hosted. Authentication/IRSA Role ARN Specify the IAM role with a policy for interacting with ECR with your Kubernetes cluster. Fields Description Registry Space The unique identifier/name of the user or company linked to your DockerHub account. User The user account ID or community user account ID with push permission. Password/Token Provide the Password/Token corresponding to your DockerHub account. It is recommended to use Token for security purposes. Checkbox/Use the Push Account's credentials Check this to use the same account for pulling and pushing operations. If unchecked, please enter the user account ID and Password/Token for your DockerHub account or community user account ID with pull permission. Fields Description Registry Endpoint Enter Harbor registry endpoint URL, for example, registry.example.com. Registry Space The project name in registry. User Provide the robot account name with push permissions. Password/Token Provide the secret corresponding to your harbor account. Checkbox/Use the Push Account's credentials Check this to use the same account for pulling and pushing operations. Provide the account name with pull permissions. Fields Description Registry Endpoint Nexus service registry endpoint URL (e.g., image-registry.nexus-image-registry.svc:5000). Repository Specify the Nexus repository that corresponds to your project. User Provide the username with push permissions. Password/Token Enter the confidential combination used for authenticating your access to the container registry. Fields Description Registry Space The unique identifier/name of the user or company linked to your GitHub account. User The user account ID or community user account ID with push permission. Password/Token Provide the Token corresponding to your GitHub account. The minimal set of permissions required for the token is described in the Manage Git Providers. Checkbox/Use the Push Account's credentials Check this to use the same account for pulling and pushing operations. If unchecked, please enter the user account ID and Token for your GitHub account or community user account ID with pull permission.
Remove Container Registryβ
To remove container registry integration from KubeRocketCI, follow the steps below:
Proceed with caution, removing registry settings might disrupt your CI/CD process. All new components created after changing the registry such as Components and Environments will start working out of the box. To work with existing codebases and pipelines familiarize with the change container registry guide.
-
In the Configuration -> Artifacts storage -> Registry.
-
Click the Reset registry button, type the
confirm
word and then click Confirm: