etcd operator working group

[ahrtr]

Initial PR to create wg-etcd-operator.

/committee steering

Adding stakeholder SIGs

/sig etcd
/sig cluster-lifecycle

cc @jmhbnz @jberkus @serathius @wenjiaswe @fabriziopandini @hakman @neolit123 @justinsb @vincepri

[ahrtr]

We need to finalize:

• liaison
• day/time for the regular meeting
• zoom link for the meeting
• a google doc (archive_url)
• slack channel
• mailing list url

[neolit123]

added some suggestions.

suggested to replace & with 'and' for more format language.

[serathius]

LGTM, awesome to see renewed interest into etcd-operator. For me this falls into making "etcd simple to operate" as proposed by the SIG-etcd vision making it a worthy investment.

[ahrtr]

/hold

I am going to send an email "WG-Creation-Request: WG etcd-operator" to [email protected] in the following 1~2 weeks.

[jmhbnz]

Overall this looks good, thanks for drafting @ahrtr. A few thoughts below.

[neolit123]

@pacoxu

It would be great if they can at least response to our survey in https://forms.gle/5gBpzaxYtuQPWdBo9.

do you see this as a blocker for the WG etcd operator creation?

[neolit123]

steering committee met on July 3rd but the creation of this WG was not on the agenda.
in terms of the punch card here:
https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md#prerequisites-for-a-wg

we are all set with the exception of:

• steering majority / voting on this ticket
• sending PR for sigs.yaml in k/community EDIT: nvm, this PR does that.
• sending email about the sigs.yaml change EDIT: we can just forward the below email

email was already sent to k-dev:
https://groups.google.com/a/kubernetes.io/g/dev/c/L1TgHxIkW_o

[neolit123]

/hold

[kvaps]

Hey I just wanted to inform that we have weekly comunity meetings for developing aenix-io/etcd-operator, we'll have one of these tomorrow:

When: every Tuesday at 16:00 CET
Where: Google meet
Link to join in:
https://meet.google.com/pib-tpfe-kuv

Minutes:
https://docs.google.com/document/d/1coiWlHOVfPAIyKqtfpYLhq9eeRPHCuuMxmNmVfo9-sA/edit

Everybody is free to join

[soltysh]

I learnt many projects are using etcd operators for performance issues. A simple solution is using a seperate etcd.

* kyverno has a new project for report server to save reports in a seperate etcd： https://github.com/kyverno/reports-server @realshuting

* Cilium has a solution of using a seperate etcd for all CRDs:  @aanm  https://github.com/cilium/cilium-etcd-operator is archived.

* other scanerios like Events and more. @kvaps has a longer list in [[epic] Move project to Kubernetes-SIGs aenix-io/etcd-operator#73](https://github.com/aenix-io/etcd-operator/issues/73)

Those projects' maintainers and users are potential etcd operator contributors and users.

I believe this point:

Bootstrap a project "etcd-operator" owned by SIG etcd which resides in the etcd-io or kubernetes-sigs Github orgs.
  - Review existing etcd operators to see if any could be forked or referenced to advance the project.

can be considered as covering Paco's comment. I don't think we want to explicitly mention these projects in the charter.

[soltysh]

Some minor nits, but mostly looks good, I'll make sure to get a final vote on this topic this week from steering.

[soltysh]

/lgtm
from steering
/hold
for other members to chime in

[BenTheElder]

/lgtm
/approve
[steering]

[palnabarun]

/lgtm
(from steering)

[pacoxu]

/lgtm
/approve
（steering）

@pacoxu It would be great if they can at least response to our survey in https://forms.gle/5gBpzaxYtuQPWdBo9.

do you see this as a blocker for the WG etcd operator creation?

just want to make more cloud native contributors/maintainers/users know this new wg and participate

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, BenTheElder, kvaps, pacoxu, palnabarun, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BenTheElder,pacoxu,palnabarun,soltysh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kvaps]

At our etcd-operator We usually have weekly community meetings every Tuesday at 16:00-17:00 CET, it is 7:00-8:00 am PT, so I would like to suggest the same time if it will be convenient to you.

Suggested change

|[etcd Operator](wg-etcd-operator/README.md)|[etcd-operator](https://github.com/kubernetes/kubernetes/labels/wg%2Fetcd-operator)|* Cluster Lifecycle<br>* etcd<br>|* [Benjamin Wang](https://github.com/ahrtr), VMware<br>* [Ciprian Hacman](https://github.com/hakman), Microsoft<br>* [Josh Berkus](https://github.com/jberkus), Red Hat<br>* [James Blair](https://github.com/jmhbnz), Red Hat<br>* [Justin Santa Barbara](https://github.com/justinsb), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-etcd-operator)<br>* [Mailing List](https://groups.google.com/u/1/g/etcd-dev)|* Regular WG Meeting: [TBDs at TBD PT (Pacific Time) (bi-weekly)](https://zoom.us/my/cncfetcdproject)<br>

|[etcd Operator](wg-etcd-operator/README.md)|[etcd-operator](https://github.com/kubernetes/kubernetes/labels/wg%2Fetcd-operator)|* Cluster Lifecycle<br>* etcd<br>|* [Benjamin Wang](https://github.com/ahrtr), VMware<br>* [Ciprian Hacman](https://github.com/hakman), Microsoft<br>* [Josh Berkus](https://github.com/jberkus), Red Hat<br>* [James Blair](https://github.com/jmhbnz), Red Hat<br>* [Justin Santa Barbara](https://github.com/justinsb), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-etcd-operator)<br>* [Mailing List](https://groups.google.com/u/1/g/etcd-dev)|* Regular WG Meeting: [Tuesdays at 7:00 PT (Pacific Time) (weekly)](https://zoom.us/my/cncfetcdproject)<br>

[ahrtr]

We will finalize the schedule later (after this PR gets merged).

[kvaps]

If it is applicable I'd like also to be in this list to represent our community.

Suggested change

	wg-etcd-operator-leads:
	- ahrtr
	- hakman
	- jberkus
	- jmhbnz
	- justinsb
	wg-etcd-operator-leads:
	- ahrtr
	- hakman
	- jberkus
	- jmhbnz
	- justinsb
	- kvaps

[jberkus]

Thanks for volunteering for the working group! This WG isn't a standing body to represent all etcd operators, though. It's a specific one-time effort to create an official Kubernetes-supported operator. As part of that, we'll be evaluating existing operators to determine if any of them can become the core of this new operator. That means that having the author of one such operator making that evaluation, as a WG chair, isn't a good idea.

You are very welcome to participate in the working group once it gets going, including meetings, issues, commentary, and roadmap.

[neolit123]

/hold cancel
thank you everyone for commenting.
(4 steering votes were added)