Container Providers

A Container Provider is an integration that allows you to manage container environments (e.g., Docker Swarm, Kubernetes) within the platform. It centralizes configuration, certificates, secrets, and images to simplify deployment and operations.

Note

When a Container Provider is created in Reemo, it is disabled by default and must be explicitly enabled by an instance administrator.

Overview

The Container Providers list displays:

• Name: identifier chosen by the administrator.

• Type: technology used (e.g., SWARM).

• Multi-cluster: deployment across one or more clusters.

• Visibility: Public or Private.

• State: Enabled or Disabled.

• Test: connectivity validation button.

List of Container Providers

Creating a Container Provider

1. Click New Provider.

2. Fill in the fields:

   • Name: provider name.

   • Type: choose SWARM or Kubernetes.

   • Visibility: Public or Private.

   • Multi-cluster deployment: enable or disable multi-cluster management (Active/Passive or Active/Active).

   • Comments: administrative notes.

Container Provider creation form

3. Example configuration of a SWARM cluster:

   • Cluster name: internal identifier.

   • URL: API access endpoint of the cluster.

   • Server Name (SNI): optional.

   • Cert Auth: enable if certificate-based authentication is required.

   • Certificate: select an existing certificate from the Certificates module.

SWARM cluster configuration

Container Provider Overview

The Configuration tab displays the provider’s main settings.

Configuration of a Container Provider

Node Management

The Nodes tab lists the nodes attached to the provider’s cluster. For each node, you will find:

• IP and name.

• Labels: configurable metadata (e.g., location: europe).

• State: status (Ready, Down…).

• Availability: Active, Pause, Drain.

• Reachability: connectivity status.

Cluster node list

Available actions:

• Edit: change node availability.

• Labels: manage custom labels.

Editing node availability

Adding or editing node labels

Label management works together with the Constraints system in an organization’s container profiles. For example, you could define node labels such as:

• Type = NOGPU

• Location = PARIS

Then, in a container profile, you could specify placement constraints:

• Type EQUAL NOGPU

• Location EQUAL PARIS

This ensures that all containers from that profile are deployed on nodes matching these constraints.

Secret Management

The Secrets tab centralizes management of Docker Secrets associated with the provider. They can be used by containers or services.

Each secret includes:

• Creation date.

• Unique ID.

• Logical name.

Managing provider secrets

Image Management

The Images tab allows declaring and enabling container images usable by the provider.

For each image:

• Name.

• State: Enabled or Disabled.

• Visibility: Public or Private.

List and management of available images

Private Container Provider Associations

A Container Provider can be defined as Public or Private:

• Public: automatically accessible by all organizations without additional configuration.

• Private: must be explicitly associated with the organizations that need it.

This distinction makes it easy to share global resources (Public) or reserve environments for specific organizations (Private).

Managing Associations

From an organization’s Container Providers section, you can associate a Private Container Provider available on the platform.

List of Container Providers associated with an organization

Adding a Private Container Provider

To associate a Private Container Provider with an organization:

1. Click Add private provider.

2. Select the desired provider from the dropdown list.

3. Save the association.

Associating a Private Container Provider with an organization

Summary

The Container Providers module offers:

• Centralized configuration.

• Management of nodes, images, and secrets.

• Reuse of certificates for authentication and security.

• Multi-cluster deployment support.

• Public Container Providers are visible to all organizations.

• Private Container Providers require explicit association.

This simplifies administration and strengthens consistency across container environments.