Write operators for databases in Kubernetes with KubeDB

Write operators for databases in Kubernetes with KubeDB

  • January 21, 2019
Table of Contents

Write operators for databases in Kubernetes with KubeDB

Running production quality databases in Kubernetes can be quite a hassle. But KubeDB promises to solve all your problems. Let’s have a quick look at this framework.

You can count on KubeDB to solve your problems when running production quality databases in Kubernetes. KubeDB is a framework for writing operators for any database that support certain requirements. Namely: Create a database declaratively using CRD.

Take one-off backups or period backups to various cloud stores, eg,S3, GCS, etc. Restore from backup or clone any database. Native integration with Prometheus for monitoring viaCoreOS Prometheus Operator.

Apply deletion lock to avoid accidental deletion of database. Keep track of deleted databases, cleanup prior snapshots with a single command. Use cli to manage databases like kubectl for Kubernetes.

Source: jaxenter.com

Share :
comments powered by Disqus

Related Posts

Kubernetes Failure Stories

Kubernetes Failure Stories

I started to compile a list of public failure/horror stories related to Kubernetes. It should make it easier for people tasked with operations to find outage reports to learn from. Since we started with Kubernetes at Zalando in 2016, we collected many internal postmortems.

Read More
Envoy Proxy at Reddit

Envoy Proxy at Reddit

Reddit’s engineering team and product complexity has seen significant growth over the last three years. Facilitating that growth has taken a lot of behind-the-scenes evolution of Reddit’s backend infrastructure. One major component has been adopting a service-oriented architecture, and a significant facet of that has been evolving service-to-service discovery and communication.

Read More
Deployment strategies for the Jaeger Agent

Deployment strategies for the Jaeger Agent

If you’ve been following the evolution of the Kubernetes templates for Jaeger, you might have noticed an important change recently: the Jaeger Agent is not being deployed as a DaemonSet anymore. Instead, instructions are now being provided on how to deploy it as a “Sidecar”. The Agent component was developed to act as a “buffer” between the tracer and the collector.

Read More