Overview

The ConfigSeeder ecosystem consists of several components. The aim of this article is to provide an overview of all ConfigSeeder components. The following graphic shows all ConfigSeeder components:

In addition to this article please also see our documentation for quick start guides and detailed information. Please don’t hesitate to contact us if we miss a component which we should absolutely offer.

Components

ConfigSeeder Management

ConfigSeeder Management is the main component of the ConfigSeeder ecosystem and is responsible for the following functionalities:

• Storing all configuration data in a secured (encrypted) way
• Granting access to configuration data to authorized users and applications
• Providing a UI for managing all configuration data stored in ConfigSeeder

The mentioned features are only an extract of all features we provide. Please also have a look at our Features page for an overview of all features.

ConfigSeeder Clients

While ConfigSeeder Management is responsible for storing configuration data, the ConfigSeeder Clients make it easy to access this configuration data. You only have to include these clients (libraries) in your application and get access to the data stored in ConfigSeeder.

We provide these clients for the following programming languages. Please contact us if you need to integrate ConfigSeeder with another programming language.

• Java (multiple variants)
• GoLang

Have a look at the description of the ConfigSeeder® client libraries for more details or look at our download page.

ConfigSeeder Value Provider

With the ConfigSeeder Value Provider, you can achieve high availability in your ConfigSeeder installation. While there should only be one running instance available of ConfigSeeder Management, there is no such limitation for the Value Provider.

• You need to integrate your applications tightly with ConfigSeeder and need high availability in accessing configuration data? Then install two or more Value Providers and put a load balancer in front of them.
• Do you need to access configuration data from multiple Kubernetes clusters? In this case, you should probably install two or more Value Providers to each of the clusters.

Kubernetes Connector

With the Kubernetes Connector, you can provision configuration data directly to a Kubernetes cluster. Define Secret- and ConfigMap Assemblies in ConfigSeeder Management and let the Kubernetes Connector manage them. Supported Kubernetes Objects are:

• Secrets containing an API Key (which grants access to ConfigSeeder)
• ConfigMaps containing key/value pairs
• ConfigMaps containing files created with a templating mechanism
• Secrets containing key/value pairs
• Secrets containing a Keystore or Truststore based on private keys and certificates stored in ConfigSeeder

See our blog article Using Kubernetes Connector for more details.

OS Connector

With the OS Connector, you can provision configuration data to file systems. Using File-Assemblies you can define different types of files in ConfigSeeder Management and let the OS Connector manage them. Supported are files with

• static content
• binary content
• templated content
• generated content in the formats properties, yaml and json

In addition, you can let the OS Connector create Keystores and Truststores out of private keys and certificates stored in ConfigSeeder.

The OS Connector comes in two variants, one for Linux (linux connector) and one Windows (windows connector). In addition, we ship the linux connector packed into a docker container.

Ansible Plugin

Not only applications require configuration data, but this is also true when you set up your infrastructure using a tool like Ansible.

With our Ansible ConfigSeeder Lookup Plugin you are able to use configuration data stored in ConfigSeeder in your Ansible Playbooks.