Skip to content

Latest commit

 

History

History
50 lines (36 loc) · 2.31 KB

README.md

File metadata and controls

50 lines (36 loc) · 2.31 KB
Raw

kubernetes provider

Provider Maturity: alpha

Basic implementation is in place, simple tests for HA, Scale Up and Scale Down have been performed. Backups are supported only via the file provider for now and a simple helm chart is provided for easy installation (NOT production ready).

The current implementation of the kubernetes provider is also determined not suitable for self hosted etcd installations backing kubernetes clusters like: https://coreos.com/tectonic/docs/latest/admin/self-hosted-etcd.html Please consider other solutions when self hosting etcd clusters on kubernetes.

Overview

The kubernetes(sts) provider is an opinionated framework for running the etcd-cloud-operator in any given Kubernetes cluster (version >= 1.10).

The provider assumes it is running inside a k8s cluster (will error out if run outside) and within a statefulset (will error out if run in a Kubernetes deployment for example).

It supports the exact same configuration options as the AWS provider (see: example).

This project also provides an accompanying helm chart to make it easy to deploy into your cluster. The helm chart can be deployed via all the regular methods:

  • Tiller installed within cluster (see helm docs)
  • Tiller running locally (see tillerless helm docs)
  • Or simply render the manifests using helm template and kubectl apply (see helm template docs)

If you already have tiller installed in your cluster, you can get up and running by simply:

git clone https://github.com/Quentin-M/etcd-cloud-operator.git
cd chart
helm install etcd-cloud-operator

This will install a basic 3 replica etcd cluster without persistent storage or client TLS. You can customize these settings using the variables available in the values file. These variables directly map to various configuration options for the operator.

TODO List:

  • Add persistent volume support in helm chart
  • Add security context in helm chart
  • Add E2E Tests for Kubernetes
  • Support S3 Snapshot provider (for non AWS deployments)
  • Make helm chart available via official helm repository
  • Provide a CRD driven K8s controller/operator(?)