Page MenuHomePhabricator

Decide if we want to stick with etcd datastore
Closed, ResolvedPublic

Description

Calico stores the data about the operational and configuration state of your cluster in a central datastore. If the datastore is unavailable your Calico network continues operating, but cannot be updated (no new pods can be networked, no policy changes can be applied, etc.).

Calico has two datastore drivers you can choose from

  • etcd - for direct connection to an etcd cluster
  • Kubernetes - for connection to a Kubernetes API server

...continue reading

We are currently using etcd datastore, but that was the only available datastore in the past. So we might want to revisit the "decision" as we now have the chance to do so easily.

Event Timeline

Decide decide if we are going to be staying with direct access to etcd (version 3?) or try and switch to the kubernetes APIs

The big issues we currently have with the etcd backed datastore is that the information in there is not tracked anyway. It is backed up but fully unsearchable. So we definitely want to at least test using the API.

akosiaris claimed this task.

I 'll mark this as resolved. We have gone with the Kubernetes datastore and the configuration for it is under admin_ng helmfile.d subdirectory of operations/deployments-charts repo