Create a Container Registry instance
You can create a custom Container Registry within your space.
During creation, you can define the characteristics, such as the name, the version and the visibility.
Once the Container Registry instance has been created, you can retrieve the administrator password that allows you to connect to Harbor.
The choice between a Private and a Public network determines who can access your registry:
-
Private: your Container Registry is only accessible within the internal Numspot network. Only your other resources located in the same network can connect to it. This option is recommended for production environments, in particular SecNumCloud environments. To access it securely, you can use a bastion VM (Virtual Machine) and a Numspot VPN (Virtual Private Network).
-
Public: your Container Registry is accessible from the Internet. Anyone with the connection credentials can connect to it, wherever they are located. This option is suitable for development, testing or environments where network security is not critical.
Recommendation: To ensure the security of your data in production, always favor a Private network.
Permissions
This action requires the following IAM (Identity and Access Management) permissions:
- registry.instance.create
- API
The POST /registry/spaces/{spaceId}/registries request lets you create and launch a Harbor registry.
The Container Registry is in a PENDING state until it is created, then moves to the RUNNING state.
Choosing the network type:
- Public: specify
"visibility": "EXTERNAL" - Private: specify
"visibility": "INTERNAL"
Example request
{
"name": "my-container-registry",
"version": "2.14",
"visibility": "EXTERNAL"
}
Example response
{
"id": "550e8400-e29b-41d4-a716-446655440002",
"name": "my-container-registry",
"status": {
"state": "RUNNING",
"message": "instance is healthy"
},
"version": "2.14",
"host": "my-container-registry.registry.eu-west-2.numspot.com",
"visibility": "EXTERNAL"
}