Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

Latest commit

 

History

History
34 lines (23 loc) · 2.84 KB

README.md

File metadata and controls

34 lines (23 loc) · 2.84 KB

MapStore

Test Status GoDoc Go Report Card

Overview

MapStore is a simple API built on top of Kubernetes ConfigMaps that allows you to programmatically read, write and delete key value pairs. This package was created as a solution to store small amounts of data without needing a persistent volume or standalone database. Because this package is backed by a ConfigMap, we must remember that potentially every interaction will send API requests to the Kubernetes API server.

To get started, check out the examples page.

Caveats

Kubernetes can not guarantee exclusive access to a ConfigMap, so we need to be aware of some edge cases. The ideal usage of MapStore is to have a single process accessing the data to ensure no inconsistences. Using a leader election package to protect access is recommended.

Internal caching

MapStore has the ability to hold the data of the ConfigMap in memory for quick lookups and reducing unnecessary requests to the Kubernetes API. This should only be enabled when you can guarantee no other app or process is accessing the same ConfigMap.

cacheConfigMapInternally := true
mapStore, err := mapstore.New("my-test-cm", cacheConfigMapInternally)

Size limitations

Please be aware that ConfigMaps are limited in size. This package has no protective measures in place to ensure you are below the limit.

A ConfigMap is not designed to hold large chunks of data. The data stored in a ConfigMap cannot exceed 1 MiB. If you need to store settings that are larger than this limit, you may want to consider mounting a volume or use a separate database or file service.

Kubernetes ConfigMap documentation

Environment variables

There are a few environment variables that you can apply to your workload that will effect MapStore:

MAPSTORE_CLUSTER_CONFIG_PATH can be set if you are using this package outside of your cluster, but still want to interact with a ConfigMap on the cluster. You can define the path to your cluster config file and it will be used by MapStore when connecting to the cluster. This is also a handy variable when testing locally. By default this value is empty and MapStore uses the InClusterConfig for it's connection.

NAMESPACE is the namespace name that MapStore will use. If not set, MapStore will attempt to pull the current namespace from /var/run/secrets/kubernetes.io/serviceaccount/namespace.