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

Istio Multicluster

Istio Multicluster

Istio Multicluster is a feature of Istio–the basis of Red Hat OpenShift Service Mesh–that allows for the extension of the service mesh across multiple Kubernetes or Red Hat OpenShift clusters. The primary goal of this feature is to enable control of services deployed across multiple clusters with a single control plane. The main requirement for Istio multicluster to work is that the pods in the mesh and the Istio control plane can talk to each other.

Read More
Moving from Kube2Iam to Kiam

Moving from Kube2Iam to Kiam

At Ibotta, we chose kube2iam to assign AWS IAM Roles to containers running in our Kubernetes cluster. Lately, we’ve run into some issues with it—specifically when running a job that scores all of our service repos. This spins up a number of pods in parallel and has often failed to correctly access roles.

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