SIG etcd Charter

SIG etcd Charter

This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance.

Scope

Owns the etcd project and how it is used by Kubernetes.

In scope

Code, Binaries and Services

Cross-cutting and Externally Facing Processes

  • Specifying, testing and improving the implicit Kubernetes-ETCD Contract, which includes storage requirements, write and delete requirements, read requirements and watch requirements.
  • Release process of etcd and other binaries belonging to etcd-io organization

Out of scope

  • Structure of data stored in etcd by Kubernetes components is owned by SIG API Machinery

Roles and Organization Management

This SIG follows the Roles and Organization Management outlined in sig-governance and opts-in to updates and modifications to sig-governance.

Additional responsibilities of Tech Leads

Deviations from sig-governance

  • SIG etcd’s participation in the Kubernetes release cycle is limited by etcd having a different schedule for its releases.
  • SIG etcd communication utilizes pre-existing forums for communication:
  • SIG etcd contributing instructions (CONTRIBUTING.md) be defined in etcd project.
  • For SIG leadership changes, we continue to follow the common Leadership Changes guidelines. SIG etcd also agrees to conduct open and transparent discussions among the current SIG leads through the following channels before sending to the SIG and kubernetes-dev mailing list,
    • The bi-weekly sig-etcd meetings
    • The etcd-maintainers@googlegroups.com mailing list
    • Slack group threads involving sig-etcd leads and etcd OWNERS.

Deviations from kubernetes-repositories

  • SIG etcd repositories live in github.com/etcd-io
  • SIG etcd repositories should (but not must) adopt merge bot, Kubernetes PR commands/bot.
  • SIG etcd repositories will follow rules for donated repositories.

Subproject Creation

By SIG Technical Leads

View Charter