This article explains how to add Oracle Cloud Infrastructure Registry (OCIR) in SWIFT by providing the OCIR region, tenancy details, and valid Oracle credentials. Once added, SWIFT validates the connection and allows discovery of container images from OCIR.
Pre-requisite:
1. Valid OCI authentication details: username/tenancy, auth token
2. Required permissions in OCI to pull images from OCIR.
add an Oracle Kubernetes Engine (OCIR) cluster in SWIFT, you need Oracle Cloud Infrastructure (OCI) credentials and configuration details. These credentials allow SWIFT to authenticate and connect to your OCI tenancy for registry discovery. We need to provide the UserID, Compartment ID, tenancy ID and fingerprint to discover the OKE cluster. For that please refer to the Pre-requisite Guide (pages 14–31) in the KB document provided below.
https://rackware.freshdesk.com/a/solutions/articles/5000888958?lang=en
Following are steps to discover the OCIR registry in SWIFT.
1. We need to login to the ‘SWIFT’ dashboard and navigate to the ‘container registries’ menu and click on ‘Add’ button. Please check below screenshot for your reference.
2. When you click on add button, it will appear a new window to add image registry, in that you need to provide OCI cloud credentials in order to add the OCIR in SWIFT.
| Field Name | Field Description |
| Friendly name | You need to enter a friendly name according to your cluster or project. |
| Registry Cloud Type | Select the Registry cloud type of OCI from the dropdown. |
| User ID | Unique identifier of the OCI IAM user used for authentication. |
| Compartment ID | Identifier of the OCI compartment where the OKE cluster resides. |
| Tenant ID | Unique identifier of your OCI tenancy (root account). |
| API Key Fingerprint | Identifier of the uploaded public key associated with the OCI user. |
| Realm Type | The Oracle Cloud realm that represents your geographic region (e.g., oc1). |
| Region | When adding OCIR in SWIFT, you need to specify the correct region endpoint so SWIFT knows where to connect and pull/push your container images |
| Username | In OCIR, the username is a combination of tenancy namespace and your OCI user name/email. |
| Tenancy Namespace | The tenancy namespace is a unique identifier automatically assigned to your OCI tenancy. It’s required when accessing OCIR because it ensures images are stored under the correct tenancy |
| Auth token | This is random string generated in OCI Console used instead of a password when authenticating with OCIR . |
| Private Key file | The private key (.pem) file that matches the public key uploaded to OCI. |
| User Email | The email linked to the OCI user |
3. After filling required details to add the OCIR , then click on 'Add' button. It will discover the OCIR. Please check below screenshot.
4. When you expand the added registry by clicking on the created image registry, you will see the summary and image repositories.
- When you go to the Summary tab, you will find information about the registry, such as user id, compartment ID, registry name and more.
- When you go to the Image Repositories tab, you will see all the images, tags, and repository URLs under the registry.
What next:
- Re-Discover : This option allows you to re-discover the image registry. If you have added new images or changed some image tags and want them to be reflected in the SWIFT portal, you can re-discover the image registry. Please refer to the link below for detailed steps on how to re-discover a Image registry.
<link>
- Configure : Use this option if you want to modify the image registry configuration. Please check KB Article on 'Configure the image registry'
<link>
- Delete : Use this option to delete the image registry. It will delete from SWIFT dashboard only not from cloud.
## Now that the image registry has been discovered, you may want to set up a DR Policy for Image registry sync Then follow below KB links.
<kb_link>
## If you want to sync one image registry with another, you can do that as well. For detailed steps, please refer to the KB article linked below.
<kb_link>