kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Rebase

This commit is contained in:
Thomas Stromberg 2019-04-09 08:03:30 -07:00
parent 99250d7472 98185d86c1
commit fe38881b69
33 changed files with 616 additions and 381 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
OWNERS_ALIASES
View File

@ -30,10 +30,6 @@ aliases:
- dstrebel
- khenidak
- feiskyer
sig-big-data-leads:
- foxish
- erikerlandson
- liyinan926
sig-cli-leads:
- soltysh
- seans3
@ -44,7 +40,7 @@ aliases:
- hogepodge
- jagosan
sig-cluster-lifecycle-leads:
- roberthbailey
- justinsb
- luxas
- timothysc
sig-contributor-experience-leads:
@ -53,7 +49,7 @@ aliases:
- cblecker
- nikhita
sig-docs-leads:
- chenopis
- jaredbhatti
- zacharysarah
- bradamant3
sig-gcp-leads:
@ -67,7 +63,7 @@ aliases:
- brancz
sig-multicluster-leads:
- csbell
- quinton-hoole-2
- quinton-hoole
sig-network-leads:
- thockin
- dcbw
@ -133,7 +129,7 @@ aliases:
wg-lts-leads:
- tpepper
- imkin
- quinton-hoole-2
- quinton-hoole
- youngnick
wg-machine-learning-leads:
- vishh
@ -157,6 +153,10 @@ aliases:
- joelsmith
- cji
- jaybeale
ug-big-data-leads:
- foxish
- erikerlandson
- liyinan926
committee-code-of-conduct:
- jdumars
- parispittman
@ -165,14 +165,13 @@ aliases:
- bradamant3
committee-product-security:
- philips
- jessfraz
- cjcullen
- tallclair
- liggitt
- joelsmith
committee-steering:
- bgrant0607
- brendanburns
- brendandburns
- derekwaynecarr
- dims
- jbeda

1
committee-product-security/README.md
View File

