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

Merge pull request #4326 from vishakhanihore/one 

Removing the referer link files and Depreciated Directories
This commit is contained in:
Kubernetes Prow Robot 2019-12-18 11:33:58 -08:00 committed by GitHub
parent fe32b44ebd 7a91c2d5ae
commit fe850f14b7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
21 changed files with 0 additions and 750 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
communication/youtube-guidelines.md
View File

@ -1,3 +0,0 @@
This file has moved to https://git.k8s.io/community/communication/youtube/youtube-guidelines.md.
This file is a placeholder to preserve links. Please remove after 2019-11-11.

26
sig-aws/2017_goals.md
View File

@ -1,26 +0,0 @@
# Kubernetes sig-aws Goals (2017)
# IAM improvements
* We hope to offer a more seamless integration path to taking advantage of IAM roles in Kubernetes
* We are looking at implementations such as [kube2iam](https://github.com/jtblin/kube2iam)
##### Statement
Kubernetes components now have the ability to take advantage of IAM roles. The process is intuitive and easy.
# Networking in AWS
* We hope to offer a knowledge base for networking in Kubernetes on AWS
* We will consolidate networking reports and metrics around Kubernetes e2e tests and grow our metric list over time
##### Statement
A user can go to a single public location, and see a side by side comparison of networking avenues in Kubernetes on AWS.
# Federation
* We need to improve and harden our federation support in AWS
##### Statement
A user can easily deploy, configure, and run a federated Kubernetes cluster across regions in AWS. There is at least 1 central knowledge base for this concern hosted within the community.

90
sig-aws/CONTRIBUTING.md
View File

@ -1,90 +0,0 @@
# Contributing
The process for contributing code to Kubernetes via SIG-aws [community][community page].
**Note**: This page is focused on helping new contributors become active
members of the community through sustained contributions.
If you are interested in contributing to Kubernetes as a whole there is a top level
[contributor's guide][contributor guide].
## Introduction
Welcome to the Kubernetes sig-aws contributing guide. We are excited
about the prospect of you joining our [community][community page]!
Mentoring and on-boarding new contributors is critical to the success
of the project.
Please be aware that all contributions to Kubernetes require time
and commitment from project maintainers to direct and review work.
This is done in additional to many other maintainer responsibilities, and
direct engagement from maintainers is a finite resource.
## Before You Begin
**Note**: Complete the following steps before reaching out to aws community members.
### Agree to contribution rules
Follow the [CLA signup instructions](../CLA.md).
### Understand the big picture
This is important.
- Play around with Kubernetes [Kubernetes Basics Tutorial].
- Get to know possibilities to set up Kubernetes on AWS https://kubernetes.io/docs/getting-started-guides/aws/
- Understand how Kubernetes on aws differs from other installations of Kubernetes [/contributors/design-proposals/aws/aws_under_the_hood.md]
## Adopt an issue
New contributors can try the following to work on an existing bug or approved design:
- In [slack][slack-messages] (signup [here][slack-signup]),
@mention a [lead][leads] and ask if there are any issues you could pick up.
We also maintain a list of [sig aws issues where help is wanted][aws_good_starter_issues].
Most of them are not very complex, so that's probably a good starting point.
Leads can recommend issues that have enough priority to receive PR review bandwidth.
- Send an email to the _kubernetes-sig-aws@googlegroups.com_ [group]
> Subject: New sig-aws contributor _${yourName}_
>
> Body: Hello, my name is _${yourName}_. I would like to get involved in
> contributing to the Kubernetes project. I have read all of the
> user documentation listed on the community contributing page.
> What should I do next to get started?
- Attend a sig-aws [meeting] and introduce yourself as looking to get started.
## Meet the community
Engage with the SIG aws community! Let us know who you are and how things are going!
- In [slack][slack-messages] (signup [here][slack-signup]),
@mention a [lead][leads] and ask if there are any issues you could pick up, or
let them know what you are working on.
- Attend a sig-aws [meeting] and introduce yourself and what you are working on.
- The sig-aws [community page] lists sig-aws [leads], channels of [communication],
and group [meeting] times.
[@mentions]: https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams
[Kubernetes Basics Tutorial]: https://kubernetes.io/docs/tutorials/kubernetes-basics
[PR]: https://help.github.com/articles/creating-a-pull-request
[agenda]: https://docs.google.com/document/d/1-i0xQidlXnFEP9fXHWkBxqySkXwJnrGJP9OGyP2_P14/edit
[communication]: /sig-aws#contact
[community page]: /sig-aws
[contributor guide]: /contributors/guide
[design repo]: /contributors/design-proposals/aws
[development guide]: /contributors/devel/development.md
[group]: https://groups.google.com/forum/#!forum/kubernetes-sig-aws
[kops]: https://git.k8s.io/kops/
[leads]: /sig-aws#leads
[management overview]: https://kubernetes.io/docs/concepts/tools/kubectl/object-management-overview
[meeting]: /sig-aws#meetings
[slack-messages]: https://kubernetes.slack.com/messages/sig-aws
[slack-signup]: http://slack.k8s.io/
[kube-aws-tools]: kubernetes-on-aws.md
[aws_good_starter_issues]: https://github.com/kubernetes/kops/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Agood-starter-issue

8
sig-aws/OWNERS
View File

@ -1,8 +0,0 @@
# See the OWNERS docs at https://go.k8s.io/owners
reviewers:
- provider-aws
approvers:
- provider-aws
labels:
- sig/aws

45
sig-aws/README.md
View File

@ -1,45 +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
--->
# [DEPRECATED] AWS Special Interest Group
The AWS Special Interest Group is now a subproject of [SIG Cloud Provider](https://github.com/kubernetes/community/tree/master/sig-cloud-provider).
## This directory is a placeholder to preserve links. Please remove after 3 months or the release of kubernetes 1.10, whichever comes first.
The [charter](charter.md) defines the scope and governance of the [DEPRECATED] AWS Special Interest Group.
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Nishi Davidson (**[@d-nishi](https://github.com/d-nishi)**), AWS
* Justin Santa Barbara (**[@justinsb](https://github.com/justinsb)**), Google
* Kris Nova (**[@kris-nova](https://github.com/kris-nova)**), VMware
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-aws)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-aws)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Faws)
## 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-aws-misc | [link](https://github.com/orgs/kubernetes/teams/sig-aws-misc) | General Discussion |
<!-- BEGIN CUSTOM CONTENT -->
## Participate
For information on how to participate in this community, read our [contribution guidelines](CONTRIBUTING.md).
<!-- END CUSTOM CONTENT -->

56
sig-aws/charter.md
View File

@ -1,56 +0,0 @@
# SIG AWS Charter
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses the Roles and Organization Management outlined in [sig-governance].
## Scope
SIG AWS is responsible for the creation and maintenance of subprojects (features/innovations) necessary to integrate AWS services for the operation and management of Kubernetes on AWS. SIG AWS also acts as a forum for Kubernetes on AWS users/developers to raise their feature requests and support issues with. SIG leads in collaboration with SIG members will make a best effort to triage known problems within one or two release cycle of issues being reported. SIG AWS in collaboration with SIG-Testing, SIG-Scalability and SIG-Docs is responsible for integration and maintenance of tests (e2e, periodic jobs, postsubmit jobs etc.); scale-tests (load, density tests) and documentation for the scope within the purview of this charter.
### In scope
Link to SIG [subprojects](https://github.com/kubernetes/community/tree/master/sig-aws#subprojects)
#### Code, Binaries and Services
Kubernetes integrations specific to AWS including:
- Integrations, interfaces, libraries and extension points for all AWS services such as IAM, storage, networking, loadbalancers, registry, security, monitoring/logging at the instance or container level
- Tools for Kubernetes APIs to work with AWS services including Amazon EKS
- Prow, testgrid, perf dashboard integrations to expand and maintain testing (e2e, jobs) and scale-testing (load, density) on AWS and Amazon EKS
- Support users on their issues and feature requests
- Documentation for all things Kubernetes on AWS
#### Cross-cutting and Externally Facing Processes
- Consult with other SIGs and the community on how to apply mechanisms owned by SIG
AWS. Examples include:
- Review escalation implications of feature and API designs as it relates to core Kubernetes components (etcd, kubelet, apiserver, controller manager, scheduler)
- CSI, CNI, CRI implementation and design
- Cloud provider implementation and design
- Best practices for hardening add-ons or other external integrations such as KMS, LB, others.
- Implementing and hardening tests, scale tests and documentation
### Out of scope
SIG AWS is not for discussing bugs or feature requests outside the scope of Kubernetes. For example, SIG AWS should not be used to discuss or resolve support requests related to AWS Services. It should also not be used to discuss topics that other, more specialized SIGs own (to avoid overlap). Examples of such scenarios include:
- Specification of CSI, CRI interfaces, cloudprovider binary (prefer: sig-storage, sig-node and sig-cloudprovider)
- Container runtime (prefer: sig-node and sig-networking)
- Resource quota (prefer: sig-scheduling)
- Resource availability (prefer: sig-apimachinery, sig-network, sig-node)
- Detailed design and scope of tests or tooling to run tests (prefer: sig-testing)
- Detailed design and scope of scale tests or tooling to run scale tests (prefer: sig-scalability)
- Troubleshooting and maintenance of test jobs related to kops (prefer: sig-cluster-lifecyle)
- Reporting specific vulnerabilities in Kubernetes. Please report using these instructions: https://kubernetes.io/security/
## Roles and Organization Management
This SIG adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].
### Subproject Creation
SIG AWS delegates subproject approval to Chairs. Chairs also act as Technical Leads in SIG AWS. See [Subproject creation - Option 1].
[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-aws/README.md#subprojects
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
[Subproject creation - Option 1]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#subproject-creation

21
sig-aws/kubernetes-on-aws.md
View File

@ -1,21 +0,0 @@
Kubernetes on Amazon Web Services
====
This page lists different options, in alphabetic order, of starting a Kubernetes cluster on Amazon Web Services.
* Clocker: http://www.clocker.io/tutorials/kubernetes-cluster.html
* Heptio: https://github.com/aws-quickstart/quickstart-heptio
* Juju Charms: https://jujucharms.com/canonical-kubernetes/
* KAT - Kubernetes cluster on AWS with Terraform: https://github.com/xuwang/kube-aws-terraform
* Kargo: https://github.com/kubernetes-incubator/kargo
* Kismatic Enterprise Toolkit: https://github.com/apprenda/kismatic
* Kraken 2: https://github.com/samsung-cnct/k2
* kube-aws: https://github.com/kubernetes-incubator/kube-aws
* Kubeadm Quickstart: https://github.com/upmc-enterprises/kubeadm-aws
* Kubernetes on AWS: https://github.com/zalando-incubator/kubernetes-on-aws/
* Kubernetes Operations (kops): https://github.com/kubernetes/kops
* OpenShift: https://access.redhat.com/articles/2623521
* Stackpoint.io: https://stackpoint.io
* Tack: https://github.com/kz8s/tack
* Tectonic: http://github.com/coreos/tectonic-installer
* Weaveworks AMI: https://github.com/weaveworks/kubernetes-ami

8
sig-azure/OWNERS
View File

@ -1,8 +0,0 @@
# See the OWNERS docs at https://go.k8s.io/owners
reviewers:
- provider-azure
approvers:
- provider-azure
labels:
- sig/azure

58
sig-azure/README.md
View File

@ -1,58 +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
--->
# [DEPRECATED] Azure Special Interest Group
The Azure Special Interest Group is now a subproject of [SIG Cloud Provider](https://github.com/kubernetes/community/tree/master/sig-cloud-provider).
### (This directory is a placeholder to preserve links. Please remove after 6 months or the release of Kubernetes 1.17, whichever comes first.)
The [charter](charter.md) defines the scope and governance of the [DEPRECATED] Azure Special Interest Group.
## Meetings
* Regular SIG Meeting: [Wednesdays at 16:00 UTC](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:00&tz=UTC).
* [Meeting notes and Agenda](https://docs.google.com/document/d/1SpxvmOgHDhnA72Z0lbhBffrfe9inQxZkU9xqlafOW9k/edit).
* [Meeting recordings](https://www.youtube.com/watch?v=yQLeUKi_dwg&list=PL69nYSiGNLP2JNdHwB8GxRs2mikK7zyc4).
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Craig Peters (**[@craiglpeters](https://github.com/craiglpeters)**), Microsoft
* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), VMware
### Technical Leads
The Technical Leads of the SIG establish new subprojects, decommission existing
subprojects, and resolve cross-subproject technical issues and decisions.
* Pengfei Ni (**[@feiskyer](https://github.com/feiskyer)**), Microsoft
* Kal Khenidak (**[@khenidak](https://github.com/khenidak)**), Microsoft
## Emeritus Leads
* Dave Strebel (**[@dstrebel](https://github.com/dstrebel)**), Microsoft
* Jaice Singer DuMars (**[@jdumars](https://github.com/jdumars)**), Google
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-azure)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-azure)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fazure)
## 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-azure | [link](https://github.com/orgs/kubernetes/teams/sig-azure) | General Discussion |
<!-- BEGIN CUSTOM CONTENT -->
<!-- END CUSTOM CONTENT -->

100
sig-azure/charter.md
View File

@ -1,100 +0,0 @@
# SIG Azure Charter
_The following is a charter for the Kubernetes Special Interest Group for Azure. It delineates the roles of SIG leadership, SIG members, as well as the organizational processes for the SIG, both as they relate to project management and technical processes for SIG subprojects._
## Roles
### SIG Chairs
- Run operations and processes governing the SIG
- Seed members established at SIG founding
- Chairs MAY decide to step down at anytime and propose a replacement. Use lazy consensus amongst chairs with fallback on majority vote to accept proposal. This SHOULD be supported by a majority of SIG Members.
- Chairs MAY select additional chairs through a [super-majority] vote amongst chairs. This SHOULD be supported by a majority of SIG Members.
- Chairs MUST remain active in the role and are automatically removed from the position if they are unresponsive for &gt; 3 months and MAY be removed if not proactively working with other chairs to fulfill responsibilities. Coordinated leaves of absence serve as exception to this requirement.
- Number: 2 - 3
- Defined in [sigs.yaml]
### SIG Technical Leads
- Establish new subprojects
- Decommission existing subprojects
- Resolve X-Subproject technical issues and decisions
- Technical Leads MUST remain active in the role and are automatically removed from the position if they are unresponsive for &gt; 3 months and MAY be removed if not proactively working with other chairs to fulfill responsibilities. Coordinated leaves of absence serve as exception to this requirement.
- Number: 2 - 3
- Defined in [sigs.yaml]
### Subproject Owners
- Scoped to a subproject defined in [sigs.yaml]
- Seed members established at subproject founding
- MUST be an escalation point for technical discussions and decisions in the subproject
- 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 &gt; 3 months. Coordinated leaves of absence serve as exception to this requirement.
- MAY be removed if not proactively working with other Subproject Owners to fulfill responsibilities.
- MAY decide to step down at anytime and propose a replacement. Use [lazy-consensus] amongst subproject owners with fallback on majority vote to accept proposal. This SHOULD be supported by a majority of subproject contributors (those having some role in the subproject).
- MAY select additional subproject owners through a [super-majority] vote amongst subproject owners. This SHOULD be supported by a majority of subproject contributors (through [lazy-consensus] with fallback on voting).
- Number: 3 - 5
- Defined in [sigs.yaml] [OWNERS] files
**IMPORTANT**
_With regards to leadership roles i.e., Chairs, Technical Leads, and Subproject Owners, we MUST, as a SIG, ensure that positions are held by a committee of members across a diverse set of companies. This allows for thoughtful discussion and structural management that can serve the needs of every consumer of Kubernetes on Azure._
### Members
- MUST maintain health of at least one subproject or the health of the SIG
- MUST show sustained contributions to at least one subproject or to the SIG
- SHOULD hold some documented role or responsibility in the SIG and / or at least one subproject (e.g. reviewer, approver, etc)
- MAY build new functionality for subprojects
- MAY participate in decision making for the subprojects they hold roles in
- Includes all reviewers and approvers in [OWNERS] files for subprojects
## Organizational management
- SIG meets bi-weekly on zoom with agenda in meeting notes
- SHOULD be facilitated by chairs unless delegated to specific Members
- SIG overview and deep-dive sessions organized for KubeCon/CloudNativeCon
- SHOULD be organized by chairs unless delegated to specific Members
- Contributing instructions defined in the SIG CONTRIBUTING.md
### Project management
#### Subproject creation
Subprojects
may be created by [KEP] proposal and accepted by [lazy-consensus] with fallback on majority vote of SIG Technical Leads. The result SHOULD be supported by the majority of SIG members.
- KEP MUST establish subproject owners
- [sigs.yaml] MUST be updated to include subproject information and [OWNERS] files with subproject owners
- Where subprojects processes differ from the SIG governance, they MUST document how
- e.g., if subprojects release separately - they must document how release and planning is performed
Subprojects must define how releases are performed and milestones are set.
Example:
- Release milestones
- Follows the kubernetes/kubernetes release milestones and schedule
- Priorities for upcoming release are discussed during the SIG meeting following the preceding release and shared through a PR. Priorities are finalized before feature freeze.
- Code and artifacts are published as part of the kubernetes/kubernetes release
### Technical processes
Subprojects of the SIG MUST use the following processes unless explicitly following alternatives they have defined.
- Proposing and making decisions
- Proposals sent as [KEP] PRs and published to Google group as announcement
- Follow [KEP] decision making process
- Test health
- Canonical health of code published to
- Consistently broken tests automatically send an alert to
- SIG members are responsible for responding to broken tests alert. PRs that break tests should be rolled back if not fixed within 24 hours (business hours).
- Test dashboard checked and reviewed at start of each SIG meeting. Owners assigned for any broken tests. and followed up during the next SIG meeting.
Issues impacting multiple subprojects in the SIG should be resolved by SIG Technical Leads, with fallback to consensus of subproject owners.
[lazy-consensus]: http://en.osswiki.info/concepts/lazy_consensus
[super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote
[KEP]: https://git.k8s.io/enhancements/keps/YYYYMMDD-kep-template.md
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454
[OWNERS]: /contributors/guide/owners.md

3
sig-contributor-experience/markdown-link-style-guide.md
View File

@ -1,3 +0,0 @@
This file has moved to https://git.k8s.io/community/contributors/guide/style-guide.md.
This file is a placeholder to preserve links. Please remove after 2020-03-30 or the release of Kubernetes 1.18, whichever comes first.

8
sig-gcp/OWNERS
View File

@ -1,8 +0,0 @@
# See the OWNERS docs at https://go.k8s.io/owners
reviewers:
- provider-gcp
approvers:
- provider-gcp
labels:
- sig/gcp

48
sig-gcp/README.md
View File

@ -1,48 +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
--->
# [DEPRECATED] GCP Special Interest Group
The GCP Special Interest Group is now a subproject of [SIG Cloud Provider](https://github.com/kubernetes/community/tree/master/sig-cloud-provider).
### (This directory is a placeholder to preserve links. Please remove after 6 months or the release of Kubernetes 1.17, whichever comes first.)
The [charter](charter.md) defines the scope and governance of the [DEPRECATED] GCP Special Interest Group.
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Adam Worrall (**[@abgworrall](https://github.com/abgworrall)**), Google
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-gcp)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-gcp)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fgcp)
## 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-gcp-api-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-gcp-api-reviews) | API Changes and Reviews |
| @kubernetes/sig-gcp-bugs | [link](https://github.com/orgs/kubernetes/teams/sig-gcp-bugs) | Bug Triage and Troubleshooting |
| @kubernetes/sig-gcp-feature-requests | [link](https://github.com/orgs/kubernetes/teams/sig-gcp-feature-requests) | Feature Requests |
| @kubernetes/sig-gcp-misc | [link](https://github.com/orgs/kubernetes/teams/sig-gcp-misc) | General Discussion |
| @kubernetes/sig-gcp-pr-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-gcp-pr-reviews) | PR Reviews |
| @kubernetes/sig-gcp-proposals | [link](https://github.com/orgs/kubernetes/teams/sig-gcp-proposals) | Design Proposals |
| @kubernetes/sig-gcp-test-failures | [link](https://github.com/orgs/kubernetes/teams/sig-gcp-test-failures) | Test Failures and Triage |
<!-- BEGIN CUSTOM CONTENT -->
<!-- END CUSTOM CONTENT -->

8
sig-ibmcloud/OWNERS
View File

@ -1,8 +0,0 @@
# See the OWNERS docs at https://go.k8s.io/owners
reviewers:
- provider-ibmcloud
approvers:
- provider-ibmcloud
labels:
- sig/ibmcloud

46
sig-ibmcloud/README.md
View File

@ -1,46 +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
--->
# [DEPRECATED] IBMCloud Special Interest Group
The IBMCloud Special Interest Group is now a subproject of [SIG Cloud Provider](https://github.com/kubernetes/community/tree/master/sig-cloud-provider).
### (This directory is a placeholder to preserve links. Please remove after 6 months or the release of Kubernetes 1.17, whichever comes first.)
The [charter](charter.md) defines the scope and governance of the [DEPRECATED] IBMCloud Special Interest Group.
## Meetings
* Regular SIG Meeting: [Wednesdays at 14:00 EST](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=14:00&tz=EST).
* [Meeting notes and Agenda](https://docs.google.com/document/d/1qd_LTu5GFaxUhSWTHigowHt3XwjJVf1L57kupj8lnwg/edit).
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Khalid Ahmed (**[@khahmed](https://github.com/khahmed)**), IBM
* Richard Theis (**[@rtheis](https://github.com/rtheis)**), IBM
* Sahdev Zala (**[@spzala](https://github.com/spzala)**), IBM
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-ibmcloud)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-ibmcloud)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fibmcloud)
## 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-ibmcloud-misc | [link](https://github.com/orgs/kubernetes/teams/sig-ibmcloud-misc) | General Discussion |
<!-- BEGIN CUSTOM CONTENT -->
<!-- END CUSTOM CONTENT -->

38
sig-ibmcloud/charter.md
View File

@ -1,38 +0,0 @@
# SIG IBMCloud Charter
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].
## Scope
The IBMCloud SIG enables activities and discussion around building, deploying, maintaining, supporting,
and using Kubernetes on IBM Public and Private Clouds.
### In scope
- Determining and documenting best practices for configuring Kubernetes on IBM Cloud Kubernetes Service (IKS).
- Determining and documenting best practices for configuring Kubernetes on IBM Cloud Private (ICP).
- Discussing IKS and ICP tracking of Kubernetes features and releases.
- Utilizing Kubernetes and related CNCF projects (e.g. Helm, Istio) by IKS and ICP.
- Discussing bugs and feature requests recorded as Kubernetes upstream issues on GitHub. These issues should be tagged with `sig/ibmcloud`.
#### Code, Binaries and Services
The work to have a cloud provider specific public code repository is in progress. This section will be updated once the work is complete. Kubernetes upstream code that
is directly related to IKS or ICP issues or features can be discussed.
### Out of scope
* Internal or commercial aspects of IKS and ICP.
## Roles and Organization Management
This SIG adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance], with exception that the SIG only
has the Chair role at present. Chairs must also fulfill all of the responsibilities of the Tech Lead role as outlined in [sig-governance].
### Subproject Creation
Associated subprojects are created following the `by SIG Technical Leads` option procedure described in [sig-governance].
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
[SIG README]: https://github.com/kubernetes/community/blob/master/sig-ibmcloud/README.md

8
sig-openstack/OWNERS
View File

@ -1,8 +0,0 @@
# See the OWNERS docs at https://go.k8s.io/owners
reviewers:
- provider-openstack
approvers:
- provider-openstack
labels:
- sig/openstack

57
sig-openstack/README.md
View File

@ -1,57 +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
--->
# [DEPRECATED] OpenStack Special Interest Group
The OpenStack Special Interest Group is now a subproject of [SIG Cloud Provider](https://github.com/kubernetes/community/tree/master/sig-cloud-provider).
### (This directory is a placeholder to preserve links. Please remove after 6 months or the release of Kubernetes 1.17, whichever comes first.)
The [charter](charter.md) defines the scope and governance of the [DEPRECATED] OpenStack Special Interest Group.
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Aditi Sharma (**[@adisky](https://github.com/adisky)**), NEC Technologies India
* Christoph Glaubitz (**[@chrigl](https://github.com/chrigl)**), iNNOVO Cloud
* Chris Hoge (**[@hogepodge](https://github.com/hogepodge)**), OpenStack Foundation
## Emeritus Leads
* David Lyle (**[@dklyle](https://github.com/dklyle)**), Intel
* Ihor Dvoretskyi (**[@idvoretskyi](https://github.com/idvoretskyi)**), CNCF
* Robert Morse (**[@rjmorse](https://github.com/rjmorse)**), Ticketmaster
* Steve Gordon (**[@xsgordon](https://github.com/xsgordon)**), Red Hat
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-openstack)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-openstack)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fopenstack)
## 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-openstack-api-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-openstack-api-reviews) | API Changes and Reviews |
| @kubernetes/sig-openstack-bugs | [link](https://github.com/orgs/kubernetes/teams/sig-openstack-bugs) | Bug Triage and Troubleshooting |
| @kubernetes/sig-openstack-feature-requests | [link](https://github.com/orgs/kubernetes/teams/sig-openstack-feature-requests) | Feature Requests |
| @kubernetes/sig-openstack-misc | [link](https://github.com/orgs/kubernetes/teams/sig-openstack-misc) | General Discussion |
| @kubernetes/sig-openstack-pr-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-openstack-pr-reviews) | PR Reviews |
| @kubernetes/sig-openstack-proposals | [link](https://github.com/orgs/kubernetes/teams/sig-openstack-proposals) | Design Proposals |
| @kubernetes/sig-openstack-test-failures | [link](https://github.com/orgs/kubernetes/teams/sig-openstack-test-failures) | Test Failures and Triage |
<!-- BEGIN CUSTOM CONTENT -->
<!-- END CUSTOM CONTENT -->

8
sig-vmware/OWNERS
View File

@ -1,8 +0,0 @@
# See the OWNERS docs at https://go.k8s.io/owners
reviewers:
- provider-vmware
approvers:
- provider-vmware
labels:
- sig/vmware

50
sig-vmware/README.md
View File

@ -1,50 +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
--->
# [DEPRECATED] VMware Special Interest Group
The VMware Special Interest Group is now a subproject of [SIG Cloud Provider](https://github.com/kubernetes/community/tree/master/sig-cloud-provider).
### (This directory is a placeholder to preserve links. Please remove after 6 months or the release of Kubernetes 1.17, whichever comes first.)
The [charter](charter.md) defines the scope and governance of the [DEPRECATED] VMware Special Interest Group.
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Steve Wong (**[@cantbewong](https://github.com/cantbewong)**), VMware
* Fabio Rapposelli (**[@frapposelli](https://github.com/frapposelli)**), VMware
## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-vmware)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-vmware)
* [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fvmware)
## 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-vmware-api-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-api-reviews) | API Changes and Reviews |
| @kubernetes/sig-vmware-bugs | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-bugs) | Bug Triage and Troubleshooting |
| @kubernetes/sig-vmware-feature-requests | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-feature-requests) | Feature Requests |
| @kubernetes/sig-vmware-members | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-members) | Release Team Members |
| @kubernetes/sig-vmware-misc | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-misc) | General Discussion |
| @kubernetes/sig-vmware-pr-reviews | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-pr-reviews) | PR Reviews |
| @kubernetes/sig-vmware-proposals | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-proposals) | Design Proposals |
| @kubernetes/sig-vmware-test-failures | [link](https://github.com/orgs/kubernetes/teams/sig-vmware-test-failures) | Test Failures and Triage |
<!-- BEGIN CUSTOM CONTENT -->
<!-- END CUSTOM CONTENT -->

61
sig-vmware/charter.md
View File

@ -1,61 +0,0 @@
# SIG VMware Charter
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].
## Scope
The VMware SIG maintains and evolves the ability to run Kubernetes on VMware infrastructure.
In addition to the cloud provider for the vSphere hypervisor, the SIG’s mission includes:
- NSX and NSX-T, infrastructure components that provide software based networking service, with automated micro-segmentation at application and control plane levels - along with security, monitoring, logging, and features for multi-cluster, multi-site, and cross cloud integration. NSX-T is not vSphere specific, and is supported on other cloud providers (e.g. OpenStack). The scope of NSX and NSX-T interaction with Kubernetes goes beyond the CNI plug-in abstraction.
- Desktop hypervisors (Fusion for OS X and Workstation for Linux and Windows), as supported by Minikube.
- vCloud Director, which enables service providers to provision and manage multi tenant clouds, which can host Kubernetes.
- Hosting architectural planning and discussion related to new CRDs, plug-ins and KEPs that allow the vSphere platform to supplement the existing capabilities of Kubernetes, container runtime, and OS functionality
### In scope
- Deploying Kubernetes of any type (standard or a packaged distribution from any vendor) on vSphere infrastructure.
- Utilizing networking and storage features of VMware infrastructure through Kubernetes.
- Determining and documenting best practices for configuring Kubernetes when running on vSphere infrastructure.
- Determining and documenting best practices for configuring VMware infrastructure when supporting Kubernetes.
- Determining and documenting best practices for using common configuration management and orchestration tools for deploying and managing Kubernetes on VMware infrastructure.
- Discussing bugs and feature requests recorded as Kubernetes or VMware cloud provider issues on GitHub. These issues should be tagged with ``sig/vmware``.
A directory of specialized subject area GitHub teams for issues, PRs, and design proposals is defined in [SIG GitHub Teams](https://github.com/kubernetes/community/tree/master/sig-vmware#github-teams).
#### Code, Binaries and Services
- vSphere Cloud Provider
- vRealize Automation Cluster API Provider
Code locations and projects are defined in [SIG Subprojects](https://github.com/kubernetes/community/tree/master/sig-vmware#subprojects)
#### Cross-cutting and Externally Facing Processes
SIG VMware serves to bring together members of the VMware and Kubernetes community to maintain, support and provide guidance for running Kubernetes on VMware platforms.
The VMware SIG will provide a forum for hosting related architectural planning and discussion. Associated activities related to development, testing, and documentation will be tracked and reported by the SIG.
- The vSphere platform’s availability and resource management can create pools that extend across Kubernetes worker node, management node, and namespace boundaries. Unique features of the vSphere platform related to high availability, load balancing, and resource management (storage, networking, compute) can supplement existing capabilities of Kubernetes, container runtime, and OS functionality.
- We drive changes that cross existing SIG boundaries by collaborating with the appropriate SIGs (eg: node, schedule, scalability, etc.)
- We co-own vSphere-specific code related to cluster and machine provisioning with sig-cluster-lifecycle and the cluster-api subproject.
- We co-own the cloud-provider-vsphere code with sig-cloud-provider
- We define requirements, interfaces, and end-to-end tests related to vSphere-specific storage with sig-storage
### Out of scope
The VMware SIG is not for discussing bugs or feature requests outside the scope of Kubernetes. For example, the VMware SIG should not be used to discuss or resolve support requests related to VMware products. It should also not be used to discuss topics that other, more specialized SIGs own (to avoid overlap).
## 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].
### Subproject Creation
Associated subprojects are created following the Federation of Subprojects procedure described in [sig-governance]
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md