Connect a Container Registry

microtica allows you to connect your own docker registries where you would store docker images built during pipeline execution you can use images to deploy services on kubernetes clusters currently, microtica supports two types of private docker registries dockerhub amazon ecr gitlab container registry connect your dockerhub registry in order to connect with dockerhub registry you would need to first create a personal access token from dockerhub portal https //hub docker com/ go to your account settings and click on security tab from the side menu on the left click on new access token button to create new access token a dialog will appear asking you to enter the name of the access token enter a name that will distinguish this token from others (e g microtica pipelines) click on create button and new access token will be generated copy the value of the token in the clipboard, we would need the value in the next step revoking access to dockerhub if you decide to revoke the access to your registry you just need to deactivate or completely remove the access token from the dockerhub portal the last thing we need to do is to add the registry in microtica portal to do that go to project integrations > container registries default registry if you mark the registry as default, when composing pipelines, if you don’t specify the registry the default registry will be used automatically connect your amazon ecr registry in order to connect with amazon ecr registry you would need to first create an iam user from aws console https //console aws amazon com/iam/home from the iam console choose users and click on add user button top left choose a username for the new user and select programmatic access for access type and click on next permission button now we have to choose the permissions to assign to this user in this particular case we only need access to the ecr service select the attach existing policies directly option and search for “container” then select amazonec2containerregistryfullaccess policy and click on next tags button in the bottom right follow the next step and at the end click on create user button new access keys are now generated copy the value of the keys in the clipboard, we would need the values in the next step the last thing we need to do is to add the registry in microtica portal to do that go to project integrations > container registries choose a simple and easy to remember name when creating a registry the name will be used when referencing it from the pipeline steps enter the access key id and secret access key as provided in the aws console default registry if you mark the registry as default, when composing pipelines, if you don’t specify the registry the default registry will be used automatically connect your gitlab container registry in order to connect with gitlab container registry you would need to login into your gitlab account from the profile menu go to preferences and then choose the access tokens tab next, generate a new token with write registry permission selected the last thing we need to do is to add the registry in microtica portal to do that go to project integrations > container registries choose a simple and easy to remember name when creating a registry the name will be used when referencing it from the pipeline steps enter the token name and token value as provided in the gitlab portal default registry if you mark the registry as default, when composing pipelines, if you don’t specify the registry the default registry will be used automatically