@ -14,7 +14,6 @@ The Kubernetes Product Security Committee is the body that is responsible for re
## Members
* Brandon Philips (**[@philips](https://github.com/philips)**), Red Hat
* Jess Frazelle (**[@jessfraz](https://github.com/jessfraz)**)
* CJ Cullen (**[@cjcullen](https://github.com/cjcullen)**), Google
* Tim Allclair (**[@tallclair](https://github.com/tallclair)**), Google
* Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**), Google

2
committee-steering/README.md
View File

@ -19,7 +19,7 @@ The [charter](https://git.k8s.io/steering/charter.md) defines the scope and gove
## Members
* Brian Grant (**[@bgrant0607](https://github.com/bgrant0607)**), Google
* Brendan Burns (**[@brendanburns](https://github.com/brendanburns)**), Microsoft
* Brendan Burns (**[@brendandburns](https://github.com/brendandburns)**), Microsoft
* Derek Carr (**[@derekwaynecarr](https://github.com/derekwaynecarr)**), Red Hat
* Davanum Srinivas (**[@dims](https://github.com/dims)**), Huawei
* Joe Beda (**[@jbeda](https://github.com/jbeda)**), VMware

2
committee-steering/governance/sig-governance.md
View File

@ -171,7 +171,7 @@ Issues impacting multiple subprojects in the SIG should be resolved by either:
[SIG PM]: https://github.com/kubernetes/community/tree/master/sig-pm
[k/enhancements]: https://github.com/kubernetes/enhancements
[forums provided]:
[forums provided]: /communication/README.md
[lazy-consensus]: http://en.osswiki.info/concepts/lazy_consensus
[super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote

126
communication/calendar-guidelines.md Normal file
View File

@ -0,0 +1,126 @@
# Calendar Guidelines
Project meetings are a life line of the Kubernetes project. Consistent
calendaring is a challenge with many different clients, corporate policies,
time zones and various iterations of Daylight Savings Time. This guide should
help you navigate some of the common pitfalls and provide some tips & best
practices.
Please feel free to PR in your favorite tips and tricks that may help others.
- [Establishing a New Meeting](#establishing-a-new-meeting)
- [Testing Permissions](#testing-permissions)
- [Transferring Ownership](#transferring-ownership)
- [Tips](#tips)
- [Viewing Kubernetes Project Calendars](#viewing-kubernetes-project-calendars)
- [Adding Events to Your own Calendar](#adding-events-to-your-own-calendar)
- [Troubleshooting](#troubleshooting)
- [Permissions Impacted After Changing Positions or Role](#permissions-impacted-after-changing-positions-or-role)
## Establishing a New Meeting
_"I'm a chair for a SIG or WG and need to set up a meeting."_
This procedure will create a calendar that allows for you and all your SIG/WG
Chairs or Tech Leads to edit and manage the meetings.
**NOTE:** As of March 2019, this is the current best practice. However with the
addition of [gsuite], this practice may change soon.
1. Use a poll service such as [doodle] that will help you get a good pulse on
your community and when they can meet.
2. Create a [new shared calendar] titled "[SIG|WG] Foo Shared Calendar" from
a gmail/google account that will not have problems sharing or posting
information publicly. This may mean using a personal gmail account if your
corporate policies restrict sharing. See [Testing Permissions] to validate
you can share your calendar.
- Creating a shared calendar is essential. If you change jobs, email
addresses, or take a break from the project it allows for a smooth transfer
of ownership.
3. [Configure access permissions and sharing:]
- Make all event details publicly accessible.
- Share it with full rights ("make changes and manage sharing”) to your SIG/WG
lead mailing list and community@kubernetes.io.
- Let your other chairs and leads know they can accidentally delete a calendar
while trying to delete it from theirs.
- Share with view permissions only (“see all event details”) to your SIG/WG
mailing list.
4. Once you have a time cadence settled from your members, create a calendar
invite with the shared calendar as the owner. Configure it with the
following settings:
- Name it “[SIG|WG] Foo [Time Cadence ex: Biweekly] Meetings”.
- Set sharing to public. **NOTE:** most gmail accounts will have a "default
visibility" setting enabled. Default visibility is usually "private" and
will need to be set to "public".
- In the calendar invite body - include your meeting notes, zoom information,
and any other pertinent information that you want your group to know.
- Invite your SIG/WG mailing list and the Kubernetes Community Public
Calendar address: `cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com`
### Testing Permissions
Make sure your work account doesn't have restrictions for public viewing of
calendar invites you create. If you are unsure, test this with other
contributors before sending it to mailing lists. This is applicable for both the
calendar entry itself and the shared calendar if you are the chair creating it.
## Transferring Ownership
If a chair is offboarding, ensure that shared calendar permissions are
configured. Once the calendar has been migrated, send out a new invite to ensure
there are no possible ghost-entries in member's calendars.
## Tips
### Viewing Kubernetes Project Calendars
_"I'm a contributor and want to see one of/all of the SIG calendar(s)."_
Public Kubernetes Events can be seen on the [Public Community Calendar].
All of the SIGs and WGs have meeting agendas with detailed information at the
top. You can get this information from the [SIG/WG list]. Join their mailing
list for the most up to date calendar invites. Chairs will always invite the
entire mailing list to their events.
### Adding Events to Your own Calendar
Don't copy calendars if you can help it. Copying the calendar onto your calendar
will prevent you from getting updates like a canceled meeting. Join the main
[contributor mailing list] and any [SIG/WG list] that is of interest.
Accept the invite from the sender and you'll have the updates.
## Troubleshooting
### Permissions Impacted After Changing Positions or Role
_"I'm a chair and the person that created the meeting is either no longer with
the project or no longer at an employer that holds the invite"_
If the calendar was created as a shared calendar with edit rights granted to
other chairs and leads they should be able to edit the invite and migrate
ownership without issue. If you do not have permissions, check first by sending
an email to community@kubernetes.io. Permissions may have been granted that team
and they will be able to facilitate the change in ownership.
If there is no shared calendar and still one owner, ask the person to transfer
it to a shared calendar or you'll need to create a new one. In these cases it
often best to just create a new one to avoid any possible issues with the
previous calendar. It doesn't hurt to recreate a meeting invite every few months
to refresh invites sent to the group.
[gsuite]: https://github.com/kubernetes/community/issues/3362
[doodle]: https://doodle.com
[testing permissions]: #testing-permissions
[new shared calendar]: https://support.google.com/calendar/answer/37095?hl=en
[configure access permissions and sharing:]: https://support.google.com/calendar/answer/37082?hl=en
[SIG/WG list]: /sig-list.md
[Public Community Calendar]: https://calendar.google.com/calendar/embed?src=cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com&ctz=America%2FLos_Angeles
[contributor mailing list]: https://groups.google.com/forum/#!forum/kubernetes-dev

2
communication/moderators.md
View File

@ -163,7 +163,7 @@ Moderators seats: 10
| Jaice Singer DuMars | @jdumars | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) |
| Paris Pittman | @paris | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) |
| Noah Kantrowitz | @coderanger | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) |
| Ihor Dvoretskyi | @ihor.dvoretskyi | EMEA | [EET - Easter European Time](https://time.is/EET) |
| Ihor Dvoretskyi | @ihor.dvoretskyi | EMEA | [EET - Eastern European Time](https://time.is/EET) |
| Yang Li | @idealhack | APAC | [CST - China Standard Time](https://time.is/China) |

35
contributors/design-proposals/scheduling/nodeaffinity.md
View File

@ -144,12 +144,36 @@ Hopefully this won't cause too much confusion.
## Examples
**TODO: fill in this section**
* Run this pod on a node with an Intel or AMD CPU
* Run this pod on a node in availability zone Z
Run a pod on a node with an Intel or AMD CPU and in availability zone Z:
```yaml
apiVersion: v1
kind: Pod
metadata:
name: pod-with-node-affinity
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/arch
operator: In
values:
- intel
- amd64
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 1
preference:
matchExpressions:
- key: failure-domain.kubernetes.io/zone
operator: In
values:
- Z
containers:
- name: pod-with-node-affinity
image: tomcat:8
```
## Backward compatibility
@ -240,3 +264,4 @@ The main related issue is [#341](https://github.com/kubernetes/kubernetes/issues
Issue [#367](https://github.com/kubernetes/kubernetes/issues/367) is also related.
Those issues reference other related issues.

45
contributors/design-proposals/storage/csi-migration.md
View File

@ -237,8 +237,7 @@ with the in-tree plugin, the VolumeAttachment object becomes orphaned.
### In-line Volumes
In-line controller calls are a special case because there is no PV. In this case
we will forward the in-tree volume source to CSI attach as-is and it will be
copied to a new field in the VolumeAttachment object
we will translate the volume source and copy it to the field
VolumeAttachment.Spec.Source.VolumeAttachmentSource.InlineVolumeSource. The
VolumeAttachment name must be made with the CSI Translated version of the
VolumeSource in order for it to be discoverable by Detach and WaitForAttach
@ -259,12 +258,12 @@ type VolumeAttachmentSource struct {
// +optional
PersistentVolumeName *string `json:"persistentVolumeName,omitempty" protobuf:"bytes,1,opt,name=persistentVolumeName"`
// Allows CSI migration code to copy an inline volume
// source from a pod to the VolumeAttachment to support shimming of
// in-tree inline volumes to a CSI backend.
// This field is alpha-level and is only honored by servers that enable the CSIMigration feature.
// Translated VolumeSource from a pod to a CSIPersistentVolumeSource
// to support shimming of in-tree inline volumes to a CSI backend.
// This field is alpha-level and is only honored by servers that
// enable the CSIMigration feature.
// +optional
InlineVolumeSource *v1.VolumeSource `json:"inlineVolumeSource,omitempty protobuf:"bytes,2,opt,name=inlineVolumeSource"`
InlineCSIVolumeSource *v1.CSIPersistentVolumeSource `json:"inlineCSIVolumeSource,omitempty" protobuf:"bytes,2,opt,name=inlineCSIVolumeSource"`
}
```
@ -292,12 +291,40 @@ existing Pods in the ADC.
TODO: Design
### Raw Block
In the OperationGenerator, `GenerateMapVolumeFunc`, `GenerateUnmapVolumeFunc` and
`GenerateUnmapDeviceFunc` are used to prepare and mount/umount block devices. At the
beginning of each API, we will check whether migration is enabled for the plugin. If
enabled, volume spec will be translated from the in-tree spec to out-of-tree spec using
CSI as the persistence volume source.
TODO: Design
Caveat: the original spec needs to be used when setting the state of `actualStateOfWorld`
for where is it used before the translation.
### Volume Reconstruction
TODO: Design
Volume Reconstruction is currently a routine in the reconciler that runs on the
nodes when a Kubelet restarts and loses its cached state (`desiredState` and
`actualState`). It is kicked off in `syncStates()` in
`pkg/kubeletvolumemanager/reconciler/reconciler.go` and attempts to reconstruct
a volume based on the mount path on the host machine.
When CSI Migration is turned on, when the reconstruction code is run and it
finds a CSI mounted volume we currently do not know whether it was mounted as a
native CSI volume or migrated from in-tree. To solve this issue we will save a
`migratedVolume` boolean in the `saveVolumeData` function when the `NewMounter`
is created during the `MountVolume` call for that particular volume in the
Operation generator.
When the Kubelet is restarted and we lose state the Kubelet will call
`reconstructVolume` we can `loadVolumeData` and determine whether that CSI
volume was migrated or not, as well as get the information about the original
plugin requested. With that information we should be able to call the
`ReconstructVolumeOperation` with the correct in-tree plugin to get the original
in-tree spec that we can then pass to the rest of volume reconstruction. The
rest of the volume reconstruction code will then use this in-tree spec passed to
the `desiredState`, `actualState`, and `operationGenerator` and the volume will
go through the standard volume pathways and go through the standard migrated
volume lifecycles described above in the "Pre-Provisioned Volumes" section.
### Volume Limit

97
contributors/devel/development.md
View File

@ -120,12 +120,6 @@ tools].
Kubernetes build system requires `rsync` command present in the development
platform.
### etcd
Kubernetes maintains state in [`etcd`][etcd-latest], a distributed key store.
Please [install it locally][etcd-install] to run local integration tests.
### Go
Kubernetes is written in [Go](http://golang.org). If you don't have a Go
@ -160,6 +154,97 @@ images.
This requires pushing the [e2e][e2e-image] and [test][test-image] images that are `FROM` the desired Go version.
- The cross tag `KUBE_BUILD_IMAGE_CROSS_TAG` in [build/common.sh].
### Quick Start
The following section is a quick start on how to build Kubernetes locally, for more detailed information you can see [kubernetes/build](https://git.k8s.io/kubernetes/build/README.md).
The best way to validate your current setup is to build a small part of Kubernetes. This way you can address issues without waiting for the full build to complete. To build a specific part of Kubernetes use the `WHAT` environment variable to let the build scripts know you want to build only a certain package/executable.
```sh
make WHAT=cmd/{$package_you_want}
```
*Note:* This applies to all top level folders under kubernetes/cmd.
So for the cli, you can run:
```sh
make WHAT=cmd/kubectl
```
If everything checks out you will have an executable in the `_output/bin` directory to play around with.
*Note:* If you are using `CDPATH`, you must either start it with a leading colon, or unset the variable. The make rules and scripts to build require the current directory to come first on the CD search path in order to properly navigate between directories.
```sh
cd $working_dir/kubernetes
make
```
To remove the limit on the number of errors the Go compiler reports (default
limit is 10 errors):
```sh
make GOGCFLAGS="-e"
```
To build with optimizations disabled (enables use of source debug tools):
```sh
make GOGCFLAGS="-N -l"
```
To build binaries for all platforms:
```sh
make cross
```
#### Install etcd
```sh
cd $working_dir/kubernetes
# Installs in ./third_party/etcd
hack/install-etcd.sh
# Add to PATH
echo export PATH="\$PATH:$working_dir/kubernetes/third_party/etcd" >> ~/.profile
```
#### Test
```sh
cd $working_dir/kubernetes
# Run all the presubmission verification. Then, run a specific update script (hack/update-*.sh)
# for each failed verification. For example:
# hack/update-gofmt.sh (to make sure all files are correctly formatted, usually needed when you add new files)
# hack/update-bazel.sh (to update bazel build related files, usually needed when you add or remove imports)
make verify
# Alternatively, run all update scripts to avoid fixing verification failures one by one.
make update
# Run every unit test
make test
# Run package tests verbosely
make test WHAT=./pkg/api/helper GOFLAGS=-v
# Run integration tests, requires etcd
# For more info, visit https://git.k8s.io/community/contributors/devel/sig-testing/testing.md#integration-tests
make test-integration
# Run e2e tests by building test binaries, turn up a test cluster, run all tests, and tear the cluster down
# Equivalent to: go run hack/e2e.go -- -v --build --up --test --down
# Note: running all e2e tests takes a LONG time! To run specific e2e tests, visit:
# ./e2e-tests.md#building-kubernetes-and-running-the-tests
make test-e2e
```
See the [testing guide](./sig-testing/testing.md) and [end-to-end tests](./sig-testing/e2e-tests.md)
for additional information and scenarios.
Run `make help` for additional information on these make targets.
#### Dependency management

2
contributors/devel/sig-api-machinery/generating-clientset.md
View File

@ -1,6 +1,6 @@
# Generation and release cycle of clientset
Client-gen is an automatic tool that generates [clientset](../design-proposals/api-machinery/client-package-structure.md#high-level-client-sets) based on API types. This doc introduces the use of client-gen, and the release cycle of the generated clientsets.
Client-gen is an automatic tool that generates [clientset](/contributors/design-proposals/api-machinery/client-package-structure.md#high-level-client-sets) based on API types. This doc introduces the use of client-gen, and the release cycle of the generated clientsets.
## Using client-gen

4
contributors/devel/sig-architecture/api-conventions.md
View File

@ -379,7 +379,7 @@ Some resources in the v1 API contain fields called **`phase`**, and associated
`message`, `reason`, and other status fields. The pattern of using `phase` is
deprecated. Newer API types should use conditions instead. Phase was
essentially a state-machine enumeration field, that contradicted [system-design
principles](../design-proposals/architecture/principles.md#control-logic) and
principles](../../design-proposals/architecture/principles.md#control-logic) and
hampered evolution, since [adding new enum values breaks backward
compatibility](api_changes.md). Rather than encouraging clients to infer
implicit properties from phases, we prefer to explicitly expose the individual
@ -404,7 +404,7 @@ only provided with reasonable effort, and is not guaranteed to not be lost.
Status information that may be large (especially proportional in size to
collections of other resources, such as lists of references to other objects --
see below) and/or rapidly changing, such as
[resource usage](../design-proposals/scheduling/resources.md#usage-data), should be put into separate
[resource usage](../../design-proposals/scheduling/resources.md#usage-data), should be put into separate
objects, with possibly a reference from the original object. This helps to
ensure that GETs and watch remain reasonably efficient for the majority of
clients, which may not need that data.

8
contributors/devel/sig-release/cherry-picks.md
View File

@ -40,9 +40,11 @@ branches.
* Milestones on cherry-pick PRs should be the milestone for the target
release branch (for example, milestone 1.11 for a cherry-pick onto
release-1.11).
* You can find the current release team members in the
[appropriate release folder](https://git.k8s.io/sig-release/releases) for the target release.
You may cc them with `<@githubusername>` on your cherry-pick PR.
* During code freeze, to get attention on a cherry-pick by the current
release team members see the [appropriate release folder](https://git.k8s.io/sig-release/releases)
for the target release's team contact information. You may cc them with
`<@githubusername>` on your cherry-pick PR.
* For prior branches, check the [patch release schedule](https://git.k8s.io/sig-release/releases/patch-releases.md), which includes contact information for the patch release team.
## Cherry-pick Review

93
contributors/guide/github-workflow.md
View File

@ -22,7 +22,7 @@ Define a local working directory:
# You must follow exactly this pattern,
# neither `$GOPATH/src/github.com/${your github profile name/`
# nor any other pattern will work.
working_dir=$GOPATH/src/k8s.io
export working_dir=$GOPATH/src/k8s.io
```
> If you already do Go development on github, the `k8s.io` directory
@ -31,7 +31,7 @@ working_dir=$GOPATH/src/k8s.io
Set `user` to match your github profile name:
```sh
user={your github profile name}
export user={your github profile name}
```
Both `$working_dir` and `$user` are mentioned in the figure above.
@ -74,95 +74,8 @@ git checkout -b myfeature
Then edit code on the `myfeature` branch.
#### Build
The following section is a quick start on how to build Kubernetes locally, for more detailed information you can see [kubernetes/build](https://git.k8s.io/kubernetes/build/README.md).
The best way to validate your current setup is to build a small part of Kubernetes. This way you can address issues without waiting for the full build to complete. To build a specific part of Kubernetes use the `WHAT` environment variable to let the build scripts know you want to build only a certain package/executable.
```sh
make WHAT=cmd/{$package_you_want}
```
*Note:* This applies to all top level folders under kubernetes/cmd.
So for the cli, you can run:
```sh
make WHAT=cmd/kubectl
```
If everything checks out you will have an executable in the `_output/bin` directory to play around with.
*Note:* If you are using `CDPATH`, you must either start it with a leading colon, or unset the variable. The make rules and scripts to build require the current directory to come first on the CD search path in order to properly navigate between directories.
```sh
cd $working_dir/kubernetes
make
```
To remove the limit on the number of errors the Go compiler reports (default
limit is 10 errors):
```sh
make GOGCFLAGS="-e"
```
To build with optimizations disabled (enables use of source debug tools):
```sh
make GOGCFLAGS="-N -l"
```
To build binaries for all platforms:
```sh
make cross
```
#### Install etcd
```sh
cd $working_dir/kubernetes
# Installs in ./third_party/etcd
hack/install-etcd.sh
# Add to PATH
echo export PATH="\$PATH:$working_dir/kubernetes/third_party/etcd" >> ~/.profile
```
#### Test
```sh
cd $working_dir/kubernetes
# Run all the presubmission verification. Then, run a specific update script (hack/update-*.sh)
# for each failed verification. For example:
# hack/update-gofmt.sh (to make sure all files are correctly formatted, usually needed when you add new files)
# hack/update-bazel.sh (to update bazel build related files, usually needed when you add or remove imports)
make verify
# Alternatively, run all update scripts to avoid fixing verification failures one by one.
make update
# Run every unit test
make test
# Run package tests verbosely
make test WHAT=./pkg/api/helper GOFLAGS=-v
# Run integration tests, requires etcd
# For more info, visit https://git.k8s.io/community/contributors/devel/sig-testing/testing.md#integration-tests
make test-integration
# Run e2e tests by building test binaries, turn up a test cluster, run all tests, and tear the cluster down
# Equivalent to: go run hack/e2e.go -- -v --build --up --test --down
# Note: running all e2e tests takes a LONG time! To run specific e2e tests, visit:
# https://git.k8s.io/community/contributors/devel/sig-testing/e2e-tests.md#building-kubernetes-and-running-the-tests
make test-e2e
```
See the [testing guide](/contributors/devel/sig-testing/testing.md) and [end-to-end tests](/contributors/devel/sig-testing/e2e-tests.md)
for additional information and scenarios.
Run `make help` for additional information on these make targets.
This workflow is process-specific; for quick start build instructions for [kubernetes/kubernetes](https://git.k8s.io/kubernetes) please [see here](/contributors/devel/development.md#building-kubernetes-on-a-local-osshell-environment).
### 4 Keep your branch in sync

6
events/2019/05-contributor-summit/README.md
View File

@ -13,8 +13,8 @@ In some sense, the summit is a real-life extension of the community meetings and
## Registration
- [Sign the CLA](/CLA.md) if you have not done so already
- Registration form will be available soon
- [Sign the CLA](/CLA.md) if you have not done so already.
- [Complete the Registration form.](https://events.linuxfoundation.org/events/contributor-summit-europe-2019/register/)
## When and Where
@ -53,7 +53,7 @@ Combined Intro (Big Room) - All Workshop Participants:
* Finding Your First Topic AKA Where Do I Fit In
* Automation and Pull Request Demo/Practice
* Setting Up Your Dev Environment Lab
* Setting Up Your Dev Environment Lab
* Install Golang (or straighten out gopaths)
* Install Docker
* Clone Kubernetes

37
events/2019/06-contributor-summit/README.md
View File

@ -1 +1,38 @@
# 2019 Kubernetes Contributor Summit Shanghai
## Essential Information
June 24th, 2019<br />
10am to 5pm<br />
Shanghai Expo Center
[Registration Page](https://www.lfasiallc.com/events/contributor-summit-shanghai-2019/)
## Description
This year's contributor summit in China will be full-day event for people who contribute to Kubernetes, or are interested in becoming contributors, whether through writing code, documentation, infrastructure, project management, or the many other places they can help. It will include three tracks:
* The New Contributor Workshop is for those looking to find out how to become Kubernetes contributors;
* The Current Contributor Day is for attendees who are already contributing to Kubernetes, and want to learn more or do hands-on work at the Summit;
* The Documentation Sprints are for community members who want to help with writing documentation or translating it.
## New Contributor Workshop
The New Contributor Workshop is a 5-hour long tutorial, with participatory exercises, that covers the basics of contributing to Kubernetes and being part of its community. It is not possible to attend only part of the workshop, and you are expected to stay for the whole day.
Attendees will be expected to bring a laptop, sign the Contributor License Agreement, and have a GitHub account. The workshop will be held in both Chinese and English, with live translation.
## Current Contributor Day
This day is for people who already contribute to Kubernetes and participate in its community and want a place to have working meetings, as well as contributors who have already taken the New Contributor Workshop and want to learn more in-depth contribution topics.
Sessions during this day will be arranged by the community, and as such a final schedule will be posted here in early June.
The Contributor Day will be held primarily in English, although one or two sessions may be in Chinese.
## Documentation Sprints
The Documentation Sprints are for community members who want to help the project by either writing original documentation, updating and improving our documentation, or by translating the existing documentation into Chinese and other languages.
Attendees must have some proficiency in written English, should bring laptops, and should sign the Kubernetes CLA.

6
governance.md
View File

@ -143,7 +143,7 @@ do not have clear deliverables or ownership of parts of the Kubernetes
code base. As such they are neither good fits for SIGs or Working Groups.
An example of such a topic might be continuous delivery to Kubernetes.
Though their central goal is not a a deliverable piece of work, as contributing
Though their central goal is not a deliverable piece of work, as contributing
members of the community user groups are expected to work with SIGs
to either identify friction or usability issues that need to be addressed,
or to provide or improve documentation in their area of expertise. However
@ -201,13 +201,13 @@ All contributors must sign the CNCF CLA, as described [here](CLA.md).
[positive experiences]: https://www.cncf.io/blog/2016/12/14/diversity-scholarship-series-one-software-engineers-unexpected-cloudnativecon-kubecon-experience
[sigs.yaml]: /sigs.yaml
[SIG Lifecycle]: /sig-wg-lifecycle
[SIG Lifecycle]: /sig-wg-lifecycle.md
[We have them!]: /values.md
[Kubernetes code of conduct]: /code-of-conduct.md
[design principles]: /contributors/design-proposals/architecture/principles.md
[scope]: https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/
[community membership]: /community-membership.md
[sig governance]: /committee-steering/sig-governance.md
[sig governance]: /committee-steering/governance/sig-governance.md
[owners]: /community-membership.md#subproject-owner
[sig charter process]: /committee-steering/governance/README.md
[short template]: /committee-steering/governance/sig-governance-template-short.md

6
sig-aws/README.md
View File

@ -48,6 +48,12 @@ The following subprojects are owned by sig-aws:
- **aws-ebs-csi-driver**
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/aws-ebs-csi-driver/master/OWNERS
- **aws-efs-csi-driver**
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/aws-efs-csi-driver/master/OWNERS
- **aws-fsx-csi-driver**
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/aws-fsx-csi-driver/master/OWNERS
## GitHub Teams

56
sig-big-data/README.md
View File

@ -1,56 +0,0 @@
<!---
This is an autogenerated file!
Please do not edit this file directly, but instead make changes to the
sigs.yaml file in the project root.
To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
--->
# Big Data Special Interest Group
Covers deploying and operating big data applications (Spark, Kafka, Hadoop, Flink, Storm, etc) on Kubernetes. We focus on integrations with big data applications and architecting the best ways to run them on Kubernetes.
## Meetings
* Regular SIG Meeting: [Wednesdays at 17:00 UTC](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=17:00&tz=UTC).
* [Meeting notes and Agenda](https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit).
* [Meeting recordings](https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit).
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Anirudh Ramanathan (**[@foxish](https://github.com/foxish)**), Rockset
* Erik Erlandson (**[@erikerlandson](https://github.com/erikerlandson)**), Red Hat
* Yinan Li (**[@liyinan926](https://github.com/liyinan926)**), Google
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-big-data)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-big-data)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fbig-data)
## GitHub Teams
The below teams can be mentioned on issues and PRs in order to get attention from the right people.
Note that the links to display team membership will only work if you are a member of the org.
| Team Name | Details | Description |
| --------- |:-------:| ----------- |
| @kubernetes/sig-big-data-api-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-api-reviews) | API Changes and Reviews |
| @kubernetes/sig-big-data-bugs | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-bugs) | Bug Triage and Troubleshooting |
| @kubernetes/sig-big-data-feature-requests | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-feature-requests) | Feature Requests |
| @kubernetes/sig-big-data-misc | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-misc) | General Discussion |
| @kubernetes/sig-big-data-pr-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-pr-reviews) | PR Reviews |
| @kubernetes/sig-big-data-proposals | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-proposals) | Design Proposals |
| @kubernetes/sig-big-data-test-failures | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-test-failures) | Test Failures and Triage |
<!-- BEGIN CUSTOM CONTENT -->
## Goals
* Design and architect ways to run big data applications effectively on Kubernetes
* Discuss ongoing implementation efforts
* Discuss resource sharing and multi-tenancy (in the context of big data applications)
* Suggest Kubernetes features where we see a need
## Non-goals
* Endorsing any particular tool/framework
<!-- END CUSTOM CONTENT -->

11
sig-cli/README.md
View File

@ -58,6 +58,17 @@ The following subprojects are owned by sig-cli:
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/cli-runtime/OWNERS
- https://raw.githubusercontent.com/kubernetes/sample-cli-plugin/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/sample-cli-plugin/OWNERS
- **krew**
- Description: Plugin manager for kubectl.
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/krew/master/OWNERS
- **krew-index**
- Description: Centralized plugin index for krew.
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/krew-index/master/OWNERS
- **cli-experimental**
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/cli-experimental/master/OWNERS
## GitHub Teams

136
sig-cloud-provider/CHARTER.md
View File

@ -1,100 +1,68 @@
# SIG Cloud Provider Charter
## Mission
The Cloud Provider SIG ensures that the Kubernetes ecosystem is evolving in a way that is neutral to all (public and private) cloud providers. It will be responsible for establishing standards and requirements that must be met by all providers to ensure optimal integration with Kubernetes.
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].
## Subprojects & Areas of Focus
## Scope
* Maintaining parts of the Kubernetes project that allows Kubernetes to integrate with the underlying provider. This includes but are not limited to:
* [cloud provider interface](https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/cloud.go)
* [cloud-controller-manager](https://github.com/kubernetes/kubernetes/tree/master/cmd/cloud-controller-manager)
* Deployment tooling which has historically resided under [cluster/](https://github.com/kubernetes/kubernetes/tree/release-1.11/cluster)
* Code ownership for all cloud providers that fall under the kubernetes organization and have opted to be subprojects of SIG Cloud Provider. Following the guidelines around subprojects we anticipate providers will have full autonomy to maintain their own repositories, however, official code ownership will still belong to SIG Cloud Provider.
* [cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure)
* [cloud-provider-gcp](https://github.com/kubernetes/cloud-provider-gcp)
* [cloud-provider-openstack](https://github.com/kubernetes/cloud-provider-openstack)
* [cloud-provider-vsphere](https://github.com/kubernetes/cloud-provider-vsphere)
* Standards for documentation that should be included by all providers.
* Defining processes/standards for E2E tests that should be reported by all providers
* Developing future functionality in Kubernetes to support use cases common to all providers while also allowing custom and pluggable implementations when required, some examples include but are not limited to:
* Extendable node status’ and machine states based on provider
* Extendable node address types based on provider
* See also [Cloud Controller Manager KEP](https://github.com/kubernetes/community/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md)
* The collection of user experience reports from Kubernetes operators running on provider subprojects; and the delivery of roadmap information to SIG PM
SIG Cloud Provider’s mission is to simplify, develop, and maintain cloud provider integrations as extensions, or add-ons, to Kubernetes clusters.
## Organizational Management
### In scope
* Six months after this charter is first ratified, it MUST be reviewed and re-approved by the SIG in order to evaluate the assumptions made in its initial drafting
* SIG meets bi-weekly on zoom with agenda in meeting notes.
* SHOULD be facilitated by chairs unless delegated to specific Members
* The SIG MUST make a best effort to provide leadership opportunities to individuals who represent different races, national origins, ethnicities, genders, abilities, sexual preferences, ages, backgrounds, levels of educational achievement, and socioeconomic statuses
#### Areas of Focus
## Subproject Creation
- Extension points between Kubernetes and any cloud provider
- APIs/interfaces for efficiently provisioning/de-provisioning cloud resources (nodes, routes, load balancers, etc)
- Configuration of cluster components to enable cloud provider integrations
- Testing and testing frameworks to ensure vendor neutrality across all cloud providers
Each Kubernetes provider will (eventually) be a subproject under SIG Cloud Provider. To add new sub projects (providers), SIG Cloud Provider will maintain an open list of requirements that must be satisfied.
The current requirements can be seen [here](https://github.com/kubernetes/community/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md#repository-requirements). Each provider subproject is entitled to create 1..N repositories related to cluster turn up or operation on their platform, subject to technical standards set by SIG Cloud Provider.
Creation of a repository SHOULD follow the KEP process to preserve the motivation for the repository and any additional instructions for how other SIGs (e.g SIG Documentation and SIG Release) should interact with the repository
#### Code, Binaries and Services
Subprojects that fall under SIG Cloud Provider may also be features in Kubernetes that is requested or needed by all, or at least a large majority of providers. The creation process for these subprojects will follow the usual KEP process.
- the [common interfaces](https://github.com/kubernetes/cloud-provider/blob/master/cloud.go) consumed by all cloud providers
- the [cloud-controller-manager](https://github.com/kubernetes/kubernetes/tree/master/cmd/cloud-controller-manager), which acts as the “out-of-tree” cloud provider component for clusters.
- core controllers (started by the cloud-controller-manager) that interact with cloud provider resources
- all [cloud provider repositories](https://github.com/kubernetes?utf8=%E2%9C%93&q=cloud-provider-&type=&language=) under the Kubernetes organization
- [e2e tests for cloud provider specific](https://github.com/kubernetes/kubernetes/tree/master/test/e2e/cloud) functionality
## Subproject Retirement
#### Cross-cutting and Externally Facing Processes
Subprojects representing Kubernetes providers may be retired given they do not satisfy requirements for more than 6 months. Final decisions for retirement should be supported by a majority of SIG members using [lazy consensus](http://en.osswiki.info/concepts/lazy_consensus). Once retired any code related to that provider will be archived into the kubernetes-retired organization.
- This SIG works with SIG Testing & SIG Release to ensure that cloud providers are actively testing & reporting test results to testgrid.
- This SIG works with SIG Docs to provide user-facing documentation on configuring Kubernetes clusters with cloud provider integration enabled.
- This SIG works with new cloud providers in the ecosystem that want to host their code in the Kubernetes organization and have an interest in contributing back.
- This SIG actively engages with SIGs owning other external components of Kubernetes (CNI, CSI, etc) to ensure a consistent integration story for users.
Subprojects representing Kubernetes features may be retired at any point given a lack of development or a lack of demand. Final decisions for retirement should be supported by a majority of SIG members, ideally from every provider. Once retired, any code related to that subproject will be archived into the kubernetes-retired organization.
### Out of scope
- This SIG does not act as a line of support for Kubernetes users running their clusters on any cloud provider, though many members of the SIG represent cloud providers and are actively engaged with users.
- This SIG does not address features/bugs pertaining to cloud providers outside the scope of Kubernetes integrations (e.g. when will instance type X be available on cloud provider Y?)
## Roles and Organization Management
This sig follows adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].
### Additional responsibilities of Chairs
- Selecting/prioritizing work to be done for a milestone
- Hosting the weekly SIG meeting, ensure that recordings are uploaded in a timely fashion.
- Ensuring that the breakout sessions the SIG hosts during the week have chairs.
- Organizing SIG sessions at KubeCon events (intro / deep dive sessions).
- Creating roadmaps for a given year or release, or reviewing and approving technical implementation plans (e.g. KEPs) in coordination with both SIG Cluster Lifecycle contributors and other SIGs.
### Deviations from [sig-governance]
- There should be no more than 1 chair from a single company. This ensures decisions are not being made in favor of a single provider/company.
- As SIG cloud provider contains a number of subprojects, the SIG has empowered subproject leads with a number of additional responsibilities, including but not limited to:
* Releases: The subproject owners are responsible for determining the subproject release cadence, producing releases, and communicating releases with SIG Release and any other relevant SIG.
* Backlog grooming: The subproject owners are responsible for ensuring that the issues for the subproject are correctly associated with milestones and that bugs are triaged in a timely manner.
PR timeliness: The subproject owners are responsible for ensuring that active pull requests for the subproject are addressed in a timely manner.
* Repository ownership: The subproject owners are given admin permissions to repositories under the subproject. For example, the owners of the Azure subproject are given admin access to the `k8s.io/cloud-provider-azure` repository.
## Technical Processes
Subprojects (providers) of the SIG MUST use the following processes unless explicitly following alternatives they have defined.
### Subproject Creation
* Proposals will be sent as [KEP](https://git.k8s.io/enhancements/keps/YYYYMMDD-kep-template.md) PRs, and published to the official group mailing list as an announcement
* Proposals, once submitted, SHOULD be placed on the next full meeting agenda
* Decisions within the scope of individual subprojects should be made by lazy consensus by subproject owners, with fallback to majority vote by subproject owners; if a decision can’t be made, it should be escalated to the SIG Chairs
* Issues impacting multiple subprojects in the SIG should be resolved by consensus of the owners of the involved subprojects; if a decision can’t be made, it should be escalated to the SIG Chairs
## Roles
The following roles are required for the SIG to function properly. In the event that any role is unfilled, the SIG will make a best effort to fill it. Any decisions reliant on a missing role will be postponed until the role is filled.
### Chairs
* 3 chairs are required
* Run operations and processes governing the SIG
* An initial set of chairs was established at the time the SIG was founded.
* Chairs MAY decide to step down at anytime and propose a replacement, who must be approved by all of the other chairs. This SHOULD be supported by a majority of SIG Members.
* Chairs MAY select additional chairs using lazy consensus amongst SIG Members.
* Chairs MUST remain active in the role and are automatically removed from the position if they are unresponsive for > 3 months and MAY be removed by consensus of the other Chairs and members if not proactively working with other Chairs to fulfill responsibilities.
* Chairs WILL be asked to step down if there is inappropriate behavior or code of conduct issues
* SIG Cloud Provider cannot have more than one chair from any one company.
### Subproject/Provider Owners
* There should be at least 1 representative per subproject/provider (though 3 is recommended to avoid deadlock) as specified in the OWNERS file of each cloud provider repository.
* MUST be an escalation point for technical discussions and decisions in the subproject/provider
* MUST set milestone priorities or delegate this responsibility
* MUST remain active in the role and are automatically removed from the position if they are unresponsive for > 3 months and MAY be removed by consensus of other subproject owners and Chairs if not proactively working with other Subproject Owners to fulfill responsibilities.
* MAY decide to step down at anytime and propose a replacement. This can be done by updating the OWNERS file for any subprojects.
* MAY select additional subproject owners by updating the OWNERs file.
* WILL be asked to step down if there is inappropriate behavior or code of conduct issues
### SIG Members
Approvers and reviewers in the OWNERS file of all subprojects under SIG Cloud Provider.
## Long Term Goals
The long term goal of SIG Cloud Provider is to promote a vendor neutral ecosystem for our community. Vendors wanting to support Kubernetes should feel equally empowered to do so
as any of today’s existing cloud providers; but more importantly ensuring a high quality user experience across providers. The SIG will act as a central group for developing
the Kubernetes project in a way that ensures all providers share common privileges and responsibilities. Below are some concrete goals on how SIG Cloud Provider plans to accomplish this.
### Consolidating Existing Cloud SIGs
SIG Cloud Provider will aim to eventually consolidate existing cloud provider SIGs and have each provider instead form a subproject under it. The subprojects would drive the development of
individual providers and work closely with SIG Cloud Provider to ensure compatibility with Kubernetes. With this model, code ownership for new and existing providers will belong to SIG Cloud Provider,
limiting SIG sprawl as more providers support Kubernetes. Existing SIGs representing cloud providers are highly encouraged to opt-in as sub-projects under SIG Cloud Provider but are not required to do.
As a SIG opts-in, it will operate to ensure a smooth transition, typically over the course of 3 release cycles.
### Supporting New Cloud Providers
One of the primary goals of SIG Cloud Provider is to become an entrypoint for new providers wishing to support Kubernetes on their platform and ensuring technical excellence from each of those providers.
SIG Cloud Provider will accomplish this by maintaining documentation around how new providers can get started and managing the set of requirements that must be met to onboard them. In addition to
onboarding new providers, the entire lifecycle of providers would also fall under the responsibility of SIG Cloud Provider, which may involve clean up work if a provider decides to no longer support Kubernetes.
Federation of Subprojects
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[sig-subprojects]: https://github.com/kubernetes/community/blob/master/sig-YOURSIG/README.md#subprojects
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md

6
sig-cluster-lifecycle/README.md
View File

@ -43,10 +43,14 @@ The Cluster Lifecycle SIG examines how we should change Kubernetes to make it ea
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Robert Bailey (**[@roberthbailey](https://github.com/roberthbailey)**), Google
* Justin Santa Barbara (**[@justinsb](https://github.com/justinsb)**), Google
* Lucas Käldström (**[@luxas](https://github.com/luxas)**), Luxas Labs (occasionally contracting for Weaveworks)
* Timothy St. Clair (**[@timothysc](https://github.com/timothysc)**), VMware
## Emeritus Leads
* Robert Bailey (**[@roberthbailey](https://github.com/roberthbailey)**), Google
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)

4
sig-creation-procedure.md
View File

@ -1,3 +1,3 @@
## SIG creation procedure
## Special Interest and Working Group creation procedure
Moved to [sig governance](/sig-governance.md#sig-creation-procedure)
Moved to [sig-wg-lifecycle](/sig-wg-lifecycle.md)

19
sig-docs/README.md
View File

@ -23,9 +23,13 @@ Covers documentation, doc processes, and doc publishing for Kubernetes.
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Andrew Chen (**[@chenopis](https://github.com/chenopis)**), Google
* Jared Bhatti (**[@jaredbhatti](https://github.com/jaredbhatti)**), Google
* Zach Corleissen (**[@zacharysarah](https://github.com/zacharysarah)**), Linux Foundation
* Jennifer Rondeau (**[@bradamant3](https://github.com/bradamant3)**), VMware
* Jennifer Rondeau (**[@bradamant3](https://github.com/bradamant3)**), Stripe
## Emeritus Leads
* Andrew Chen (**[@chenopis](https://github.com/chenopis)**), Google
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-docs)
@ -54,9 +58,14 @@ Note that the links to display team membership will only work if you are a membe
| --------- |:-------:| ----------- |
| @kubernetes/sig-docs-maintainers | [link](https://github.com/orgs/kubernetes/teams/sig-docs-maintainers) | Documentation maintainers |
| @kubernetes/sig-docs-pr-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-docs-pr-reviews) | Documentation PR reviews |
| @kubernetes/sig-docs-ko-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-ko-owners) | Korean localization |
| @kubernetes/sig-docs-ja-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-ja-owners) | Japanese localization |
| @kubernetes/sig-docs-zh-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-zh-owners) | Chinese localization |
| @kubernetes/sig-docs-en-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-en-owners) | English content (default) |
| @kubernetes/sig-docs-es-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-es-owners) | Spanish content |
| @kubernetes/sig-docs-de-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-de-owners) | German content |
| @kubernetes/sig-docs-fr-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-fr-owners) | French content |
| @kubernetes/sig-docs-it-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-it-owners) | Italian content |
| @kubernetes/sig-docs-ja-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-ja-owners) | Japanese content |
| @kubernetes/sig-docs-ko-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-ko-owners) | Korean content |
| @kubernetes/sig-docs-zh-owners | [link](https://github.com/orgs/kubernetes/teams/sig-docs-zh-owners) | Chinese content |
<!-- BEGIN CUSTOM CONTENT -->
## Goals

19
sig-list.md
View File

@ -29,16 +29,15 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[Autoscaling](sig-autoscaling/README.md)|autoscaling|* [Marcin Wielgus](https://github.com/mwielgus), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-autoscaling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-autoscaling)|* Regular SIG Meeting: [Mondays at 14:00 UTC (biweekly/triweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[AWS](sig-aws/README.md)|aws|* [Justin Santa Barbara](https://github.com/justinsb)<br>* [Kris Nova](https://github.com/kris-nova), VMware<br>* [Nishi Davidson](https://github.com/d-nishi), AWS<br>|* [Slack](https://kubernetes.slack.com/messages/sig-aws)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-aws)|* Regular SIG Meeting: [Fridays at 9:00 PT (Pacific Time) (biweekly 2019 start date: Jan. 11th)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Azure](sig-azure/README.md)|azure|* [Stephen Augustus](https://github.com/justaugustus), VMware<br>* [Dave Strebel](https://github.com/dstrebel), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/sig-azure)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-azure)|* Regular SIG Meeting: [Wednesdays at 16:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Big Data](sig-big-data/README.md)|big-data|* [Anirudh Ramanathan](https://github.com/foxish), Rockset<br>* [Erik Erlandson](https://github.com/erikerlandson), Red Hat<br>* [Yinan Li](https://github.com/liyinan926), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-big-data)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-big-data)|* Regular SIG Meeting: [Wednesdays at 17:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[CLI](sig-cli/README.md)|cli|* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>* [Sean Sullivan](https://github.com/seans3), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cli)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cli)|* Regular SIG Meeting: [Wednesdays at 09:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Cloud Provider](sig-cloud-provider/README.md)|cloud-provider|* [Andrew Sy Kim](https://github.com/andrewsykim), VMware<br>* [Chris Hoge](https://github.com/hogepodge), OpenStack Foundation<br>* [Jago Macleod](https://github.com/jagosan), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cloud-provider)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cloud-provider)|* Regular SIG Meeting: [Wednesdays at 1:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (cloud-provider-extraction-migration) Weekly Sync removing the in-tree cloud providers led by @cheftako and @mcrute: [Thursdays at 13:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1KLsGGzNXQbsPeELCeF_q-f0h0CEGSe20xiwvcR2NlYM/edit)<br>
|[Cluster Lifecycle](sig-cluster-lifecycle/README.md)|cluster-lifecycle|* [Robert Bailey](https://github.com/roberthbailey), Google<br>* [Lucas Käldström](https://github.com/luxas), Luxas Labs (occasionally contracting for Weaveworks)<br>* [Timothy St. Clair](https://github.com/timothysc), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)|* Regular SIG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* kubeadm Office Hours: [Wednesdays at 09:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API office hours: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API Provider Implementers' office hours (EMEA): [Wednesdays at 15:00 CEST (Central European Summer Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API Provider Implementers' office hours (US West Coast): [Tuesdays at 12:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API (AWS implementation) office hours: [Mondays at 10:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* kops Office Hours: [Fridays at 09:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Kubespray Office Hours: [Wednesdays at 08:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster Addons meeting: [Fridays at 10:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* minikube Office Hours: [Mondays at 10:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Cluster Lifecycle](sig-cluster-lifecycle/README.md)|cluster-lifecycle|* [Justin Santa Barbara](https://github.com/justinsb), Google<br>* [Lucas Käldström](https://github.com/luxas), Luxas Labs (occasionally contracting for Weaveworks)<br>* [Timothy St. Clair](https://github.com/timothysc), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)|* Regular SIG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* kubeadm Office Hours: [Wednesdays at 09:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API office hours: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API Provider Implementers' office hours (EMEA): [Wednesdays at 15:00 CEST (Central European Summer Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API Provider Implementers' office hours (US West Coast): [Tuesdays at 12:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster API (AWS implementation) office hours: [Mondays at 10:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* kops Office Hours: [Fridays at 09:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Kubespray Office Hours: [Wednesdays at 08:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Cluster Addons meeting: [Fridays at 10:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* minikube Office Hours: [Mondays at 10:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Contributor Experience](sig-contributor-experience/README.md)|contributor-experience|* [Elsie Phillips](https://github.com/Phillels), Red Hat<br>* [Paris Pittman](https://github.com/parispittman), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-contribex)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-contribex)|* Regular SIG Meeting: [Wednesdays at 9:30 PT (Pacific Time) (weekly - except fourth Wednesday every month)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* APAC SIG Meeting: [Wednesdays at 20:00 PT (Pacific Time) (monthly - fourth Wednesday every month)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (contributors-documentation) Non-Code Contributors Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1gdFWfkrapQclZ4-z4Lx2JwqKsJjXXUOVoLhBzZiZgSk/edit)<br>* (events) Contributor Summit strategy, content and planning: [Mondays at 9:00 PT (Pacific Time) (weekly)]()<br>
|[Docs](sig-docs/README.md)|docs|* [Andrew Chen](https://github.com/chenopis), Google<br>* [Zach Corleissen](https://github.com/zacharysarah), Linux Foundation<br>* [Jennifer Rondeau](https://github.com/bradamant3), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-docs)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)|* Regular SIG Meeting: [Tuesdays at 17:30 UTC (weekly - except fourth Tuesday every month)](https://docs.google.com/document/d/1zg6By77SGg90EVUrhDIhopjZlSDg2jCebU-Ks9cYx0w/edit)<br>* APAC SIG Meeting: [Wednesdays at 02:00 UTC (monthly - fourth Wednesday every month)](https://docs.google.com/document/d/1zg6By77SGg90EVUrhDIhopjZlSDg2jCebU-Ks9cYx0w/edit)<br>
|[Docs](sig-docs/README.md)|docs|* [Jared Bhatti](https://github.com/jaredbhatti), Google<br>* [Zach Corleissen](https://github.com/zacharysarah), Linux Foundation<br>* [Jennifer Rondeau](https://github.com/bradamant3), Stripe<br>|* [Slack](https://kubernetes.slack.com/messages/sig-docs)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)|* Regular SIG Meeting: [Tuesdays at 17:30 UTC (weekly - except fourth Tuesday every month)](https://docs.google.com/document/d/1zg6By77SGg90EVUrhDIhopjZlSDg2jCebU-Ks9cYx0w/edit)<br>* APAC SIG Meeting: [Wednesdays at 02:00 UTC (monthly - fourth Wednesday every month)](https://docs.google.com/document/d/1zg6By77SGg90EVUrhDIhopjZlSDg2jCebU-Ks9cYx0w/edit)<br>
|[GCP](sig-gcp/README.md)|gcp|* [Adam Worrall](https://github.com/abgworrall), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-gcp)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-gcp)|* Regular SIG Meeting: [Thursdays at 16:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[IBMCloud](sig-ibmcloud/README.md)|ibmcloud|* [Khalid Ahmed](https://github.com/khahmed), IBM<br>* [Richard Theis](https://github.com/rtheis), IBM<br>* [Sahdev Zala](https://github.com/spzala), IBM<br>|* [Slack](https://kubernetes.slack.com/messages/sig-ibmcloud)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-ibmcloud)|* Regular SIG Meeting: [Wednesdays at 14:00 EST (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Instrumentation](sig-instrumentation/README.md)|instrumentation|* [Piotr Szczesniak](https://github.com/piosz), Google<br>* [Frederic Branczyk](https://github.com/brancz), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-instrumentation)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-instrumentation)|* Regular SIG Meeting: [Thursdays at 17:30 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Multicluster](sig-multicluster/README.md)|multicluster|* [Christian Bell](https://github.com/csbell), Google<br>* [Quinton Hoole](https://github.com/quinton-hoole-2), Huawei<br>|* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-multicluster)|* Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Federation v2 Working Group: [Wednesdays at 7:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Multicluster](sig-multicluster/README.md)|multicluster|* [Christian Bell](https://github.com/csbell), Google<br>* [Quinton Hoole](https://github.com/quinton-hoole), Huawei<br>|* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-multicluster)|* Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Federation v2 Working Group: [Wednesdays at 7:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Network](sig-network/README.md)|network|* [Tim Hockin](https://github.com/thockin), Google<br>* [Dan Williams](https://github.com/dcbw), Red Hat<br>* [Casey Davenport](https://github.com/caseydavenport), Tigera<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Regular SIG Meeting: [Thursdays at 14:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Node](sig-node/README.md)|node|* [Dawn Chen](https://github.com/dchen1107), Google<br>* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-node)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-node)|* Regular SIG Meeting: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[OpenStack](sig-openstack/README.md)|openstack|* [Chris Hoge](https://github.com/hogepodge), OpenStack Foundation<br>* [Aditi Sharma](https://github.com/adisky), NEC Technologies India<br>* [Christoph Glaubitz](https://github.com/chrigl), iNNOVO Cloud<br>|* [Slack](https://kubernetes.slack.com/messages/sig-openstack)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-openstack)|* Regular SIG Meeting: [Wednesdays at 08:00 PT (Pacific Time) (biweekly starting Wednesday March 20, 2019)](https://docs.google.com/document/d/1bW3j4hFN4D8rv2LFv-DybB3gcE5ISAaOO_OpvDCgrGg/edit)<br>
@ -61,20 +60,26 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[Component Standard](wg-component-standard/README.md)|* Architecture<br>* API Machinery<br>* Cluster Lifecycle<br>|* [Lucas Käldström](https://github.com/luxas), Luxas Labs (occasionally contracting for Weaveworks)<br>* [Dr. Stefan Schimanski](https://github.com/sttts), Red Hat<br>* [Michael Taufen](https://github.com/mtaufen), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-component-standard)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-component-standard)|* Regular WG Meeting: [Tuesdays at 08:30 PT (Pacific Time) (weekly)](https://zoom.us/j/705540322)<br>
|[IoT Edge](wg-iot-edge/README.md)|* Multicluster<br>* Networking<br>|* [Cindy Xing](https://github.com/cindyxing), Huawei<br>* [Dejan Bosanac](https://github.com/dejanb), Red Hat<br>* [Preston Holmes](https://github.com/ptone), Google<br>* [Steve Wong](https://github.com/cantbewong), VMWare<br>|* [Slack](https://kubernetes.slack.com/messages/wg-iot-edge)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge)|* Regular WG Meeting: [Wednesdays at 17:00 UTC (every four weeks)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* APAC WG Meeting: [Wednesdays at 5:00 UTC (every four weeks)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[K8s Infra](wg-k8s-infra/README.md)|* Architecture<br>* Contributor Experience<br>* Release<br>* Testing<br>|* [Davanum Srinivas](https://github.com/dims), Huawei<br>* [Aaron Crickenberger](https://github.com/spiffxp), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-k8s-infra)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-k8s-infra)|* Regular WG Meeting: [Wednesdays at 8:30 PT (Pacific Time) (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[LTS](wg-lts/README.md)|* API Machinery<br>* CLI<br>* Node<br>|* [Tim Pepper](https://github.com/tpepper), VMware<br>* [Dhawal Yogesh Bhanusali](https://github.com/imkin), VMware<br>* [Quinton Hoole](https://github.com/quinton-hoole-2), Huawei<br>* [Nick Young](https://github.com/youngnick), Atlassian<br>|* [Slack](https://kubernetes.slack.com/messages/wg-lts)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-lts)|* Regular WG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[LTS](wg-lts/README.md)|* API Machinery<br>* CLI<br>* Node<br>|* [Tim Pepper](https://github.com/tpepper), VMware<br>* [Dhawal Yogesh Bhanusali](https://github.com/imkin), VMware<br>* [Quinton Hoole](https://github.com/quinton-hoole), Huawei<br>* [Nick Young](https://github.com/youngnick), Atlassian<br>|* [Slack](https://kubernetes.slack.com/messages/wg-lts)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-lts)|* Regular WG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Machine Learning](wg-machine-learning/README.md)||* [Vishnu Kannan](https://github.com/vishh), Google<br>* [Kenneth Owens](https://github.com/kow3ns), Google<br>* [Balaji Subramaniam](https://github.com/balajismaniam), Intel<br>* [Connor Doyle](https://github.com/ConnorDoyle), Intel<br>|* [Slack](https://kubernetes.slack.com/messages/wg-machine-learning)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-machine-learning)|* Regular WG Meeting: [Thursdays at 13:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Multitenancy](wg-multitenancy/README.md)||* [David Oppenheimer](https://github.com/davidopp), Google<br>* [Tasha Drew](https://github.com/tashimi), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/wg-multitenancy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy)|* Regular WG Meeting: [Tuesdays at 11:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Policy](wg-policy/README.md)||* [Howard Huang](https://github.com/hannibalhuang), Huawei<br>* [Torin Sandall](https://github.com/tsandall), Styra<br>* [Yisui Hu](https://github.com/easeway), Google<br>* [Erica von Buelow](https://github.com/ericavonb), Red Hat<br>* [Michael Elder](https://github.com/mdelder), IBM<br>|* [Slack](https://kubernetes.slack.com/messages/wg-policy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-policy)|* Regular WG Meeting: [Wednesdays at 16:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Resource Management](wg-resource-management/README.md)||* [Vishnu Kannan](https://github.com/vishh), Google<br>* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-resource-mgmt)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-resource-management)|* Regular WG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly (On demand))](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|[Security Audit](wg-security-audit/README.md)||* [Aaron Small](https://github.com/aasmall), Google<br>* [Joel Smith](https://github.com/joelsmith), Red Hat<br>* [Craig Ingram](https://github.com/cji), Salesforce<br>* [Jay Beale](https://github.com/jaybeale), InGuardians<br>|* [Slack](https://kubernetes.slack.com/messages/wg-security-audit)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-security-audit)|* Regular WG Meeting: [Mondays at 13:00 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1RbC4SBZBlKth7IjYv_NaEpnmLGwMJ0ElpUOmsG-bdRA/edit)<br>
### Master User Group List
| Name | Organizers | Contact | Meetings |
|------|------------|---------|----------|
|[Big Data](ug-big-data/README.md)|* [Anirudh Ramanathan](https://github.com/foxish), Rockset<br>* [Erik Erlandson](https://github.com/erikerlandson), Red Hat<br>* [Yinan Li](https://github.com/liyinan926), Google<br>|* [Slack](https://kubernetes.slack.com/messages/ug-big-data)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-ug-big-data)|* Regular User Group Meeting: [Wednesdays at 18:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
### Master Committee List
| Name | Label | Members | Contact |
|------|--------|---------|---------|
|[Code of Conduct](committee-code-of-conduct/README.md)|conduct|* [Jaice Singer Dumars](https://github.com/jdumars), Google<br>* [Paris Pittman](https://github.com/parispittman), Google<br>* [Carolyn Van Slyck](https://github.com/carolynvs), Microsoft<br>* [Eric Paris](https://github.com/eparis), Red Hat<br>* [Jennifer Rondeau](https://github.com/bradamant3), VMware<br>|* [Private Mailing List](conduct@kubernetes.io)
|[Product Security](committee-product-security/README.md)|product-security|* [Brandon Philips](https://github.com/philips), Red Hat<br>* [Jess Frazelle](https://github.com/jessfraz)<br>* [CJ Cullen](https://github.com/cjcullen), Google<br>* [Tim Allclair](https://github.com/tallclair), Google<br>* [Jordan Liggitt](https://github.com/liggitt), Google<br>* [Joel Smith](https://github.com/joelsmith), Red Hat<br>|* [Private Mailing List](security@kubernetes.io)
|[Steering](committee-steering/README.md)|steering|* [Brian Grant](https://github.com/bgrant0607), Google<br>* [Brendan Burns](https://github.com/brendanburns), Microsoft<br>* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>* [Davanum Srinivas](https://github.com/dims), Huawei<br>* [Joe Beda](https://github.com/jbeda), VMware<br>* [Michelle Noorali](https://github.com/michelleN), Microsoft<br>* [Brandon Philips](https://github.com/philips), Red Hat<br>* [Phillip Wittrock](https://github.com/pwittrock), Google<br>* [Sarah Novotny](https://github.com/sarahnovotny), Google<br>* [Clayton Coleman](https://github.com/smarterclayton), Red Hat<br>* [Aaron Crickenberger](https://github.com/spiffxp), Google<br>* [Timothy St. Clair](https://github.com/timothysc), VMware<br>|* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io)
|[Product Security](committee-product-security/README.md)|product-security|* [Brandon Philips](https://github.com/philips), Red Hat<br>* [CJ Cullen](https://github.com/cjcullen), Google<br>* [Tim Allclair](https://github.com/tallclair), Google<br>* [Jordan Liggitt](https://github.com/liggitt), Google<br>* [Joel Smith](https://github.com/joelsmith), Red Hat<br>|* [Private Mailing List](security@kubernetes.io)
|[Steering](committee-steering/README.md)|steering|* [Brian Grant](https://github.com/bgrant0607), Google<br>* [Brendan Burns](https://github.com/brendandburns), Microsoft<br>* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>* [Davanum Srinivas](https://github.com/dims), Huawei<br>* [Joe Beda](https://github.com/jbeda), VMware<br>* [Michelle Noorali](https://github.com/michelleN), Microsoft<br>* [Brandon Philips](https://github.com/philips), Red Hat<br>* [Phillip Wittrock](https://github.com/pwittrock), Google<br>* [Sarah Novotny](https://github.com/sarahnovotny), Google<br>* [Clayton Coleman](https://github.com/smarterclayton), Red Hat<br>* [Aaron Crickenberger](https://github.com/spiffxp), Google<br>* [Timothy St. Clair](https://github.com/timothysc), VMware<br>|* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io)
<!-- BEGIN CUSTOM CONTENT -->
<!-- END CUSTOM CONTENT -->

2
sig-multicluster/README.md
View File

@ -26,7 +26,7 @@ The [charter](charter.md) defines the scope and governance of the Multicluster S
The Chairs of the SIG run operations and processes governing the SIG.
* Christian Bell (**[@csbell](https://github.com/csbell)**), Google
* Quinton Hoole (**[@quinton-hoole-2](https://github.com/quinton-hoole-2)**), Huawei
* Quinton Hoole (**[@quinton-hoole](https://github.com/quinton-hoole)**), Huawei
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)

3
sig-node/README.md
View File

@ -30,6 +30,9 @@ The Chairs of the SIG run operations and processes governing the SIG.
## Subprojects
The following subprojects are owned by sig-node:
- **cri-api**
- Owners:
- https://raw.githubusercontent.com/kubernetes/cri-api/master/OWNERS
- **cri-o**
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/cri-o/master/OWNERS

2
sig-storage/README.md
View File

@ -103,7 +103,7 @@ We hold a public meeting every two weeks, on Thursdays at 9 AM (PT).
* Recordings of past meetings: https://www.youtube.com/playlist?list=PLb1_clREIGYVaqvKaUsVyXxjfcSQDBnmB
### Contributing
Interested in contributing to storage features in Kubernetes? [Please read our guide for new contributors](https://github.com/kubernetes/community/blob/master/sig-storage/CONTRIBUTING.md)
Interested in contributing to storage features in Kubernetes? [Please read our guide for new contributors](/sig-storage/contributing.md)
### Links
* Public Slack Channel: https://kubernetes.slack.com/messages/sig-storage/details/

40
sig-wg-lifecycle.md
View File

@ -1,4 +1,4 @@
# SUMMARY:
## SUMMARY:
This document covers everything you need to know about the creation and retirement (“lifecycle”) of a special interest or working group within the Kubernetes project. General project governance information can be found in the [steering committee repo].
Out of scope for this document: [subproject] creation.
@ -6,15 +6,15 @@ Out of scope for this document: [subproject] creation.
[Creation]
[Retirement]
# [Creation]
## Prerequisites for a SIG
## [Creation]
### Prerequisites for a SIG
- [ ] Read [sig-governance.md]
- [ ] Send an email to the Steering Committee <steering@kubernetes.io> to scope the SIG and get provisional approval.
- [ ] Look at the checklist below for processes and tips that you will need to do while this is going on. It's best to collect this information upfront so you have a smoother process to launch
- [ ] Follow the [SIG charter process] to propose and obtain approval for a charter
- [ ] Announce new SIG on kubernetes-dev@googlegroups.com
## Prerequisites for a WG
### Prerequisites for a WG
- [ ] Read [wg-governance.md]
- [ ] Send email to [kubernetes-dev@googlegroups.com] titled "WG-Creation-Request: WG Foo" with some of the questions answered from wg-goverance.md and wait for community discourse; ask for SIG sponsorship
- [ ] Do the first checklist item in the #GitHub section below and add a row to the WG section:
@ -23,7 +23,7 @@ Out of scope for this document: [subproject] creation.
- [ ] Place a `/hold` on it until the members that need to review have; a contributor experience member will do this for you if they don't see one already
- [ ] Send an email to the stakeholder SIG mailing lists and steering committee with the sigs.yaml pull request
## GitHub:
### GitHub:
- [ ] Submit a PR that will add rows to [sigs.yaml] using the [generator doc]; this will create README files and OWNERS_ALIASES files for your new directory in `kubernetes/community`
- You’ll need:
- SIG Name
@ -37,7 +37,7 @@ Out of scope for this document: [subproject] creation.
- [ ] Add SIG-related docs like charter.md, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory once the above PR is merged.
- [ ] File a [Kubernetes/Org] Issue for a label; read about our [GitHub management] services
## Communicate:
### Communicate:
Each one of these has a linked canonical source guideline from set up to moderation and your role and responsibilities for each. We are all responsible for enforcing our [code of conduct].
- [ ] Read [moderation.md] and understand your role in keeping our community safe
- [ ] Create your mailing lists - One for your members and another for your chairs/leads
@ -48,34 +48,27 @@ Each one of these has a linked canonical source guideline from set up to moderat
- [ ] Request a YouTube playlist link [youtube-guidelines.md]
- [ ] Request a zoom account [zoom-guidelines.md]
## Engage:
### Engage:
...as a chair/tech lead with other chairs/tech leads
- [ ] Subscribe to the kubernetes-sig-leads@googlegroups.com group
- [ ] Join the #chairs-and-techleads slack channel
...with the community as part of [sig-governance.md]
- [ ] Get on the schedule for [Thursday community updates]; info at the top of the agenda
- [ ] Schedule your weekly/biweekly/at least every 3 weeks update meetings [TODO - THIS MAY CHANGE ONCE WE EXPLORE GSUITE]
- Use a poll service like doodle.com that will help you get a good pulse on your community and when they can meet
- This calendar creation process will allow all of your leads to edit SIG/WG Meetings. This is important as we all change jobs, email addresses, and take breaks from the project. Shared calendars will also provide consistenacy with contributors looking for your subproject meetings, office hours, and anything else that the SIG/WGs contributors should know about.
- Create a shared calendar on your own account. [example with google calendars: https://support.google.com/calendar/answer/37095?hl=en] Note: If you are creating from a corporate account like Google, it will not be public. Do a test first and ask a friend that doesn't work at your company.
- Name it “SIG/WG Foo [Time Cadence] Meetings”
- Sharing / access settings: Make it public
- Share it with full rights ("make changes and manage sharing”) with: cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com (Why this weird address? This is a public calendar that will be used to populate calendars on various sites)
- Your SIG/WG lead email distro (see second bullet in Communicate)
- Share it with lowest level of shown details (“see all event details”):
- SIG/WG membership distro (example: kubernetes-sig-foo@)
- [ ] Create a shared calendar and schedule your weekly/biweekly/triweekly weeks [update meetings]
- This calendar creation process will allow all of your leads to edit SIG/WG Meetings. This is important as we all change jobs, email addresses, and take breaks from the project. Shared calendars will also provide consistency with contributors looking for your subproject meetings, office hours, and anything else that the SIG/WGs contributors should know about.
# [Retirement] (merging or disbandment)
## [Retirement]
(merging or disbandment)
Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may also merge with an existing SIG/WG if deemed appropriate, and would save project overhead in the long run. Working Groups in particular are more ephemeral than SIGs, so this process should be followed when the Working Group has accomplished it's mission.
## Prerequisites for SIG Retirement
### Prerequisites for SIG Retirement
- [ ] SIG’s retirement decision follows the decision making and communication processes as outlined in their charter
## Prerequisites for WG Retirement
### Prerequisites for WG Retirement
- [ ] Have completed the mission of the WG or have another reason as outlined in [wg-governance.md]
## Steps:
### Steps:
- [ ] Send an email to kubernetes-dev@googlegroups.com and community@kubernetes.io alerting the community of your intentions to disband or merge. [example]
- This kicks off the process for Contributor Experience’s community managers who will reach out and set an issue against `kubernetes/community` with exact next steps covered below. We can help walk through this when you get there. Most of this is covered in the same creation communication docs as above.
- [ ] Archive the member and lead/chair mailing lists/[GoogleGroups]
@ -97,8 +90,8 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
[steering committee repo]: https://github.com/kubernetes/steering
[discuss.kubernetes.io]: https://discuss.kubernetes.io
[subproject]: /governance.md#subprojects
[Creation]: (#Creation)
[Retirement]: (#Retirement)
[Creation]: #Creation
[Retirement]: #Retirement
[sig-governance.md]: /committee-steering/governance/sig-governance.md
[SIG charter process]: /committee-steering/governance
[wg-governance.md]: /committee-steering/governance/wg-governance.md
@ -115,3 +108,4 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
[discuss-guidelines.md]: /communication/discuss-guidelines.md
[Thursday community updates]: /events/community-meeting.md
[example]: https://docs.google.com/document/d/1qZcAvuWBznR_oEaPWtwm7U4JNT91m8r9YOUvInU-src/edit#heading=h.jsw0l2t0ra8
[update meetings]: /communication/calendar-guidelines.md

147
sigs.yaml
View File

@ -563,6 +563,12 @@ sigs:
- name: aws-ebs-csi-driver
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/aws-ebs-csi-driver/master/OWNERS
- name: aws-efs-csi-driver
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/aws-efs-csi-driver/master/OWNERS
- name: aws-fsx-csi-driver
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/aws-fsx-csi-driver/master/OWNERS
- name: Azure
dir: sig-azure
mission_statement: >
@ -611,52 +617,6 @@ sigs:
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/azuredisk-csi-driver/master/OWNERS
- https://raw.githubusercontent.com/kubernetes-sigs/azurefile-csi-driver/master/OWNERS
- name: Big Data
dir: sig-big-data
mission_statement: >
Covers deploying and operating big data applications (Spark, Kafka,
Hadoop, Flink, Storm, etc) on Kubernetes. We focus on integrations with
big data applications and architecting the best ways to run them on Kubernetes.
charter_link:
label: big-data
leadership:
chairs:
- name: Anirudh Ramanathan
github: foxish
company: Rockset
- name: Erik Erlandson
github: erikerlandson
company: Red Hat
- name: Yinan Li
github: liyinan926
company: Google
meetings:
- description: Regular SIG Meeting
day: Wednesday
time: "17:00"
tz: "UTC"
frequency: biweekly
url: https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit
archive_url: https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit
recordings_url: https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit
contact:
slack: sig-big-data
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-big-data
teams:
- name: sig-big-data-api-reviews
description: API Changes and Reviews
- name: sig-big-data-bugs
description: Bug Triage and Troubleshooting
- name: sig-big-data-feature-requests
description: Feature Requests
- name: sig-big-data-misc
description: General Discussion
- name: sig-big-data-pr-reviews
description: PR Reviews
- name: sig-big-data-proposals
description: Design Proposals
- name: sig-big-data-test-failures
description: Test Failures and Triage
- name: CLI
dir: sig-cli
mission_statement: >
@ -725,7 +685,6 @@ sigs:
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/kubectl/OWNERS
- name: kustomize
owners:
# "owners" entry
- https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/OWNERS
- name: cli-sdk
owners:
@ -733,6 +692,17 @@ sigs:
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/cli-runtime/OWNERS
- https://raw.githubusercontent.com/kubernetes/sample-cli-plugin/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/sample-cli-plugin/OWNERS
- name: krew
description: Plugin manager for kubectl.
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/krew/master/OWNERS
- name: krew-index
description: Centralized plugin index for krew.
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/krew-index/master/OWNERS
- name: cli-experimental
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/cli-experimental/master/OWNERS
- name: Cloud Provider
dir: sig-cloud-provider
mission_statement: >
@ -822,8 +792,8 @@ sigs:
label: cluster-lifecycle
leadership:
chairs:
- name: Robert Bailey
github: roberthbailey
- name: Justin Santa Barbara
github: justinsb
company: Google
- name: Lucas Käldström
github: luxas
@ -831,6 +801,10 @@ sigs:
- name: Timothy St. Clair
github: timothysc
company: VMware
emeritus_leads:
- name: Robert Bailey
github: roberthbailey
company: Google
meetings:
- description: Regular SIG Meeting
day: Tuesday
@ -1083,15 +1057,19 @@ sigs:
label: docs
leadership:
chairs:
- name: Andrew Chen
github: chenopis
- name: Jared Bhatti
github: jaredbhatti
company: Google
- name: Zach Corleissen
github: zacharysarah
company: Linux Foundation
- name: Jennifer Rondeau
github: bradamant3
company: VMware
company: Stripe
emeritus_leads:
- name: Andrew Chen
github: chenopis
company: Google
meetings:
- description: Regular SIG Meeting
day: Tuesday
@ -1117,12 +1095,22 @@ sigs:
description: Documentation maintainers
- name: sig-docs-pr-reviews
description: Documentation PR reviews
- name: sig-docs-ko-owners
description: Korean localization
- name: sig-docs-en-owners
description: English content (default)
- name: sig-docs-es-owners
description: Spanish content
- name: sig-docs-de-owners
description: German content
- name: sig-docs-fr-owners
description: French content
- name: sig-docs-it-owners
description: Italian content
- name: sig-docs-ja-owners
description: Japanese localization
description: Japanese content
- name: sig-docs-ko-owners
description: Korean content
- name: sig-docs-zh-owners
description: Chinese localization
description: Chinese content
subprojects:
- name: reference-docs
owners:
@ -1292,7 +1280,7 @@ sigs:
github: csbell
company: Google
- name: Quinton Hoole
github: quinton-hoole-2
github: quinton-hoole
company: Huawei
meetings:
- description: Regular SIG Meeting
@ -1448,6 +1436,9 @@ sigs:
- name: sig-node-test-failures
description: Test Failures and Triage
subprojects:
- name: cri-api
owners:
- https://raw.githubusercontent.com/kubernetes/cri-api/master/OWNERS
- name: cri-o
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/cri-o/master/OWNERS
@ -2272,7 +2263,7 @@ workinggroups:
github: imkin
company: VMware
- name: Quinton Hoole
github: quinton-hoole-2
github: quinton-hoole
company: Huawei
- name: Nick Young
github: youngnick
@ -2540,6 +2531,42 @@ workinggroups:
contact:
slack: wg-k8s-infra
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-k8s-infra
usergroups:
- name: Big Data
dir: ug-big-data
mission_statement: >
Serve as a community resource for advising big data and data science related software projects
on techniques and best practices for integrating with Kubernetes.
Represents the concerns of users from big data communities to Kubernetes for the purposes of
driving new features and other enhancements, based on big data use cases.
charter_link:
label: big-data
leadership:
chairs:
- name: Anirudh Ramanathan
github: foxish
company: Rockset
- name: Erik Erlandson
github: erikerlandson
company: Red Hat
- name: Yinan Li
github: liyinan926
company: Google
meetings:
- description: Regular User Group Meeting
day: Wednesday
time: "18:00"
tz: "UTC"
frequency: biweekly
url: https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit
archive_url: https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit
recordings_url: https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit
contact:
slack: ug-big-data
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-ug-big-data
teams:
- name: ug-big-data
description: General Discussion
committees:
- name: Steering
dir: committee-steering
@ -2556,7 +2583,7 @@ committees:
github: bgrant0607
company: Google
- name: Brendan Burns
github: brendanburns
github: brendandburns
company: Microsoft
- name: Derek Carr
github: derekwaynecarr
@ -2657,8 +2684,6 @@ committees:
- name: Brandon Philips
github: philips
company: Red Hat
- name: Jess Frazelle
github: jessfraz
- name: CJ Cullen
github: cjcullen
company: Google

6
sig-big-data/OWNERS → ug-big-data/OWNERS
View File

@ -1,8 +1,8 @@
# See the OWNERS docs at https://go.k8s.io/owners
reviewers:
- sig-big-data-leads
- ug-big-data-leads
approvers:
- sig-big-data-leads
- ug-big-data-leads
labels:
- sig/big-data
- ug/big-data

53
ug-big-data/README.md Normal file
View File

@ -0,0 +1,53 @@
<!---
This is an autogenerated file!
Please do not edit this file directly, but instead make changes to the
sigs.yaml file in the project root.
To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
--->
# Big Data User Group
Serve as a community resource for advising big data and data science related software projects on techniques and best practices for integrating with Kubernetes. Represents the concerns of users from big data communities to Kubernetes for the purposes of driving new features and other enhancements, based on big data use cases.
## Meetings
* Regular User Group Meeting: [Wednesdays at 18:00 UTC](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=18:00&tz=UTC).
* [Meeting notes and Agenda](https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit).
* [Meeting recordings](https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit).
## Organizers
* Anirudh Ramanathan (**[@foxish](https://github.com/foxish)**), Rockset
* Erik Erlandson (**[@erikerlandson](https://github.com/erikerlandson)**), Red Hat
* Yinan Li (**[@liyinan926](https://github.com/liyinan926)**), Google
## Contact
* [Slack](https://kubernetes.slack.com/messages/ug-big-data)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-ug-big-data)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/ug%2Fbig-data)
## GitHub Teams
The below teams can be mentioned on issues and PRs in order to get attention from the right people.
Note that the links to display team membership will only work if you are a member of the org.
| Team Name | Details | Description |
| --------- |:-------:| ----------- |
| @kubernetes/ug-big-data | [link](https://github.com/orgs/kubernetes/teams/ug-big-data) | General Discussion |
<!-- BEGIN CUSTOM CONTENT -->
### Goals
- Promoting best practices for Kubernetes integrations
- Advising big data communities on Kubernetes features
- Shepherding issues and pull requests from community members
- Hosting demos and discussions of big data integrations for Kubernetes
### Non Goals
- Promoting or otherwise advocating for any specific big data project
- Software and tooling communities that have no intersection with data science or big data
<!-- END CUSTOM CONTENT -->

0
sig-big-data/resources.md → ug-big-data/resources.md
View File

2
wg-lts/README.md
View File

@ -26,7 +26,7 @@ The [charter](charter.md) defines the scope and governance of the LTS Working Gr
* Tim Pepper (**[@tpepper](https://github.com/tpepper)**), VMware
* Dhawal Yogesh Bhanusali (**[@imkin](https://github.com/imkin)**), VMware
* Quinton Hoole (**[@quinton-hoole-2](https://github.com/quinton-hoole-2)**), Huawei
* Quinton Hoole (**[@quinton-hoole](https://github.com/quinton-hoole)**), Huawei
* Nick Young (**[@youngnick](https://github.com/youngnick)**), Atlassian
## Contact