Accès au registre OCI pour les déploiements conteneurisés

BOC provides ADONIS from version 19.0.0, ADOIT from version 21.0.0, and ADOGRC from version 15.0.0 as OCI images for containerized deployments.
The images are made available through a public OCI registry and can be integrated into existing Kubernetes or Docker environments. Additionally, Helm charts for Kubernetes are provided.

How do I get access to the OCI Registry?

If you want to install a BOC product as a container deployment, you will need credentials for the OCI registry. These are provided individually after reviewing your request.

Please create a ticket via the BOC Support Portal.

Important:
When creating the ticket, select the category "I want to use a service" and then "Receive credentials for the OCI registry."

What information is required?

Please provide the following information in your request:

• Company name – Official company name of your organization.
• Contact person – Name and email address of the Application Owner.
• Product(s) – The BOC products you want to deploy containerized.
• Contact for delivery of credentials – Email address and mobile phone number of the technical person responsible for installation, management, and use of the OCI images as well as your local OCI registry.

The mobile phone number is required for two-factor authentication (2FA). If you cannot provide a mobile phone number, please note this in your request.

How do I receive the installation package?

After successful review of your request, you will receive the OCI registry credentials at the specified technical contact. You can then download the required OCI images and Helm charts directly from the registry and integrate them into your infrastructure.

For Docker deployments, BOC also provides a sample docker-compose.yml in the GitHub repository, which can be used as a starting point for installation.

Recommendation for production use

The provided credentials allow up to four downloads per month and product. For production environments, BOC therefore recommends using your own local registry.

• Caching proxy / pull-through cache for caching the images.
• Local mirroring of the required images into an internal registry. This option is also suitable for air-gapped environments.

Further information on installation and configuration can be found in the respective product documentation.