├── keps ├── NEXT_KEP_NUMBER ├── sig-apps │ ├── README.md │ └── OWNERS ├── sig-network │ ├── README.md │ └── OWNERS ├── sig-cluster-lifecycle │ ├── README.md │ └── OWNERS ├── sig-contributor-experience │ └── OWNERS └── OWNERS ├── generator ├── .gitignore ├── testdata │ ├── example.tmpl │ ├── sigs.yaml │ ├── example.md │ ├── no_custom_content.md │ └── custom_content.md ├── OWNERS ├── header.tmpl ├── aliases.tmpl └── list.tmpl ├── contributors ├── design-proposals │ ├── scheduling │ │ ├── images │ │ │ ├── .gitignore │ │ │ ├── OWNERS │ │ │ ├── preemption_1.png │ │ │ ├── preemption_2.png │ │ │ ├── preemption_3.png │ │ │ ├── preemption_4.png │ │ │ └── preemption_flowchart.png │ │ └── OWNERS │ ├── cluster-lifecycle │ │ ├── clustering │ │ │ ├── .gitignore │ │ │ ├── OWNERS │ │ │ ├── dynamic.png │ │ │ ├── static.png │ │ │ ├── static.seqdiag │ │ │ ├── README.md │ │ │ ├── dynamic.seqdiag │ │ │ ├── Dockerfile │ │ │ └── Makefile │ │ ├── OWNERS │ │ ├── self-hosted-layers.png │ │ ├── self-hosted-final-cluster.png │ │ ├── self-hosted-moving-parts.png │ │ └── high-availability.md │ ├── aws │ │ └── OWNERS │ ├── cli │ │ └── OWNERS │ ├── gcp │ │ └── OWNERS │ ├── apps │ │ └── OWNERS │ ├── auth │ │ ├── OWNERS │ │ ├── kms-grpc-class-diagram.png │ │ └── kms-grpc-deployment-diagram.png │ ├── node │ │ ├── OWNERS │ │ ├── pleg.png │ │ ├── pod-cache.png │ │ └── kubelet-hypercontainer-runtime.md │ ├── network │ │ └── OWNERS │ ├── release │ │ └── OWNERS │ ├── storage │ │ ├── OWNERS │ │ ├── volume-snapshotting.png │ │ ├── volume-topology-scheduling.png │ │ ├── container-storage-interface_diagram1.png │ │ └── containerized-mounter.md │ ├── testing │ │ └── OWNERS │ ├── resource-management │ │ ├── OWNERS │ │ ├── device-plugin.png │ │ └── device-plugin-overview.png │ ├── autoscaling │ │ ├── OWNERS │ │ └── images │ │ │ └── vpa-architecture.png │ ├── multicluster │ │ ├── OWNERS │ │ ├── ubernetes-design.png │ │ ├── ubernetes-scheduling.png │ │ ├── ubernetes-cluster-state.png │ │ ├── federation-high-level-arch.png │ │ └── federated-api-servers.md │ ├── scalability │ │ ├── OWNERS │ │ └── Kubemark_architecture.png │ ├── api-machinery │ │ └── OWNERS │ ├── architecture │ │ ├── images │ │ │ └── apiserver.png │ │ └── OWNERS │ ├── vault-based-kms-class-diagram.png │ ├── instrumentation │ │ ├── OWNERS │ │ └── monitoring_architecture.png │ ├── service-catalog │ │ └── OWNERS │ ├── OWNERS │ ├── README.md │ └── Design_Proposal_TEMPLATE.md ├── devel │ ├── issues.md │ ├── pr_workflow.dia │ ├── pr_workflow.png │ ├── arch-roadmap-1.png │ ├── welcome-to-kubernetes-new-developer-guide.md │ ├── gubernator-images │ │ ├── skipping1.png │ │ ├── skipping2.png │ │ ├── filterpage.png │ │ ├── filterpage1.png │ │ ├── filterpage2.png │ │ ├── filterpage3.png │ │ └── testfailures.png │ ├── adding-an-APIGroup.md │ ├── client-libraries.md │ ├── how-to-doc.md │ ├── OWNERS │ ├── help-wanted.md │ ├── logging.md │ ├── getting-builds.md │ ├── collab.md │ ├── cherry-picks.md │ ├── staging.md │ └── cri-validation.md ├── guide │ ├── git_workflow.png │ ├── OWNERS │ ├── release-notes.md │ └── contributor-cheatsheet.md └── new-contributor-playground │ ├── OWNERS │ └── README.md ├── hack ├── .spelling_failures ├── OWNERS ├── verify-spelling.sh └── verify-generated-docs.sh ├── communication.md ├── sig-apps ├── minutes │ ├── OWNERS │ ├── README.md │ ├── 2016-05-25.md │ ├── 2016-07-06.md │ ├── 2016-07-20.md │ ├── 2016-05-18.md │ ├── 2016-06-29.md │ ├── 2016-06-22.md │ ├── 2016-06-15.md │ ├── 2016-07-13.md │ ├── 2016-08-03.md │ ├── 2016-06-08.md │ └── 2016-07-27.md └── OWNERS ├── sig-rktnetes ├── OWNERS └── README.md ├── wg-app-def ├── OWNERS └── README.md ├── archive ├── README.md └── sig-configuration │ └── README.md ├── sig-cluster-lifecycle ├── postmortems │ └── OWNERS ├── OWNERS └── migrated-from-wiki │ └── README.md ├── sig-ui ├── OWNERS └── README.md ├── wg-cluster-api ├── OWNERS └── README.md ├── wg-multitenancy ├── OWNERS └── README.md ├── sig-aws ├── OWNERS ├── 2017_goals.md ├── kubernetes-on-aws.md └── README.md ├── sig-cli ├── OWNERS └── migrated-from-wiki │ ├── README.md │ └── contributor-guide-building-your-kubernetes-tool.md ├── sig-gcp └── OWNERS ├── sig-auth └── OWNERS ├── sig-docs ├── OWNERS └── migrated-from-wiki │ ├── README.md │ └── roadmap-docs.md ├── sig-node └── OWNERS ├── sig-azure └── OWNERS ├── sig-vmware ├── OWNERS └── README.md ├── wg-kubeadm-adoption ├── OWNERS └── README.md ├── sig-creation-procedure.md ├── sig-network └── OWNERS ├── sig-release └── OWNERS ├── sig-storage ├── OWNERS └── 1.3-retrospective │ └── OWNERS ├── sig-testing └── OWNERS ├── sig-windows └── OWNERS ├── wg-container-identity ├── OWNERS └── README.md ├── wg-resource-management └── OWNERS ├── sig-big-data ├── OWNERS └── resources.md ├── sig-openstack └── OWNERS ├── committee-steering ├── OWNERS └── governance │ ├── README.md │ └── FAQ.md ├── sig-autoscaling └── OWNERS ├── sig-cluster-ops ├── OWNERS └── README.md ├── sig-scalability └── OWNERS ├── sig-scheduling └── OWNERS ├── events ├── 2016 │ ├── developer-summit-2016 │ │ ├── k8sDevSummitSchedule.pdf │ │ ├── cluster_federation_notes.md │ │ └── KubDevSummitVoting.md │ └── Kubernetes_1st_Bday.md ├── 2017 │ ├── 12-contributor-summit │ │ ├── schedule.png │ │ ├── feature-roadmap-2018.jpg │ │ ├── Meeting Room 4ABC - 1st set, Tues fishbowl.PNG │ │ ├── Meeting Room 6A and 6B - 1st Set, Tues fishbowl.PNG │ │ ├── current-state-of-client-libraries.md │ │ ├── steering-committee-update.md │ │ └── scaling-new-contributors.md │ └── 05-leadership-summit │ │ ├── session-notes │ │ ├── 1345-1430_SIGGOVERNANCE.md │ │ └── readme.md │ │ └── announcement.md ├── OWNERS └── elections │ └── 2017 │ ├── RESULTS.md │ ├── aaroncrickenberger_bio.md │ ├── errordeveloper_bio.md │ ├── michaelrubin_bio.md │ ├── kris-nova_bio.md │ ├── alexpollitt_bio.md │ ├── timothysc_bio.md │ ├── jaicesingerdumars_bio.md │ ├── calebamiles_bio.md │ ├── dougdavis_bio.md │ ├── vote_for_justinsb.md │ ├── adnanabdulhussein_bio.md │ ├── mattfarina_bio.md │ ├── pwittrock_bio.md │ ├── rhirschfeld_bio.md │ ├── derekcarr_bio.md │ ├── idvoretskyi_bio.md │ └── aaronschlesinger_bio.md ├── sig-architecture ├── OWNERS ├── backlog.md └── charter.md ├── sig-multicluster └── OWNERS ├── Gopkg.toml ├── sig-api-machinery └── OWNERS ├── sig-product-management └── OWNERS ├── sig-instrumentation └── OWNERS ├── sig-service-catalog └── OWNERS ├── .travis.yml ├── project-managers ├── OWNERS └── README.md ├── mentoring ├── OWNERS ├── the1-on-1hour.md ├── mentoring-events.md └── README.md ├── code-of-conduct.md ├── sig-contributor-experience ├── OWNERS ├── migrated-from-wiki │ ├── README.md │ └── effective-reviewable.md └── markdown-link-style-guide.md ├── OWNERS ├── communication └── OWNERS ├── .github └── PULL_REQUEST_TEMPLATE ├── vendor ├── github.com │ └── client9 │ │ └── misspell │ │ ├── url.go │ │ ├── LICENSE │ │ ├── case.go │ │ ├── ascii.go │ │ ├── legal.go │ │ └── notwords.go └── gopkg.in │ └── yaml.v2 │ ├── NOTICE │ ├── writerc.go │ └── LICENSE.libyaml ├── .gitignore ├── Makefile ├── Gopkg.lock ├── .generated_files ├── wg-apply └── README.md ├── CONTRIBUTING.md ├── wg-cloud-provider └── README.md ├── wg-policy └── README.md ├── wg-machine-learning └── README.md ├── sig-ibmcloud └── README.md └── README.md /keps/NEXT_KEP_NUMBER: -------------------------------------------------------------------------------- 1 | 8 2 | -------------------------------------------------------------------------------- /generator/.gitignore: -------------------------------------------------------------------------------- 1 | generated/ 2 | -------------------------------------------------------------------------------- /generator/testdata/example.tmpl: -------------------------------------------------------------------------------- 1 | {{.Message}} 2 | -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/images/.gitignore: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /hack/.spelling_failures: -------------------------------------------------------------------------------- 1 | events/elections/2017/ 2 | vendor/ 3 | -------------------------------------------------------------------------------- /communication.md: -------------------------------------------------------------------------------- 1 | **NOTE:** This document has moved to [a new location](communication/). 2 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/.gitignore: -------------------------------------------------------------------------------- 1 | DroidSansMono.ttf 2 | -------------------------------------------------------------------------------- /sig-apps/minutes/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - EnergyLiYN 3 | approvers: 4 | - EnergyLiYN 5 | -------------------------------------------------------------------------------- /sig-rktnetes/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - calebamiles 3 | approvers: 4 | - calebamiles 5 | -------------------------------------------------------------------------------- /wg-app-def/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - wg-app-def-leads 3 | approvers: 4 | - wg-app-def-leads 5 | -------------------------------------------------------------------------------- /keps/sig-apps/README.md: -------------------------------------------------------------------------------- 1 | # SIG Apps KEPs 2 | 3 | This directory contains KEPs related to SIG Apps. 4 | -------------------------------------------------------------------------------- /archive/README.md: -------------------------------------------------------------------------------- 1 | # Archive 2 | 3 | The archive contains SIG information for those no longer active. 4 | -------------------------------------------------------------------------------- /sig-cluster-lifecycle/postmortems/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - pipejakob 3 | approvers: 4 | - pipejakob 5 | -------------------------------------------------------------------------------- /generator/testdata/sigs.yaml: -------------------------------------------------------------------------------- 1 | sigs: 2 | - name: Foo 3 | - name: Bar 4 | workinggroups: 5 | - name: Baz 6 | -------------------------------------------------------------------------------- /keps/sig-network/README.md: -------------------------------------------------------------------------------- 1 | # SIG Network KEPs 2 | 3 | This directory contains KEPs related to SIG Network. 4 | -------------------------------------------------------------------------------- /sig-ui/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-ui-leads 3 | approvers: 4 | - sig-ui-leads 5 | labels: 6 | - sig/ui 7 | -------------------------------------------------------------------------------- /wg-cluster-api/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - wg-cluster-api-leads 3 | approvers: 4 | - wg-cluster-api-leads 5 | -------------------------------------------------------------------------------- /wg-multitenancy/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - wg-multitenancy-leads 3 | approvers: 4 | - wg-multitenancy-leads 5 | -------------------------------------------------------------------------------- /sig-aws/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-aws-leads 3 | approvers: 4 | - sig-aws-leads 5 | labels: 6 | - sig/aws 7 | -------------------------------------------------------------------------------- /sig-cli/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-cli-leads 3 | approvers: 4 | - sig-cli-leads 5 | labels: 6 | - sig/cli 7 | -------------------------------------------------------------------------------- /sig-gcp/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-gcp-leads 3 | approvers: 4 | - sig-gcp-leads 5 | labels: 6 | - sig/gcp 7 | -------------------------------------------------------------------------------- /hack/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - cblecker 3 | approvers: 4 | - cblecker 5 | labels: 6 | - sig/contributor-experience 7 | -------------------------------------------------------------------------------- /sig-apps/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-apps-leads 3 | approvers: 4 | - sig-apps-leads 5 | labels: 6 | - sig/apps 7 | -------------------------------------------------------------------------------- /sig-auth/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-auth-leads 3 | approvers: 4 | - sig-auth-leads 5 | labels: 6 | - sig/auth 7 | -------------------------------------------------------------------------------- /sig-docs/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-docs-leads 3 | approvers: 4 | - sig-docs-leads 5 | labels: 6 | - sig/docs 7 | -------------------------------------------------------------------------------- /sig-node/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-node-leads 3 | approvers: 4 | - sig-node-leads 5 | labels: 6 | - sig/node 7 | -------------------------------------------------------------------------------- /contributors/devel/issues.md: -------------------------------------------------------------------------------- 1 | +**NOTE:** This document has moved to [a new location](/contributors/guide/issue-triage.md) 2 | -------------------------------------------------------------------------------- /contributors/devel/pr_workflow.dia: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/pr_workflow.dia -------------------------------------------------------------------------------- /contributors/devel/pr_workflow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/pr_workflow.png -------------------------------------------------------------------------------- /contributors/guide/git_workflow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/guide/git_workflow.png -------------------------------------------------------------------------------- /keps/sig-apps/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-apps-leads 3 | approvers: 4 | - sig-apps-leads 5 | labels: 6 | - sig/apps 7 | -------------------------------------------------------------------------------- /sig-azure/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-azure-leads 3 | approvers: 4 | - sig-azure-leads 5 | labels: 6 | - sig/azure 7 | -------------------------------------------------------------------------------- /sig-vmware/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-vmware-leads 3 | approvers: 4 | - sig-vmware-leads 5 | labels: 6 | - sig/vmware 7 | -------------------------------------------------------------------------------- /wg-kubeadm-adoption/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - wg-kubeadm-adoption-leads 3 | approvers: 4 | - wg-kubeadm-adoption-leads 5 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - michelleN 3 | approvers: 4 | - michelleN 5 | -------------------------------------------------------------------------------- /contributors/devel/arch-roadmap-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/arch-roadmap-1.png -------------------------------------------------------------------------------- /sig-creation-procedure.md: -------------------------------------------------------------------------------- 1 | ## SIG creation procedure 2 | 3 | Moved to [sig governance](/sig-governance.md#sig-creation-procedure) 4 | -------------------------------------------------------------------------------- /sig-network/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-network-leads 3 | approvers: 4 | - sig-network-leads 5 | labels: 6 | - sig/network 7 | -------------------------------------------------------------------------------- /sig-release/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-release-leads 3 | approvers: 4 | - sig-release-leads 5 | labels: 6 | - sig/release 7 | -------------------------------------------------------------------------------- /sig-storage/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-storage-leads 3 | approvers: 4 | - sig-storage-leads 5 | labels: 6 | - sig/storage 7 | -------------------------------------------------------------------------------- /sig-testing/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-testing-leads 3 | approvers: 4 | - sig-testing-leads 5 | labels: 6 | - sig/testing 7 | -------------------------------------------------------------------------------- /sig-windows/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-windows-leads 3 | approvers: 4 | - sig-windows-leads 5 | labels: 6 | - sig/windows 7 | -------------------------------------------------------------------------------- /wg-container-identity/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - wg-container-identity-leads 3 | approvers: 4 | - wg-container-identity-leads 5 | -------------------------------------------------------------------------------- /wg-resource-management/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - wg-resource-management-leads 3 | approvers: 4 | - wg-resource-management-leads 5 | -------------------------------------------------------------------------------- /keps/sig-network/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-network-leads 3 | approvers: 4 | - sig-network-leads 5 | labels: 6 | - sig/network 7 | -------------------------------------------------------------------------------- /sig-big-data/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-big-data-leads 3 | approvers: 4 | - sig-big-data-leads 5 | labels: 6 | - sig/big-data 7 | -------------------------------------------------------------------------------- /sig-storage/1.3-retrospective/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - saad-ali 3 | - EnergyLiYN 4 | approvers: 5 | - saad-ali 6 | - EnergyLiYN 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/aws/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-aws-leads 3 | approvers: 4 | - sig-aws-leads 5 | labels: 6 | - sig/aws 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/cli/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-cli-leads 3 | approvers: 4 | - sig-cli-leads 5 | labels: 6 | - sig/cli 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/gcp/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-gcp-leads 3 | approvers: 4 | - sig-gcp-leads 5 | labels: 6 | - sig/gcp 7 | -------------------------------------------------------------------------------- /sig-openstack/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-openstack-leads 3 | approvers: 4 | - sig-openstack-leads 5 | labels: 6 | - sig/openstack 7 | -------------------------------------------------------------------------------- /committee-steering/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - steering-committee 3 | approvers: 4 | - steering-committee 5 | labels: 6 | - committee/steering 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/apps/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-apps-leads 3 | approvers: 4 | - sig-apps-leads 5 | labels: 6 | - sig/apps 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/auth/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-auth-leads 3 | approvers: 4 | - sig-auth-leads 5 | labels: 6 | - sig/auth 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/node/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-node-leads 3 | approvers: 4 | - sig-node-leads 5 | labels: 6 | - sig/node 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/node/pleg.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/node/pleg.png -------------------------------------------------------------------------------- /generator/testdata/example.md: -------------------------------------------------------------------------------- 1 | Hello! 2 | 3 | Example 4 | custom 5 | content! 6 | 7 | 8 | -------------------------------------------------------------------------------- /sig-autoscaling/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-autoscaling-leads 3 | approvers: 4 | - sig-autoscaling-leads 5 | labels: 6 | - sig/autoscaling 7 | -------------------------------------------------------------------------------- /sig-cluster-ops/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-cluster-ops-leads 3 | approvers: 4 | - sig-cluster-ops-leads 5 | labels: 6 | - sig/cluster-ops 7 | -------------------------------------------------------------------------------- /sig-scalability/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-scalability-leads 3 | approvers: 4 | - sig-scalability-leads 5 | labels: 6 | - sig/scalability 7 | -------------------------------------------------------------------------------- /sig-scheduling/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-scheduling-leads 3 | approvers: 4 | - sig-scheduling-leads 5 | labels: 6 | - sig/scheduling 7 | -------------------------------------------------------------------------------- /contributors/devel/welcome-to-kubernetes-new-developer-guide.md: -------------------------------------------------------------------------------- 1 | This page has moved to: 2 | 3 | https://git.k8s.io/community/contributors/guide/ 4 | -------------------------------------------------------------------------------- /events/2017/12-contributor-summit/schedule.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/events/2017/12-contributor-summit/schedule.png -------------------------------------------------------------------------------- /sig-architecture/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-architecture-leads 3 | approvers: 4 | - sig-architecture-leads 5 | labels: 6 | - sig/architecture 7 | -------------------------------------------------------------------------------- /sig-multicluster/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-multicluster-leads 3 | approvers: 4 | - sig-multicluster-leads 5 | labels: 6 | - sig/multicluster 7 | -------------------------------------------------------------------------------- /Gopkg.toml: -------------------------------------------------------------------------------- 1 | required = ["github.com/client9/misspell/cmd/misspell"] 2 | 3 | [prune] 4 | go-tests = true 5 | unused-packages = true 6 | non-go = true 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/network/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-network-leads 3 | approvers: 4 | - sig-network-leads 5 | labels: 6 | - sig/network 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/node/pod-cache.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/node/pod-cache.png -------------------------------------------------------------------------------- /contributors/design-proposals/release/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-release-leads 3 | approvers: 4 | - sig-release-leads 5 | labels: 6 | - sig/release 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/images/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - bsalamat 3 | - michelleN 4 | approvers: 5 | - bsalamat 6 | - michelleN 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/storage/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-storage-leads 3 | approvers: 4 | - sig-storage-leads 5 | labels: 6 | - sig/storage 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/testing/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-testing-leads 3 | approvers: 4 | - sig-testing-leads 5 | labels: 6 | - sig/testing 7 | -------------------------------------------------------------------------------- /contributors/devel/gubernator-images/skipping1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/gubernator-images/skipping1.png -------------------------------------------------------------------------------- /contributors/devel/gubernator-images/skipping2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/gubernator-images/skipping2.png -------------------------------------------------------------------------------- /sig-api-machinery/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-api-machinery-leads 3 | approvers: 4 | - sig-api-machinery-leads 5 | labels: 6 | - sig/api-machinery 7 | -------------------------------------------------------------------------------- /sig-apps/minutes/README.md: -------------------------------------------------------------------------------- 1 | [Minutes have moved to Google Docs](https://docs.google.com/document/d/1LZLBGW2wRDwAfdBNHJjFfk9CFoyZPcIYGWU7R1PQ3ng/edit#). 2 | -------------------------------------------------------------------------------- /contributors/design-proposals/resource-management/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - wg-resource-management-leads 3 | approvers: 4 | - wg-resource-management-leads 5 | -------------------------------------------------------------------------------- /contributors/devel/gubernator-images/filterpage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/gubernator-images/filterpage.png -------------------------------------------------------------------------------- /contributors/devel/gubernator-images/filterpage1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/gubernator-images/filterpage1.png -------------------------------------------------------------------------------- /contributors/devel/gubernator-images/filterpage2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/gubernator-images/filterpage2.png -------------------------------------------------------------------------------- /contributors/devel/gubernator-images/filterpage3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/gubernator-images/filterpage3.png -------------------------------------------------------------------------------- /sig-product-management/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-product-management-leads 3 | approvers: 4 | - sig-product-management-leads 5 | labels: 6 | - sig/pm 7 | -------------------------------------------------------------------------------- /contributors/devel/adding-an-APIGroup.md: -------------------------------------------------------------------------------- 1 | Adding an API Group 2 | =============== 3 | 4 | Please refer to [api_changes.md](api_changes.md#making-a-new-api-group). 5 | -------------------------------------------------------------------------------- /contributors/devel/gubernator-images/testfailures.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/devel/gubernator-images/testfailures.png -------------------------------------------------------------------------------- /keps/sig-cluster-lifecycle/README.md: -------------------------------------------------------------------------------- 1 | # SIG Cluster Lifecycle KEPs 2 | 3 | This directory contains KEPs related to [SIG Cluster Lifecycle](../../sig-cluster-lifecycle). -------------------------------------------------------------------------------- /sig-instrumentation/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-instrumentation-leads 3 | approvers: 4 | - sig-instrumentation-leads 5 | labels: 6 | - sig/instrumentation 7 | -------------------------------------------------------------------------------- /sig-service-catalog/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-service-catalog-leads 3 | approvers: 4 | - sig-service-catalog-leads 5 | labels: 6 | - sig/service-catalog 7 | -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | sudo: required 2 | 3 | language: bash 4 | 5 | services: 6 | - docker 7 | 8 | script: 9 | - make test-unit 10 | - bash ./scripts/verify.sh 11 | -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-scheduling-leads 3 | approvers: 4 | - sig-scheduling-leads 5 | labels: 6 | - sig/scheduling 7 | -------------------------------------------------------------------------------- /project-managers/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - calebamiles 3 | - idvoretskyi 4 | - grodrigues3 5 | approvers: 6 | - calebamiles 7 | - idvoretskyi 8 | - grodrigues3 9 | -------------------------------------------------------------------------------- /sig-cluster-lifecycle/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-cluster-lifecycle-leads 3 | approvers: 4 | - sig-cluster-lifecycle-leads 5 | labels: 6 | - sig/cluster-lifecycle 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/autoscaling/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-autoscaling-leads 3 | approvers: 4 | - sig-autoscaling-leads 5 | labels: 6 | - sig/autoscaling 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/multicluster/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-multicluster-leads 3 | approvers: 4 | - sig-multicluster-leads 5 | labels: 6 | - sig/multicluster 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/scalability/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-scalability-leads 3 | approvers: 4 | - sig-scalability-leads 5 | labels: 6 | - sig/scalability 7 | -------------------------------------------------------------------------------- /contributors/devel/client-libraries.md: -------------------------------------------------------------------------------- 1 | ## Kubernetes API client libraries 2 | 3 | This document has been moved to https://kubernetes.io/docs/reference/client-libraries/. 4 | -------------------------------------------------------------------------------- /events/2016/developer-summit-2016/k8sDevSummitSchedule.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/events/2016/developer-summit-2016/k8sDevSummitSchedule.pdf -------------------------------------------------------------------------------- /events/2017/12-contributor-summit/feature-roadmap-2018.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/events/2017/12-contributor-summit/feature-roadmap-2018.jpg -------------------------------------------------------------------------------- /keps/sig-cluster-lifecycle/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-cluster-lifecycle-leads 3 | approvers: 4 | - sig-cluster-lifecycle-leads 5 | labels: 6 | - sig/cluster-lifecycle 7 | -------------------------------------------------------------------------------- /mentoring/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - parispittman 3 | approvers: 4 | - parispittman 5 | - sig-contributor-experience-leads 6 | labels: 7 | - sig/contributor-experience 8 | -------------------------------------------------------------------------------- /contributors/design-proposals/api-machinery/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-api-machinery-leads 3 | approvers: 4 | - sig-api-machinery-leads 5 | labels: 6 | - sig/api-machinery 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/auth/kms-grpc-class-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/auth/kms-grpc-class-diagram.png -------------------------------------------------------------------------------- /contributors/design-proposals/storage/volume-snapshotting.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/storage/volume-snapshotting.png -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Kubernetes Community Code of Conduct 2 | 3 | Kubernetes follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). 4 | -------------------------------------------------------------------------------- /contributors/design-proposals/architecture/images/apiserver.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/architecture/images/apiserver.png -------------------------------------------------------------------------------- /contributors/design-proposals/multicluster/ubernetes-design.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/multicluster/ubernetes-design.png -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/images/preemption_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/scheduling/images/preemption_1.png -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/images/preemption_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/scheduling/images/preemption_2.png -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/images/preemption_3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/scheduling/images/preemption_3.png -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/images/preemption_4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/scheduling/images/preemption_4.png -------------------------------------------------------------------------------- /contributors/design-proposals/vault-based-kms-class-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/vault-based-kms-class-diagram.png -------------------------------------------------------------------------------- /contributors/design-proposals/auth/kms-grpc-deployment-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/auth/kms-grpc-deployment-diagram.png -------------------------------------------------------------------------------- /contributors/design-proposals/instrumentation/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-instrumentation-leads 3 | approvers: 4 | - sig-instrumentation-leads 5 | labels: 6 | - sig/instrumentation 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/multicluster/ubernetes-scheduling.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/multicluster/ubernetes-scheduling.png -------------------------------------------------------------------------------- /contributors/design-proposals/resource-management/device-plugin.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/resource-management/device-plugin.png -------------------------------------------------------------------------------- /contributors/design-proposals/scalability/Kubemark_architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/scalability/Kubemark_architecture.png -------------------------------------------------------------------------------- /contributors/design-proposals/service-catalog/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-service-catalog-leads 3 | approvers: 4 | - sig-service-catalog-leads 5 | labels: 6 | - sig/service-catalog 7 | -------------------------------------------------------------------------------- /keps/sig-contributor-experience/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-contributor-experience-leads 3 | approvers: 4 | - sig-contributor-experience-leads 5 | labels: 6 | - sig/contributor-experience -------------------------------------------------------------------------------- /sig-contributor-experience/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-contributor-experience-leads 3 | approvers: 4 | - sig-contributor-experience-leads 5 | labels: 6 | - sig/contributor-experience 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/autoscaling/images/vpa-architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/autoscaling/images/vpa-architecture.png -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-cluster-lifecycle-leads 3 | approvers: 4 | - sig-cluster-lifecycle-leads 5 | labels: 6 | - sig/cluster-lifecycle 7 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/dynamic.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/cluster-lifecycle/clustering/dynamic.png -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/static.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/cluster-lifecycle/clustering/static.png -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/self-hosted-layers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/cluster-lifecycle/self-hosted-layers.png -------------------------------------------------------------------------------- /contributors/design-proposals/multicluster/ubernetes-cluster-state.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/multicluster/ubernetes-cluster-state.png -------------------------------------------------------------------------------- /contributors/design-proposals/storage/volume-topology-scheduling.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/storage/volume-topology-scheduling.png -------------------------------------------------------------------------------- /contributors/design-proposals/scheduling/images/preemption_flowchart.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/scheduling/images/preemption_flowchart.png -------------------------------------------------------------------------------- /contributors/design-proposals/architecture/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-architecture-leads 3 | - jbeda 4 | approvers: 5 | - sig-architecture-leads 6 | - jbeda 7 | labels: 8 | - sig/architecture 9 | -------------------------------------------------------------------------------- /contributors/design-proposals/instrumentation/monitoring_architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/instrumentation/monitoring_architecture.png -------------------------------------------------------------------------------- /contributors/design-proposals/multicluster/federation-high-level-arch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/multicluster/federation-high-level-arch.png -------------------------------------------------------------------------------- /events/2017/05-leadership-summit/session-notes/1345-1430_SIGGOVERNANCE.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/events/2017/05-leadership-summit/session-notes/1345-1430_SIGGOVERNANCE.md -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/self-hosted-final-cluster.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/cluster-lifecycle/self-hosted-final-cluster.png -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/self-hosted-moving-parts.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/cluster-lifecycle/self-hosted-moving-parts.png -------------------------------------------------------------------------------- /contributors/design-proposals/resource-management/device-plugin-overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/resource-management/device-plugin-overview.png -------------------------------------------------------------------------------- /contributors/design-proposals/storage/container-storage-interface_diagram1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/contributors/design-proposals/storage/container-storage-interface_diagram1.png -------------------------------------------------------------------------------- /events/2017/12-contributor-summit/Meeting Room 4ABC - 1st set, Tues fishbowl.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/events/2017/12-contributor-summit/Meeting Room 4ABC - 1st set, Tues fishbowl.PNG -------------------------------------------------------------------------------- /events/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - parispittman 3 | - castrojo 4 | approvers: 5 | - parispittman 6 | - castrojo 7 | - sig-contributor-experience-leads 8 | labels: 9 | - sig/contributor-experience 10 | -------------------------------------------------------------------------------- /contributors/devel/how-to-doc.md: -------------------------------------------------------------------------------- 1 | # Document Conventions 2 | 3 | Updated: 11/3/2017 4 | 5 | *Users and developers who want to write documents for Kubernetes can get started [here](https://github.com/kubernetes/website).* 6 | -------------------------------------------------------------------------------- /events/2017/12-contributor-summit/Meeting Room 6A and 6B - 1st Set, Tues fishbowl.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mikebryant/community/master/events/2017/12-contributor-summit/Meeting Room 6A and 6B - 1st Set, Tues fishbowl.PNG -------------------------------------------------------------------------------- /generator/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - cblecker 3 | - grodrigues3 4 | - jamiehannaford 5 | - spiffxp 6 | approvers: 7 | - cblecker 8 | - grodrigues3 9 | - spiffxp 10 | labels: 11 | - sig/contributor-experience 12 | -------------------------------------------------------------------------------- /sig-cli/migrated-from-wiki/README.md: -------------------------------------------------------------------------------- 1 | The content in here has been migrated from https://github.com/kubernetes/community/wiki and is likely severely out of date. Please contact this SIG if you have questions or ideas about where this content should go. 2 | -------------------------------------------------------------------------------- /sig-docs/migrated-from-wiki/README.md: -------------------------------------------------------------------------------- 1 | The content in here has been migrated from https://github.com/kubernetes/community/wiki and is likely severely out of date. Please contact this SIG if you have questions or ideas about where this content should go. 2 | -------------------------------------------------------------------------------- /contributors/guide/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - castrojo 3 | - guineveresaenger 4 | - idvoretskyi 5 | - tpepper 6 | approvers: 7 | - castrojo 8 | - parispittman 9 | labels: 10 | - sig/contributor-experience 11 | - area/contributor-guide 12 | -------------------------------------------------------------------------------- /OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - calebamiles 3 | - castrojo 4 | - cblecker 5 | - grodrigues3 6 | - idvoretskyi 7 | approvers: 8 | - calebamiles 9 | - castrojo 10 | - cblecker 11 | - grodrigues3 12 | - idvoretskyi 13 | - steering-committee 14 | -------------------------------------------------------------------------------- /sig-cluster-lifecycle/migrated-from-wiki/README.md: -------------------------------------------------------------------------------- 1 | The content in here has been migrated from https://github.com/kubernetes/community/wiki and is likely severely out of date. Please contact this SIG if you have questions or ideas about where this content should go. 2 | -------------------------------------------------------------------------------- /sig-contributor-experience/migrated-from-wiki/README.md: -------------------------------------------------------------------------------- 1 | The content in here has been migrated from https://github.com/kubernetes/community/wiki and is likely severely out of date. Please contact this SIG if you have questions or ideas about where this content should go. 2 | -------------------------------------------------------------------------------- /contributors/design-proposals/multicluster/federated-api-servers.md: -------------------------------------------------------------------------------- 1 | # Federated API Servers 2 | 3 | Moved to [aggregated-api-servers.md](../api-machinery/aggregated-api-servers.md) since cluster 4 | federation stole the word "federation" from this effort and it was very confusing. 5 | -------------------------------------------------------------------------------- /contributors/devel/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - grodrigues3 3 | - Phillels 4 | - idvoretskyi 5 | - calebamiles 6 | - cblecker 7 | - spiffxp 8 | approvers: 9 | - grodrigues3 10 | - Phillels 11 | - idvoretskyi 12 | - calebamiles 13 | - cblecker 14 | - spiffxp 15 | -------------------------------------------------------------------------------- /communication/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - parispittman 3 | - castrojo 4 | - jdumars 5 | - idvoretskyi 6 | approvers: 7 | - castrojo 8 | - parispittman 9 | - sig-contributor-experience-leads 10 | labels: 11 | - sig/contributor-experience 12 | - area/community-management 13 | -------------------------------------------------------------------------------- /keps/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - sig-architecture-leads 3 | - jbeda 4 | - bgrant0607 5 | - jdumars 6 | - calebamiles 7 | - idvoretskyi 8 | approvers: 9 | - sig-architecture-leads 10 | - jbeda 11 | - bgrant0607 12 | - jdumars 13 | - calebamiles 14 | - idvoretskyi 15 | labels: 16 | - sig/architecture 17 | -------------------------------------------------------------------------------- /contributors/new-contributor-playground/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - parispittman 3 | - guineveresaenger 4 | - jberkus 5 | - errordeveloper 6 | - tpepper 7 | - spiffxp 8 | approvers: 9 | - parispittman 10 | - guineveresaenger 11 | - jberkus 12 | - errordeveloper 13 | labels: 14 | - area/new-contributor-track 15 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/high-availability.md: -------------------------------------------------------------------------------- 1 | # High Availability of Scheduling and Controller Components in Kubernetes 2 | 3 | This document is deprecated. For more details about running a highly available 4 | cluster master, please see the [admin instructions document](https://kubernetes.io/docs/admin/high-availability/). 5 | -------------------------------------------------------------------------------- /events/2017/05-leadership-summit/session-notes/readme.md: -------------------------------------------------------------------------------- 1 | **Per the [Template & Instruction Document](https://docs.google.com/document/d/1ncrfiVEy_WELqZaNdYOX0_9uuKzuTikgVC-mz2Izsc4/edit?usp=sharing), 2 | upload your session notes here with the name format**: 3 | 4 | *HHMM-HHMM_SESSIONTITLE.md* 5 | 6 | where HHMM is the time in 24-hour format. 7 | -------------------------------------------------------------------------------- /generator/header.tmpl: -------------------------------------------------------------------------------- 1 | {{- define "header" -}} 2 | 10 | {{- end -}} 11 | -------------------------------------------------------------------------------- /contributors/design-proposals/OWNERS: -------------------------------------------------------------------------------- 1 | reviewers: 2 | - brendandburns 3 | - dchen1107 4 | - jbeda 5 | - lavalamp 6 | - smarterclayton 7 | - thockin 8 | - wojtek-t 9 | - bgrant0607 10 | approvers: 11 | - brendandburns 12 | - dchen1107 13 | - jbeda 14 | - lavalamp 15 | - smarterclayton 16 | - thockin 17 | - wojtek-t 18 | - bgrant0607 19 | labels: 20 | - kind/design 21 | -------------------------------------------------------------------------------- /generator/aliases.tmpl: -------------------------------------------------------------------------------- 1 | aliases: 2 | {{- range .Sigs}} 3 | {{.Dir}}-leads: 4 | {{- range .Leadership.Chairs}} 5 | - {{.GitHub}} 6 | {{- end}} 7 | {{- range .Leadership.TechnicalLeads}} 8 | - {{.GitHub}} 9 | {{- end}} 10 | {{- end}} 11 | {{- range .WorkingGroups}} 12 | {{.Dir}}-leads: 13 | {{- range .Leadership.Chairs}} 14 | - {{.GitHub}} 15 | {{- end}} 16 | {{- end}} 17 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/static.seqdiag: -------------------------------------------------------------------------------- 1 | seqdiag { 2 | activation = none; 3 | 4 | admin[label = "Manual Admin"]; 5 | ca[label = "Manual CA"] 6 | master; 7 | kubelet[stacked]; 8 | 9 | admin => ca [label="create\n- master-cert"]; 10 | admin ->> master [label="start\n- ca-root\n- master-cert"]; 11 | 12 | admin => ca [label="create\n- kubelet-cert"]; 13 | admin ->> kubelet [label="start\n- ca-root\n- kubelet-cert\n- master-location"]; 14 | 15 | kubelet => master [label="register\n- kubelet-location"]; 16 | } 17 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-05-25.md: -------------------------------------------------------------------------------- 1 | # May 25, 2016 2 | 3 | * Intro by Michelle 4 | * Mike Metral from Rackspace demo 5 | * Recursively process configuration files with the -R flag 6 | * Discuss the survey 7 | * Gabe from Deis, Mike from Red Hat, and Doug Davis from IBM are willing to chip in. 8 | * How can we provide Prashanth and pet sets feedback? 9 | * We need some docs on how to use it with some examples (2) that you can copy and paste. 10 | * Lack of examples and docs is a blocker for new k8s feature adoption. 11 | 12 | Watch the [recording](https://vimeo.com/168816241) 13 | -------------------------------------------------------------------------------- /contributors/design-proposals/README.md: -------------------------------------------------------------------------------- 1 | # Kubernetes Design Documents and Proposals 2 | 3 | This directory contains Kubernetes design documents and accepted design proposals. 4 | 5 | For a design overview, please see [the architecture document](architecture/architecture.md). 6 | 7 | Note that a number of these documents are historical and may be out of date or unimplemented. 8 | 9 | TODO: Add the current status to each document and clearly indicate which are up to date. 10 | 11 | TODO: Document the [proposal process](../devel/faster_reviews.md#1-dont-build-a-cathedral-in-one-pr). 12 | -------------------------------------------------------------------------------- /contributors/new-contributor-playground/README.md: -------------------------------------------------------------------------------- 1 | # Welcome to KubeCon Copenhagen's New Contributor Track! 2 | 3 | Hello new contributors! 4 | 5 | This subfolder of kubernetes/community will be used as a safe space for participants in the New Contributor Onboarding Track to familiarize themselves with (some of) the Kubernetes Project's review and pull request processes. 6 | 7 | The label associated with this track is `area/new-contributor-track`. 8 | 9 | *If you are not currently attending or organizing this event, please DO NOT create issues or pull requests against this section of the community repo.* -------------------------------------------------------------------------------- /sig-apps/minutes/2016-07-06.md: -------------------------------------------------------------------------------- 1 | # July 6, 2016 2 | 3 | - Matt Farina gave an introduction and overview of the agenda 4 | - Chris Love gave a demo of his Cassandra cluster 5 | - It was a great example of PetSet in action 6 | - His demo application is located at https://github.com/k8s-for-greeks/gpmr 7 | - Matt Farina gave an update on the analysis of the sig-apps survey 8 | - He will reach out to those interested in helping analyze the data 9 | - It's not too late to volunteer to help. Contact @mattfarina for more. 10 | 11 | 12 | Watch the [recording](https://youtu.be/J-HWkEp8GcA). 13 | -------------------------------------------------------------------------------- /vendor/github.com/client9/misspell/url.go: -------------------------------------------------------------------------------- 1 | package misspell 2 | 3 | import ( 4 | "regexp" 5 | ) 6 | 7 | // Regexp for URL https://mathiasbynens.be/demo/url-regex 8 | // 9 | // original @imme_emosol (54 chars) has trouble with dashes in hostname 10 | // @(https?|ftp)://(-\.)?([^\s/?\.#-]+\.?)+(/[^\s]*)?$@iS 11 | var reURL = regexp.MustCompile(`(?i)(https?|ftp)://(-\.)?([^\s/?\.#]+\.?)+(/[^\s]*)?`) 12 | 13 | // StripURL attemps to replace URLs with blank spaces, e.g. 14 | // "xxx http://foo.com/ yyy -> "xxx yyyy" 15 | func StripURL(s string) string { 16 | return reURL.ReplaceAllStringFunc(s, replaceWithBlanks) 17 | } 18 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # OSX leaves these everywhere on SMB shares 2 | ._* 3 | 4 | # OSX trash 5 | .DS_Store 6 | 7 | # Eclipse files 8 | .classpath 9 | .project 10 | .settings/** 11 | 12 | # Files generated by JetBrains IDEs, e.g. IntelliJ IDEA 13 | .idea/ 14 | *.iml 15 | 16 | # Vscode files 17 | .vscode 18 | 19 | # Emacs save files 20 | *~ 21 | \#*\# 22 | .\#* 23 | 24 | # Vim-related files 25 | [._]*.s[a-w][a-z] 26 | [._]s[a-w][a-z] 27 | *.un~ 28 | Session.vim 29 | .netrwhist 30 | 31 | # JUnit test output from ginkgo e2e tests 32 | /junit*.xml 33 | 34 | # Mercurial files 35 | **/.hg 36 | **/.hg* 37 | 38 | # direnv .envrc files 39 | .envrc 40 | -------------------------------------------------------------------------------- /vendor/gopkg.in/yaml.v2/NOTICE: -------------------------------------------------------------------------------- 1 | Copyright 2011-2016 Canonical Ltd. 2 | 3 | Licensed under the Apache License, Version 2.0 (the "License"); 4 | you may not use this file except in compliance with the License. 5 | You may obtain a copy of the License at 6 | 7 | http://www.apache.org/licenses/LICENSE-2.0 8 | 9 | Unless required by applicable law or agreed to in writing, software 10 | distributed under the License is distributed on an "AS IS" BASIS, 11 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 12 | See the License for the specific language governing permissions and 13 | limitations under the License. 14 | -------------------------------------------------------------------------------- /Makefile: -------------------------------------------------------------------------------- 1 | IMAGE_NAME=golang:1.9 2 | 3 | default: \ 4 | generate \ 5 | 6 | reset-docs: 7 | git checkout HEAD -- ./sig-list.md ./sig-*/README.md ./wg-*/README.md 8 | 9 | generate: 10 | go run ./generator/app.go 11 | 12 | generate-dockerized: 13 | docker run --rm -e WHAT -v $(shell pwd):/go/src/app:Z $(IMAGE_NAME) make -C /go/src/app generate 14 | 15 | verify: 16 | @hack/verify.sh 17 | 18 | test: 19 | go test -v ./generator/... 20 | 21 | test-dockerized: 22 | docker run --rm -v $(shell pwd):/go/src/app:Z $(IMAGE_NAME) make -C /go/src/app test 23 | 24 | .PHONY: default reset-docs generate generate-dockerized verify test test-dockerized 25 | -------------------------------------------------------------------------------- /archive/sig-configuration/README.md: -------------------------------------------------------------------------------- 1 | This group is for discussion about application configuration and deployment in Kubernetes. We use the label `area/app-config-deployment` to tag related issues and pull requests on Github. 2 | 3 | For Kubernetes cluster configuration and deployment, see [SIG-Cluster-Ops](SIG-Cluster-Ops). 4 | 5 | [Google group](https://groups.google.com/forum/#!forum/kubernetes-sig-config) 6 | 7 | [Slack](https://kubernetes.slack.com/messages/sig-configuration/) 8 | 9 | For access to the meeting agenda and notes, please join the Google group. 10 | * [Meeting Agenda and Notes](https://docs.google.com/document/d/1FZ_jiOdBZ_bfPD5Y3QMcfs2SCx956QLc9_E0QdR_l20/edit) 11 | 12 | -------------------------------------------------------------------------------- /Gopkg.lock: -------------------------------------------------------------------------------- 1 | # This file is autogenerated, do not edit; changes may be undone by the next 'dep ensure'. 2 | 3 | 4 | [[projects]] 5 | name = "github.com/client9/misspell" 6 | packages = [ 7 | ".", 8 | "cmd/misspell" 9 | ] 10 | revision = "b90dc15cfd220ecf8bbc9043ecb928cef381f011" 11 | version = "v0.3.4" 12 | 13 | [[projects]] 14 | name = "gopkg.in/yaml.v2" 15 | packages = ["."] 16 | revision = "5420a8b6744d3b0345ab293f6fcba19c978f1183" 17 | version = "v2.2.1" 18 | 19 | [solve-meta] 20 | analyzer-name = "dep" 21 | analyzer-version = 1 22 | inputs-digest = "15876bcf5bae26a3d8ca6af5a0463be3842912808256ce8818c2f34e0b3859fd" 23 | solver-name = "gps-cdcl" 24 | solver-version = 1 25 | -------------------------------------------------------------------------------- /.generated_files: -------------------------------------------------------------------------------- 1 | # Files that should be ignored by tools which do not want to consider generated 2 | # code. 3 | # 4 | # https://git.k8s.io/contrib/mungegithub/mungers/size.go 5 | # 6 | # This file is a series of lines, each of the form: 7 | # 8 | # 9 | # Type can be: 10 | # path - an exact path to a single file 11 | # file-name - an exact leaf filename, regardless of path 12 | # path-prefix - a prefix match on the file path 13 | # file-prefix - a prefix match of the leaf filename (no path) 14 | # paths-from-repo - read a file from the repo and load file paths 15 | # 16 | # For the community repo, there are no autogenerated files that should be skipped by tools and automation. 17 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-07-20.md: -------------------------------------------------------------------------------- 1 | # July 20, 2016 2 | 3 | - Michelle Noorali gave an introduction and overview of the agenda 4 | - Janet Kuo gave an overview of Deployment features 5 | - See her [blog post](http://blog.kubernetes.io/2016/04/using-deployment-objects-with.html ) 6 | - See used [minikube](https://github.com/kubernetes/minikube) for the local cluster set up during her demo 7 | - Saad Ali gave an overview of Volume features and things to look forward to around Volumes 8 | - Check out his [presentation](https://docs.google.com/presentation/d/17w7GqwGE8kO9WPNAO1qC8NyS7dRw_oLBwqKznD9WqUs) 9 | - We are looking forward to the sig-apps survey results next week 10 | 11 | Watch the [recording](https://youtu.be/DrLGxkFdDNc?list=PLI1CvzwXi1cUVsxm2QBIyJgeCkf62ylun). 12 | -------------------------------------------------------------------------------- /vendor/gopkg.in/yaml.v2/writerc.go: -------------------------------------------------------------------------------- 1 | package yaml 2 | 3 | // Set the writer error and return false. 4 | func yaml_emitter_set_writer_error(emitter *yaml_emitter_t, problem string) bool { 5 | emitter.error = yaml_WRITER_ERROR 6 | emitter.problem = problem 7 | return false 8 | } 9 | 10 | // Flush the output buffer. 11 | func yaml_emitter_flush(emitter *yaml_emitter_t) bool { 12 | if emitter.write_handler == nil { 13 | panic("write handler not set") 14 | } 15 | 16 | // Check if the buffer is empty. 17 | if emitter.buffer_pos == 0 { 18 | return true 19 | } 20 | 21 | if err := emitter.write_handler(emitter, emitter.buffer[:emitter.buffer_pos]); err != nil { 22 | return yaml_emitter_set_writer_error(emitter, "write error: "+err.Error()) 23 | } 24 | emitter.buffer_pos = 0 25 | return true 26 | } 27 | -------------------------------------------------------------------------------- /contributors/devel/help-wanted.md: -------------------------------------------------------------------------------- 1 | # Help Wanted 2 | 3 | Items marked with the `help wanted` label need to ensure that they are: 4 | 5 | - Sufficiently actionable: clear description of what should be done 6 | - Tractable for new/casual contributors: there is documentation how that type of change should be made 7 | - Goldilocks priority: Not too high that a core contributor should do it, but not too low that it isn't useful enough for a core contributor to spend time to review it, answer questions, help get it into a release, etc. 8 | - Up to date: Often these issues become obsolete and have already been done, are no longer desirable, no longer make sense, change in priority, change in difficulty, etc. 9 | 10 | Related commands: 11 | 12 | - `/help` : adds the `help wanted` label to an issue 13 | - `/remove-help` : removes the `help wanted` label from an issue -------------------------------------------------------------------------------- /sig-big-data/resources.md: -------------------------------------------------------------------------------- 1 | # Resources 2 | 3 | ### Spark 4 | * [Spark on Kubernetes Design Proposal](https://docs.google.com/document/d/1_bBzOZ8rKiOSjQg78DXOA3ZBIo_KkDJjqxVuq0yXdew/edit#) 5 | * [Spark Dynamic Allocation Proposal](https://docs.google.com/document/d/1S9OMnFaeSf_UUxWpMpvC7ERcWx-jDr2g85MWri3Hccc/edit?usp=sharing) 6 | * [SPARK-JIRA](https://issues.apache.org/jira/browse/SPARK-18278) 7 | * [Kubernetes Issue #34377](https://github.com/kubernetes/kubernetes/issues/34377) 8 | * [External Repository](https://github.com/apache-spark-on-k8s/spark) 9 | 10 | ### HDFS 11 | * [Data Locality Doc](https://docs.google.com/document/d/1TAC6UQDS3M2sin2msFcZ9UBBQFyyz4jFKWw5BM54cQo/edit) 12 | * [External Repository](https://github.com/apache-spark-on-k8s/kubernetes-HDFS) 13 | 14 | ### Airflow 15 | * [Airflow roadmap](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=71013666) 16 | -------------------------------------------------------------------------------- /sig-rktnetes/README.md: -------------------------------------------------------------------------------- 1 | # The Mission 2 | `sig-rktnetes` is focused on topics related to the integration between Kubernetes and the rkt container runtime, more succinctly referred to as "rktnetes". 3 | 4 | This includes: 5 | - Kubernetes and rkt integration 6 | - Performance and scalability 7 | - Images, package management 8 | - Rktnetes deployments 9 | - Issues related to monitoring (cAdvsor, Heapster, etc.) 10 | 11 | The main objective of this SIG is to establish rkt as the go-to/default runtime choice for a Kubernetes cluster. 12 | 13 | # Resources 14 | 15 | [Meeting Notes](https://docs.google.com/document/d/1otDQ2LSubtBUaDfdM8ZcSdWkqRHup4Hqt1VX1jSxh6A/edit?usp=sharing) 16 | 17 | [Zoom Meeting](https://zoom.us/j/830298957) 18 | 19 | [Google Group](https://groups.google.com/forum/#!forum/kubernetes-sig-rktnetes) 20 | 21 | Mailing List: kubernetes-sig-rktnetes@googlegroups.com 22 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-05-18.md: -------------------------------------------------------------------------------- 1 | # May 18, 2016 2 | 3 | * The first SIG Apps meeting 4 | * Intro from Michelle 5 | * Discussion on the future of the SIG: 6 | * Mike from Rackspace offered to do a demo of the recursive functionality ([issue](https://github.com/kubernetes/kubernetes/pull/25110)) 7 | * Idea: solicit the community for cases where their use cases aren't met. 8 | * Demo from Prashanth B on PetSets ([issue](https://github.com/kubernetes/kubernetes/issues/260)) 9 | * Supposed to make deploying and managing stateful apps easier. Will be alpha in 1.3. 10 | * Zookeeper, mysql, cassandra are example apps to run in this 11 | * A group of elements in the identity of a thing. Initially storage and networking (including name) 12 | * Scale up and down is handled differently as well. 13 | * Init containers just went in. Right now most containers start at same time. Init containers let you do one first to initialize the environment. 14 | -------------------------------------------------------------------------------- /contributors/design-proposals/Design_Proposal_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | # 2 | 3 | Status: Pending 4 | 5 | Version: Alpha | Beta | GA 6 | 7 | Implementation Owner: TBD 8 | 9 | ## Motivation 10 | 11 | <2-6 sentences about why this is needed> 12 | 13 | ## Proposal 14 | 15 | <4-6 description of the proposed solution> 16 | 17 | ## User Experience 18 | 19 | ### Use Cases 20 | 21 | <enumerated list of use cases for this feature> 22 | 23 | <in depth description of user experience> 24 | 25 | <*include full examples*> 26 | 27 | ## Implementation 28 | 29 | <in depth description of how the feature will be implemented. in some cases this may be very simple.> 30 | 31 | ### Client/Server Backwards/Forwards compatibility 32 | 33 | <define behavior when using a kubectl client with an older or newer version of the apiserver (+-1 version)> 34 | 35 | ## Alternatives considered 36 | 37 | <short description of alternative solutions to be considered> 38 | 39 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/README.md: -------------------------------------------------------------------------------- 1 | This directory contains diagrams for the clustering design doc. 2 | 3 | This depends on the `seqdiag` [utility](http://blockdiag.com/en/seqdiag/index.html). 4 | Assuming you have a non-borked python install, this should be installable with: 5 | 6 | ```sh 7 | pip install seqdiag 8 | ``` 9 | 10 | Just call `make` to regenerate the diagrams. 11 | 12 | ## Building with Docker 13 | 14 | If you are on a Mac or your pip install is messed up, you can easily build with 15 | docker: 16 | 17 | ```sh 18 | make docker 19 | ``` 20 | 21 | The first run will be slow but things should be fast after that. 22 | 23 | To clean up the docker containers that are created (and other cruft that is left 24 | around) you can run `make docker-clean`. 25 | 26 | ## Automatically rebuild on file changes 27 | 28 | If you have the fswatch utility installed, you can have it monitor the file 29 | system and automatically rebuild when files have changed. Just do a 30 | `make watch`. 31 | 32 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-06-29.md: -------------------------------------------------------------------------------- 1 | # June 29, 2016 2 | 3 | - Bart Spaans gave a demo and talked about [KubeFuse](https://github.com/opencredo/kubefuse) 4 | - Work with your Kubernetes cluster like it's a file system 5 | - You can also edit resources and update them in cluster on writes 6 | - Find more details in this [post](https://opencredo.com/introducing-kubefuse-file-system-kubernetes/) 7 | - Contact Bart on [Twitter](https://twitter.com/Work_of_Bart): @Work_of_Bart 8 | - The DRUD team showed off how they use Kubernetes Jobs 9 | - DRUD is a drupal and wordpress management platform built on Kubernetes 10 | - KubeJobWatcher can be found [here](https://github.com/drud/KubeJobWatcher) 11 | - For help or questions, reach out to Erin at erin@newmediadenver.com 12 | - Matt Farina is looking for people to help analyze the data from the sig-apps survey. Volunteers are welcome to reach out to him on [Twitter](http://twitter.com/mattfarina) or Slack: @mattfarina. 13 | 14 | Watch the [recording](https://youtu.be/6wA_YdgWL8o). 15 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/dynamic.seqdiag: -------------------------------------------------------------------------------- 1 | seqdiag { 2 | activation = none; 3 | 4 | 5 | user[label = "Admin User"]; 6 | bootstrap[label = "Bootstrap API\nEndpoint"]; 7 | master; 8 | kubelet[stacked]; 9 | 10 | user -> bootstrap [label="createCluster", return="cluster ID"]; 11 | user <-- bootstrap [label="returns\n- bootstrap-cluster-uri"]; 12 | 13 | user ->> master [label="start\n- bootstrap-cluster-uri"]; 14 | master => bootstrap [label="setMaster\n- master-location\n- master-ca"]; 15 | 16 | user ->> kubelet [label="start\n- bootstrap-cluster-uri"]; 17 | kubelet => bootstrap [label="get-master", return="returns\n- master-location\n- master-ca"]; 18 | kubelet ->> master [label="signCert\n- unsigned-kubelet-cert", return="returns\n- kubelet-cert"]; 19 | user => master [label="getSignRequests"]; 20 | user => master [label="approveSignRequests"]; 21 | kubelet <<-- master [label="returns\n- kubelet-cert"]; 22 | 23 | kubelet => master [label="register\n- kubelet-location"] 24 | } 25 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/Dockerfile: -------------------------------------------------------------------------------- 1 | # Copyright 2016 The Kubernetes Authors. 2 | # 3 | # Licensed under the Apache License, Version 2.0 (the "License"); 4 | # you may not use this file except in compliance with the License. 5 | # You may obtain a copy of the License at 6 | # 7 | # http://www.apache.org/licenses/LICENSE-2.0 8 | # 9 | # Unless required by applicable law or agreed to in writing, software 10 | # distributed under the License is distributed on an "AS IS" BASIS, 11 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 12 | # See the License for the specific language governing permissions and 13 | # limitations under the License. 14 | 15 | FROM debian:jessie 16 | 17 | RUN apt-get update 18 | RUN apt-get -qy install python-seqdiag make curl 19 | 20 | WORKDIR /diagrams 21 | 22 | RUN curl -sLo DroidSansMono.ttf https://googlefontdirectory.googlecode.com/hg/apache/droidsansmono/DroidSansMono.ttf 23 | 24 | ADD . /diagrams 25 | 26 | CMD bash -c 'make >/dev/stderr && tar cf - *.png' -------------------------------------------------------------------------------- /sig-apps/minutes/2016-06-22.md: -------------------------------------------------------------------------------- 1 | # June 22, 2016 2 | 3 | - Michelle Noorali gave a quick introduction 4 | - Antoine Legrand did a demo of [KPM]((https://github.com/kubespray/kpm) 5 | - Matt Farina gave an update on the SIG-apps survey 6 | - The survey ends this Friday, so there are only two more days to collect data. 7 | - The survey can be found [here](http://goo.gl/forms/VFbJ0fjJYYSEgwND2). 8 | - Please help us share the survey and get as much feedback on running apps in kubernetes as possible! 9 | - If you'd like to help analyze the data, please contact @mattfarina. 10 | - We discussed topics of interest with the group. 11 | - The sig-apps members are interested in seeing some standardization when it comes to deploying, managing, and operating applications in Kubernetes. There was discussion around putting together a post or some documentation about common trends to try to bring them to light. 12 | - There was also interest specifically around how people are actually using Kubernetes Jobs in actuality and seeing real-world examples of that. 13 | -------------------------------------------------------------------------------- /sig-aws/2017_goals.md: -------------------------------------------------------------------------------- 1 | # Kubernetes sig-aws Goals (2017) 2 | 3 | # IAM improvements 4 | * We hope to offer a more seamless integration path to taking advantage of IAM roles in Kubernetes 5 | * We are looking at implementations such as [kube2iam](https://github.com/jtblin/kube2iam) 6 | 7 | ##### Statement 8 | 9 | Kubernetes components now have the ability to take advantage of IAM roles. The process is intuitive and easy. 10 | 11 | # Networking in AWS 12 | * We hope to offer a knowledge base for networking in Kubernetes on AWS 13 | * We will consolidate networking reports and metrics around Kubernetes e2e tests and grow our metric list over time 14 | 15 | ##### Statement 16 | 17 | A user can go to a single public location, and see a side by side comparison of networking avenues in Kubernetes on AWS. 18 | 19 | 20 | # Federation 21 | 22 | * We need to improve and harden our federation support in AWS 23 | 24 | ##### Statement 25 | 26 | 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. 27 | -------------------------------------------------------------------------------- /sig-docs/migrated-from-wiki/roadmap-docs.md: -------------------------------------------------------------------------------- 1 | # Docs and examples roadmap 2 | 3 | If you'd like to help with documentation, please read the [kubernetes.io site instructions](https://git.k8s.io/kubernetes.github.io/README.md). 4 | 5 | If you'd like to contribute an example, please read the [guidelines](https://git.k8s.io/kubernetes/examples/guidelines.md). 6 | 7 | Owners: @kubernetes/docs, @kubernetes/examples 8 | 9 | Labels: [kind/documentation](https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fdocumentation), [kind/example](https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fexample) 10 | 11 | We're currently planning a documentation site overhaul. Join kubernetes-dev@googlegroups.com to gain access to the proposals. 12 | 13 | * [Overhaul proposal](https://docs.google.com/document/d/12Nfj2E8tZL-CMnnpkSH9m5k_oqd4qJh4qDwYDxPGJJI/edit?ts=5705b1fc#) 14 | * [Mocks](https://docs.google.com/presentation/d/14mJwJGlwBJHIpMRGR-nYMSyyNk-kRpabyz74-YYXeTo/edit#slide=id.g12d21f53ed_2_11) 15 | * [API documentation improvements](https://github.com/kubernetes/kubernetes/issues/19680) -------------------------------------------------------------------------------- /generator/testdata/no_custom_content.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see generator/README.md. 8 | --> 9 | # Auth SIG 10 | 11 | Covers improvements to Kubernetes authorization, authentication, and cluster security policy. 12 | 13 | ## Meetings 14 | * [Wednesdays at 18:00 UTC](https://zoom.us/my/k8s.sig.auth) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=18:00&tz=UTC). 15 | 16 | Meeting notes and Agenda can be found [here](https://docs.google.com/document/d/1woLGRoONE3EBVx-wTb4pvp4CI7tmLZ6lS26VTbosLKM/edit#). 17 | 18 | ## Leads 19 | * [Eric Chiang](https://github.com/ericchiang), CoreOS 20 | * [Jordan Liggitt](https://github.com/liggitt), Red Hat 21 | * [David Eads](https://github.com/deads2k), Red Hat 22 | 23 | ## Contact 24 | * [Slack](https://kubernetes.slack.com/messages/sig-auth) 25 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-auth) 26 | 27 | <!-- BEGIN CUSTOM CONTENT --> 28 | 29 | <!-- END CUSTOM CONTENT --> 30 | -------------------------------------------------------------------------------- /generator/testdata/custom_content.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see generator/README.md. 8 | --> 9 | # Auth SIG 10 | 11 | Covers improvements to Kubernetes authorization, authentication, and cluster security policy. 12 | 13 | ## Meetings 14 | * [Wednesdays at 18:00 UTC](https://zoom.us/my/k8s.sig.auth) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=18:00&tz=UTC). 15 | 16 | Meeting notes and Agenda can be found [here](https://docs.google.com/document/d/1woLGRoONE3EBVx-wTb4pvp4CI7tmLZ6lS26VTbosLKM/edit#). 17 | 18 | ## Leads 19 | * [Eric Chiang](https://github.com/ericchiang), CoreOS 20 | * [Jordan Liggitt](https://github.com/liggitt), Red Hat 21 | * [David Eads](https://github.com/deads2k), Red Hat 22 | 23 | ## Contact 24 | * [Slack](https://kubernetes.slack.com/messages/sig-auth) 25 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-auth) 26 | 27 | <!-- BEGIN CUSTOM CONTENT --> 28 | FOO BAR BAZ 29 | <!-- END CUSTOM CONTENT --> 30 | -------------------------------------------------------------------------------- /vendor/github.com/client9/misspell/LICENSE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2015-2017 Nick Galbreath 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | 23 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-06-15.md: -------------------------------------------------------------------------------- 1 | # June 15, 2016 2 | 3 | - Michelle Noorali gave an introduction 4 | - Ben Hall, founder of katacoda, did a demo of [katacoda](https://www.katacoda.com/) 5 | - Katacoda is an interactive learning platform for software engineers. 6 | - Ben showed off the current lessons on Kubernetes which are available now. 7 | - Ben also talked about how companies/people can make their own interactive lessons and embed them. 8 | - Contact Ben on [Twitter](https://twitter.com/Ben_Hall): @Ben_Hall 9 | - Eric Chiang demoed new Role Based Access Control features and capability in Kubernetes 1.3. 10 | - This demo was extensive and very helpful! Check out the [recording](https://www.youtube.com/watch?v=97VMYjfjWyg&list=PLI1CvzwXi1cUVsxm2QBIyJgeCkf62ylun&index=2) for the full scoop. 11 | - You can find the demo script/setup/example from the meeting in Eric's github repo [here](https://github.com/ericchiang/coreos-kubernetes/tree/sig-apps-demo/single-node). 12 | - Michelle Noorali shared the sig-apps survey which can be found [here](http://goo.gl/forms/n7vcisBv3l9IuTQr1). 13 | 14 | Watch the [recording](https://www.youtube.com/watch?v=97VMYjfjWyg&list=PLI1CvzwXi1cUVsxm2QBIyJgeCkf62ylun&index=2). 15 | -------------------------------------------------------------------------------- /wg-cluster-api/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Cluster API Working Group 10 | 11 | Define a portable API that represents a Kubernetes cluster. The API will contain the control plane and its configuration and the underlying infrastructure (nodes, node pools, etc). 12 | 13 | ## Meetings 14 | * Regular WG Meeting: [s at ]() (). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=&tz=). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/16ils69KImmE94RlmzjWDrkmFZysgB2J4lGnYMRN89WM/edit). 16 | 17 | ## Organizers 18 | 19 | * Kris Nova (**[@kris-nova](https://github.com/kris-nova)**), Heptio 20 | * Robert Bailey (**[@roberthbailey](https://github.com/roberthbailey)**), Google 21 | 22 | ## Contact 23 | * [Slack](https://kubernetes.slack.com/messages/cluster-api) 24 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle) 25 | 26 | <!-- BEGIN CUSTOM CONTENT --> 27 | 28 | <!-- END CUSTOM CONTENT --> 29 | -------------------------------------------------------------------------------- /sig-aws/kubernetes-on-aws.md: -------------------------------------------------------------------------------- 1 | Kubernetes on Amazon Web Services 2 | ==== 3 | 4 | This page lists different options, in alphabetic order, of starting a Kubernetes cluster on Amazon Web Services. 5 | 6 | * Clocker: http://www.clocker.io/tutorials/kubernetes-cluster.html 7 | * Heptio: https://github.com/aws-quickstart/quickstart-heptio 8 | * Juju Charms: https://jujucharms.com/canonical-kubernetes/ 9 | * KAT - Kubernetes cluster on AWS with Terraform: https://github.com/xuwang/kube-aws-terraform 10 | * Kargo: https://github.com/kubernetes-incubator/kargo 11 | * Kismatic Enterprise Toolkit: https://github.com/apprenda/kismatic 12 | * Kraken 2: https://github.com/samsung-cnct/k2 13 | * kube-aws: https://github.com/kubernetes-incubator/kube-aws 14 | * Kubeadm Quickstart: https://github.com/upmc-enterprises/kubeadm-aws 15 | * Kubernetes on AWS: https://github.com/zalando-incubator/kubernetes-on-aws/ 16 | * Kubernetes Operations (kops): https://github.com/kubernetes/kops 17 | * OpenShift: https://access.redhat.com/articles/2623521 18 | * Stackpoint.io: https://stackpoint.io 19 | * Tack: https://github.com/kz8s/tack 20 | * Tectonic: http://github.com/coreos/tectonic-installer 21 | * Weaveworks AMI: https://github.com/weaveworks/kubernetes-ami 22 | -------------------------------------------------------------------------------- /wg-apply/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Apply Working Group 10 | 11 | Improve the state of declarative object management by fixing `kubectl apply`, moving the logic from the client to the server. This move also enables new/fixed features included in the scope of this working-group: diff, dry-run and prune. 12 | Resources can be found in [this Google drive folder](https://drive.google.com/drive/folders/1wlpgkS2gFZXdp4x2WlRsfUBxkFlt2Gx0) 13 | 14 | ## Meetings 15 | * Regular WG Meeting: [Tuesdays at 9:30 PT (Pacific Time)](https://zoom.us/my/apimachinery) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:30&tz=PT%20%28Pacific%20Time%29). 16 | 17 | ## Organizers 18 | 19 | * Daniel Smith (**[@lavalamp](https://github.com/lavalamp)**), Google 20 | 21 | ## Contact 22 | * [Slack](https://kubernetes.slack.com/messages/wg-apply) 23 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-apply) 24 | 25 | <!-- BEGIN CUSTOM CONTENT --> 26 | 27 | <!-- END CUSTOM CONTENT --> 28 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-07-13.md: -------------------------------------------------------------------------------- 1 | # July 13, 2016 2 | 3 | - Michelle Noorali gave an introduction and overview of the agenda 4 | - Christian Simon from JetStack gave a demo of [Kube-Lego](https://github.com/jetstack/kube-lego) 5 | - Kube-Lego automatically requests certificates for Kubernetes Ingress resources Let's Encrypt 6 | - Here are the [slides](https://docs.google.com/presentation/d/1t9FhmkGjchBmVzIlbGdfj_aSHcIRdg9qxBtIWIWdbnY/edit?usp=sharing) 7 | - Matt Farina gave an update on the analysis of the sig-apps survey 8 | - He has formed a team and should have results from the survey soon 9 | - A blog post with the results will follow 10 | - Clayton Coleman called to attention that there are many open discussions on PetSet 11 | - Now is the time to get involved in key decision making conversations especially if you have already implemented a PetSet 12 | - Follow along in the ["Pet Set in Beta" issue (#28718)](https://github.com/kubernetes/kubernetes/issues/28718#issuecomment-233291118) which also points to other relevant PetSet topics. 13 | - This is the issue for [Pet Set upgrades (#28706)](https://github.com/kubernetes/kubernetes/issues/28706#issuecomment-232831791) 14 | 15 | 16 | Watch the [recording](https://youtu.be/Cktqa_44DHs?list=PLI1CvzwXi1cUVsxm2QBIyJgeCkf62ylun). 17 | -------------------------------------------------------------------------------- /events/elections/2017/RESULTS.md: -------------------------------------------------------------------------------- 1 | # Results of the 2017 Steering Committee Election 2 | 3 | Number of seats open: 3 (2 year term), 3 (1 year term) 4 | 5 | Number of eligible voters: 392 6 | 7 | Number of votes cast: 309 8 | 9 | Turnout: 78.8% 10 | 11 | [Raw ballot data](BALLOTS.csv) 12 | 13 | ## Results 14 | 15 | The final ranking, using the "Schulze" Condorcet completion, is as follows: 16 | 17 | 1. Derek Carr 18 | 2. Michelle Noorali 19 | 3. Phillip Wittrock 20 | 4. Michael Rubin 21 | 5. Timothy St. Clair 22 | 6. Quinton Hoole 23 | 7. Aaron Crickenberger 24 | 8. Caleb Miles 25 | 9. Jaice Singer DuMars 26 | 10. Kris Nova 27 | 11. Justin Santa Barbara 28 | 12. Alex Pollitt 29 | 13. Sebastien Goasguen 30 | 14. Ihor Dvoretskyi 31 | 15. Adnan Abdulhussein 32 | 16. Ilya Dmitrichenko 33 | 17. Matt Farina 34 | 18. Aaron Schlesinger 35 | 19. Rob Hirschfeld 36 | 20. Doug Davis 37 | 38 | According to the limits on company representation, Google would be 39 | over-represented with this result, so Michael Rubin must be excluded. 40 | 41 | ## Winners 42 | 43 | The winners of the open seats are as follows: 44 | 45 | Two year term: 46 | 1. Derek Carr 47 | 2. Michelle Noorali 48 | 3. Phillip Wittrock 49 | 50 | One year term: 51 | 1. Timothy St. Clair 52 | 2. Quinton Hoole 53 | 3. Aaron Crickenberger 54 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to the Community Repo 2 | 3 | Welcome to the Kubernetes Community contributing guide. We are excited about the prospect of you joining our [community](https://github.com/kubernetes/community)! 4 | 5 | ## Getting Started 6 | 7 | We have full documentation on how to get started contributing here: 8 | 9 | - [Kubernetes Contributor Guide](http://git.k8s.io/community/contributors/guide) - Main contributor documentation 10 | - [Contributor Cheat Sheet](https://git.k8s.io/community/contributors/guide/contributor-cheatsheet.md) - Common resources for existing developers 11 | 12 | ## Mentorship 13 | 14 | - [Mentoring Initiatives](https://git.k8s.io/community/mentoring) - We have a diverse set of mentorship programs available that are always looking for volunteers! 15 | 16 | ## Contributing to Individual SIGs 17 | 18 | Each SIG may or may not have it's own policies for editing their section of this repository. 19 | 20 | Edits in SIG sub-directories should follow any additional guidelines described 21 | by the respective SIG leads in the sub-directory's `CONTRIBUTING` file 22 | (e.g. [sig-cli/CONTRIBUTING](sig-cli/CONTRIBUTING.md)). 23 | 24 | Attending a [SIG meeting](/sig-list.md) or posting on their mailing list might be prudent if you want to make extensive contributions. 25 | 26 | -------------------------------------------------------------------------------- /mentoring/the1-on-1hour.md: -------------------------------------------------------------------------------- 1 | The 1:1 Hour 2 | ======= 3 | 4 | One mentor. One mentee. One Hour. 5 | 6 | In this mentorship opportunity, you'll be paired with someone in the ecosystem that can help drive your upstream Kubernetes experience forward with a quick burst of information. The mentee controls the content that will be served during that hour. This is open for new AND current contributors of all [levels](/community-membership.md). 7 | 8 | Activities that you can select from include: 9 | * pair programming 10 | * live code review how-to (for those wishing to be a reviewer or be a better reviewer) 11 | * live docs review how-to 12 | * live code review of a proposed solution you are working on 13 | * codebase tour of a certain area 14 | * guidance on your contributor path (advice on becoming an approver, etc.) 15 | * AMA session (ask anything!) 16 | 17 | We will attempt to match you with the closest mentor of your area of interested or activity. 18 | 19 | ## Sign up! 20 | [Fill out this form](https://goo.gl/forms/9WllkPFTRB999vcc2) and we'll be in touch! 21 | 22 | ## Mentors 23 | 24 | If you are interested in signing up to be a mentor for this, please see the [mentor guidelines](mentorguidelines.md). 25 | 26 | ### Notes 27 | Please pardon our dust as we build out the process for this and recruit more mentors. 28 | 29 | -------------------------------------------------------------------------------- /wg-cloud-provider/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Cloud Provider Working Group 10 | 11 | Charter can be found [here](https://docs.google.com/document/d/1m4Kvnh_u_9cENEE9n1ifYowQEFSgiHnbw43urGJMB64/edit#) 12 | 13 | ## Meetings 14 | * Regular WG Meeting: [Wednesdays at 10:00 PT (Pacific Time)](https://zoom.us/my/cloudprovider) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=10:00&tz=PT%20%28Pacific%20Time%29). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1OZE-ub-v6B8y-GuaWejL-vU_f9jsjBbrim4LtTfxssw/edit#heading=h.w7i4ksrweimp). 16 | 17 | ## Organizers 18 | 19 | * Sidhartha Mani (**[@wlan0](https://github.com/wlan0)**), Caascade Labs 20 | * Jago Macleod (**[@jagosan](https://github.com/jagosan)**), Google 21 | 22 | ## Contact 23 | * [Slack](https://kubernetes.slack.com/messages/wg-cloud-provider) 24 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-cloud-provider) 25 | * [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fcloud-provider) 26 | 27 | <!-- BEGIN CUSTOM CONTENT --> 28 | 29 | <!-- END CUSTOM CONTENT --> 30 | -------------------------------------------------------------------------------- /wg-container-identity/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Container Identity Working Group 10 | 11 | Ensure containers are able to interact with external systems and acquire secure identities for communication, integrating with external solutions as necessary. 12 | 13 | ## Meetings 14 | * Regular WG Meeting: [Tuesdays at 15:00 UTC](TBD) (bi-weekly (On demand)). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=15:00&tz=UTC). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1uH60pNr1-jBn7N2pEcddk6-6NTnmV5qepwKUJe9tMRo/edit). 16 | 17 | ## Organizers 18 | 19 | * Clayton Coleman (**[@smarterclayton](https://github.com/smarterclayton)**), Red Hat 20 | * Greg Castle (**[@destijl](https://github.com/destijl)**), Google 21 | 22 | ## Contact 23 | * [Slack](https://kubernetes.slack.com/messages/wg-container-identity) 24 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-container-identity) 25 | 26 | <!-- BEGIN CUSTOM CONTENT --> 27 | The working group proposal can be found [here](https://docs.google.com/document/d/1bCK-1_Zy2WfsrMBJkdaV72d2hidaxZBhS5YQHAgscPI/edit). 28 | 29 | <!-- END CUSTOM CONTENT --> 30 | -------------------------------------------------------------------------------- /wg-multitenancy/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Multitenancy Working Group 10 | 11 | Define the models of multitenancy that Kubernetes will support. Discuss and execute upon any remaining work that needs to be done to support these models. Create conformance tests that will prove that these models can be built and used in production environments. 12 | 13 | ## Meetings 14 | * Regular WG Meeting: [Wednesdays at 11:00 PT (Pacific Time)](https://zoom.us/my/k8s.sig.auth) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1fj3yzmeU2eU8ZNBCUJG97dk_wC7228-e_MmdcmTNrZY/edit?usp=sharing). 16 | 17 | ## Organizers 18 | 19 | * David Oppenheimer (**[@davidopp](https://github.com/davidopp)**), Google 20 | * Jessie Frazelle (**[@jessfraz](https://github.com/jessfraz)**), Microsoft 21 | 22 | ## Contact 23 | * [Slack](https://kubernetes.slack.com/messages/wg-multitenancy) 24 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy) 25 | 26 | <!-- BEGIN CUSTOM CONTENT --> 27 | 28 | <!-- END CUSTOM CONTENT --> 29 | -------------------------------------------------------------------------------- /sig-vmware/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # VMware Special Interest Group 10 | 11 | Bring together members of the VMware and Kubernetes community to maintain, support and run Kubernetes on VMware platforms. 12 | 13 | ## Meetings 14 | * Regular SIG Meeting: [Thursdays at 18:00 UTC](https://zoom.us/j/183662780) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=18:00&tz=UTC). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1RV0nVtlPoAtM0DQwNYxYCC9lHfiHpTNatyv4bek6XtA/edit?usp=sharing). 16 | 17 | ## Leadership 18 | 19 | ### Chairs 20 | The Chairs of the SIG run operations and processes governing the SIG. 21 | 22 | * Fabio Rapposelli (**[@frapposelli](https://github.com/frapposelli)**), VMware 23 | * Steve Wong (**[@cantbewong](https://github.com/cantbewong)**), VMware 24 | 25 | ## Contact 26 | * [Slack](https://kubernetes.slack.com/messages/sig-vmware) 27 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-vmware) 28 | * [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fvmware) 29 | 30 | <!-- BEGIN CUSTOM CONTENT --> 31 | 32 | <!-- END CUSTOM CONTENT --> 33 | -------------------------------------------------------------------------------- /sig-architecture/backlog.md: -------------------------------------------------------------------------------- 1 | # Backlog 2 | 3 | ## Processes 4 | 5 | * KEP process rollout and iteration 6 | * New repo process 7 | * [API review process](https://github.com/kubernetes/community/pull/419/files) 8 | * Conformance test suite change review process 9 | * Escalation process 10 | * [Branching policy](https://github.com/kubernetes/community/issues/566) 11 | 12 | ## SIG-related 13 | 14 | * Improve charter to meet expectations of Steering Committee 15 | * Clarify criteria for areas out of scope for the SIG 16 | * Formalize decision processes 17 | * Identify subprojects/subefforts 18 | * Determine initial reviewers and approvers 19 | * How are SIG leads chosen 20 | 21 | ## Documentation 22 | 23 | * Update What Is Kubernetes on the web site 24 | * [Architectural diagram](https://github.com/kubernetes/community/issues/767) 25 | * Document who owns client library, build, and release artifacts 26 | * Document who owns conformance definition, profiles, etc. 27 | * Document [design decisions](https://docs.google.com/document/d/1D_OlIZRSieMNPQaq2PNrh5Ax7EwXNjmGfKIWiofJ6jY/edit#) 28 | * Overall extension strategy 29 | 30 | ## Major technical issues and conventions 31 | 32 | * [Multi-repo plan and roadmap](https://github.com/kubernetes/kubernetes/issues/24343) 33 | * ["v2 API" plan](https://github.com/kubernetes/kubernetes/issues/8190) 34 | * [Architectural layers](https://github.com/kubernetes/community/issues/952) 35 | -------------------------------------------------------------------------------- /contributors/design-proposals/cluster-lifecycle/clustering/Makefile: -------------------------------------------------------------------------------- 1 | # Copyright 2016 The Kubernetes Authors. 2 | # 3 | # Licensed under the Apache License, Version 2.0 (the "License"); 4 | # you may not use this file except in compliance with the License. 5 | # You may obtain a copy of the License at 6 | # 7 | # http://www.apache.org/licenses/LICENSE-2.0 8 | # 9 | # Unless required by applicable law or agreed to in writing, software 10 | # distributed under the License is distributed on an "AS IS" BASIS, 11 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 12 | # See the License for the specific language governing permissions and 13 | # limitations under the License. 14 | 15 | FONT := DroidSansMono.ttf 16 | 17 | PNGS := $(patsubst %.seqdiag,%.png,$(wildcard *.seqdiag)) 18 | 19 | .PHONY: all 20 | all: $(PNGS) 21 | 22 | .PHONY: watch 23 | watch: 24 | fswatch *.seqdiag | xargs -n 1 sh -c "make || true" 25 | 26 | $(FONT): 27 | curl -sLo $@ https://googlefontdirectory.googlecode.com/hg/apache/droidsansmono/$(FONT) 28 | 29 | %.png: %.seqdiag $(FONT) 30 | seqdiag --no-transparency -a -f '$(FONT)' $< 31 | 32 | # Build the stuff via a docker image 33 | .PHONY: docker 34 | docker: 35 | docker build -t clustering-seqdiag . 36 | docker run --rm clustering-seqdiag | tar xvf - 37 | 38 | .PHONY: docker-clean 39 | docker-clean: 40 | docker rmi clustering-seqdiag || true 41 | docker images -q --filter "dangling=true" | xargs docker rmi 42 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-08-03.md: -------------------------------------------------------------------------------- 1 | # August 03, 2016 2 | 3 | * Intro by Michelle 4 | * [Ryan J](https://twitter.com/ryanj?lang=en) talked about "Defining Applications in Kubernetes(and Openshift). 5 | * His presentation can be found [here](bit.ly/sig-apps-openshift) and includes lots of helpful links. 6 | * He went through some OpenShift primitives that are not in Kubernetes but may show up soon if the community sees a need. 7 | * There was some in depth discussion about Deployments. 8 | * Kubernetes has some concepts that came out of OpenShift Deployment Config. 9 | * Q: What features are in Deployment Config that are high priority to push into Kubernetes Core at the moment? 10 | A: _(Clayton)_ Yes. Handling deployment failures at a high level, a generic idea for a trigger controller which watches another system for changes and makes updates to a Deployment, and hooks. 11 | * Ryan showed off OC which is a command line tool which is a wrapper for kubectl 12 | * Comment: One of the challenges Kubernetes faces today is that there is not a great way to extensibly pull in new chunks of APIs. 13 | * This is something that is actively being worked on today. This work is being discussed and worked on in [SIG-API-Machinery](/sig-api-machinery) 14 | * Free O'Reilly EBooks can be found [here](http://gist-reveal.it/4ca683dff6cdb9601c495e27d4bb5289#/oreilly-ebooks) courtesy of Red Hat. 15 | 16 | 17 | Watch the [recording](https://youtu.be/8Gn44O6hSCw) 18 | -------------------------------------------------------------------------------- /vendor/gopkg.in/yaml.v2/LICENSE.libyaml: -------------------------------------------------------------------------------- 1 | The following files were ported to Go from C files of libyaml, and thus 2 | are still covered by their original copyright and license: 3 | 4 | apic.go 5 | emitterc.go 6 | parserc.go 7 | readerc.go 8 | scannerc.go 9 | writerc.go 10 | yamlh.go 11 | yamlprivateh.go 12 | 13 | Copyright (c) 2006 Kirill Simonov 14 | 15 | Permission is hereby granted, free of charge, to any person obtaining a copy of 16 | this software and associated documentation files (the "Software"), to deal in 17 | the Software without restriction, including without limitation the rights to 18 | use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies 19 | of the Software, and to permit persons to whom the Software is furnished to do 20 | so, subject to the following conditions: 21 | 22 | The above copyright notice and this permission notice shall be included in all 23 | copies or substantial portions of the Software. 24 | 25 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 26 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 27 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 28 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 29 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 30 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 31 | SOFTWARE. 32 | -------------------------------------------------------------------------------- /mentoring/mentoring-events.md: -------------------------------------------------------------------------------- 1 | # Mentoring Activities at Events 2 | 3 | During events like KubeCon and other related events that arise, there will be the opportunity for mentoring activities. This doc will list those and their respective details. The KubeCon events are run by CNCF/LF and not Contributor Experience although we may advise and members could help out. 4 | 5 | --- 6 | 7 | CNCF is hosting another speed networking and mentoring session during [KubeCon + CloudNativeCon Europe 2018](https://events.linuxfoundation.org/kubecon-eu-2018/). 8 | Speed Networking & Mentoring Event Details: 9 | Date: Wednesday, May 2 10 | Time: 15:40 - 17:00 11 | Location: Meeting Rooms 18 & 19 12 | Registration: Complimentary - pre-registration required 13 | 14 | Please help spread the word by encouraging KubeCon attendees to sign up for the free session. Pre-registration for this session is required - so fill out the [MENTOR](https://docs.google.com/forms/d/e/1FAIpQLSe6eClecYb4ZXWPpWDrk7FIqh6qPQPLLnXk9hSqC0b46sXO9Q/viewform) or [MENTEE](https://docs.google.com/forms/d/e/1FAIpQLSdxjqDS59NE1mi42JHDvHngSxBS4lGDDZzmXOLDO7nBawFhJw/viewform) forms today. 15 | 16 | The session is for those who are new or not so new to the community. Mentees are paired with mentors from across the community and CNCF projects and have the opportunity to explore growing a cloud native career, getting more involved in the ecosystem or working with new, emerging projects in areas like networking or service meshes. -------------------------------------------------------------------------------- /hack/verify-spelling.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | 3 | # Copyright 2018 The Kubernetes Authors. 4 | # 5 | # Licensed under the Apache License, Version 2.0 (the "License"); 6 | # you may not use this file except in compliance with the License. 7 | # You may obtain a copy of the License at 8 | # 9 | # http://www.apache.org/licenses/LICENSE-2.0 10 | # 11 | # Unless required by applicable law or agreed to in writing, software 12 | # distributed under the License is distributed on an "AS IS" BASIS, 13 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 14 | # See the License for the specific language governing permissions and 15 | # limitations under the License. 16 | 17 | set -o errexit 18 | set -o nounset 19 | set -o pipefail 20 | 21 | export KUBE_ROOT=$(dirname "${BASH_SOURCE}")/.. 22 | 23 | # Install tools we need, but only from vendor/... 24 | cd ${KUBE_ROOT} 25 | go install ./vendor/github.com/client9/misspell/cmd/misspell 26 | if ! which misspell >/dev/null 2>&1; then 27 | echo "Can't find misspell - is your GOPATH 'bin' in your PATH?" >&2 28 | echo " GOPATH: ${GOPATH}" >&2 29 | echo " PATH: ${PATH}" >&2 30 | exit 1 31 | fi 32 | 33 | # Spell checking 34 | # All the skipping files are defined in hack/.spelling_failures 35 | skipping_file="${KUBE_ROOT}/hack/.spelling_failures" 36 | failing_packages=$(echo `cat ${skipping_file}` | sed "s| | -e |g") 37 | git ls-files | grep -v -e ${failing_packages} | xargs misspell -i "" -error -o stderr 38 | -------------------------------------------------------------------------------- /events/elections/2017/aaroncrickenberger_bio.md: -------------------------------------------------------------------------------- 1 | # Aaron Crickenberger 2 | 3 | I can be reached as [@spiffxp](https://github.com/spiffxp) on github, slack, gmail, linkedin, twitter, soundcloud, etc 4 | 5 | ## What I've done 6 | 7 | I have been involved in open source projects since 2007, cloud related projects since 2009, and Kubernetes since 2015. 8 | 9 | I co-founded SIG Testing. I actively contribute in SIG Contributor Experience, Release, Scale. If you attend the weekly Kubernetes Community meetings, chances are you've seen me (or at least my beard.) 10 | 11 | I have participated in every Kubernetes release since v1.4. I drafted release notes for [v1.4](https://github.com/kubernetes/kubernetes/pull/33410) and [v1.5](https://github.com/kubernetes/features/pull/140). I am a member of of the [v1.8 release team](https://github.com/kubernetes/features/blob/master/release-1.8/release_team.md). 12 | 13 | I helped found [the kubernetes/community repo](https://github.com/kubernetes/community/pull/3). 14 | 15 | ## What I'll do 16 | 17 | [The same thing we do every night Pinky...](https://www.youtube.com/watch?v=XJYmyYzuTa8) 18 | 19 | I will advocate for transparency and accountability in our decision making process. I will strive for simplicity and human-sized solutions to large-scale problems where possible. I will continue to push for community empowerment and ownership of key project responsibilities. Narf. 20 | 21 | ## Where I work 22 | 23 | Samsung SDS, as part of the [Cloud Native Computing Team](https://samsung-cnct.github.io) 24 | -------------------------------------------------------------------------------- /wg-app-def/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # App Def Working Group 10 | 11 | Improve UX of declarative primitives in the API and/or primary client libraries and tools, understand the needs of other parts of the ecosystem on this layer, and improve the interoperability of application management tools through better separation of concerns, common conventions, and common principles. 12 | Charter can be found [here](https://docs.google.com/document/d/1TzRwzWYRulx4o8Fii8k7ToIx4LR4MSncxxLdJ9TkOAs/edit#) 13 | 14 | ## Meetings 15 | * Regular WG Meeting: [Wednesdays at 16:00 UTC](https://zoom.us/j/748123863) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:00&tz=UTC). 16 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1Pxc-qwAt4FvuISZ_Ib5KdUwlynFkGueuzPx5Je_lbGM/edit). 17 | 18 | ## Organizers 19 | 20 | * Antoine Legrand (**[@ant31](https://github.com/ant31)**), CoreOS 21 | * Bryan Liles (**[@bryanl](https://github.com/bryanl)**), Heptio 22 | * Gareth Rushgrove (**[@garethr](https://github.com/garethr)**), Docker 23 | 24 | ## Contact 25 | * [Slack](https://kubernetes.slack.com/messages/wg-app-def) 26 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-app-def) 27 | 28 | <!-- BEGIN CUSTOM CONTENT --> 29 | 30 | <!-- END CUSTOM CONTENT --> 31 | -------------------------------------------------------------------------------- /wg-kubeadm-adoption/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Kubeadm Adoption Working Group 10 | 11 | Boost adoption of the kubeadm tool. kubeadm is a tool for creating new Kubernetes clusters easily for new users, but can also be used as a toolbox for higher-level deployment solutions. This working group makes sure kubeadm meets the extensibility requirements of those higher-level Kubernetes installers. 12 | 13 | ## Meetings 14 | * Regular WG Meeting: [Tuesdays at 18:00 UTC](https://zoom.us/j/166836%E2%80%8B624) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=18:00&tz=UTC). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1KdXsLYiJYJdiRbtgZsx6qbHF4g_K-gAScB9Zs4avgzg/edit). 16 | * [Meeting recordings](https://www.youtube.com/watch?v=-Xlcrm5iT80&list=PLPgAK4Icr0ehh93BiMC3djAc5KoW7WIkl). 17 | 18 | ## Organizers 19 | 20 | * Lucas Käldström (**[@luxas](https://github.com/luxas)**), Luxas Labs (occasionally contracting for Weaveworks) 21 | * Justin Santa Barbara (**[@justinsb](https://github.com/justinsb)**) 22 | 23 | ## Contact 24 | * [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle) 25 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle) 26 | 27 | <!-- BEGIN CUSTOM CONTENT --> 28 | 29 | <!-- END CUSTOM CONTENT --> 30 | -------------------------------------------------------------------------------- /sig-contributor-experience/markdown-link-style-guide.md: -------------------------------------------------------------------------------- 1 | # Markdown Link Style Guide 2 | 3 | Markdown provides for a number of different ways to link between documents. There are advantages and disadvantages of each method. 4 | 5 | - If you are linking between documents in the same folder, the easiest way to do it is use a relative link. 6 | ``` 7 | See this other document [here](document-2.md). 8 | ``` 9 | 10 | - If you are linking to a file in the same repo, but not in the same directory, it's usually best to use an absolute link from the root of the repo. The reason for this is if the source document moves, the destination document will still have the correct link. It also allows your links to work properly in your own fork of the repo. 11 | ``` 12 | For more information, check out [this](/contributor/guide/document-3.md) document. 13 | ``` 14 | 15 | - If you are linking to a file in another kubernetes repo, then use of the git.k8s.io shortener is preferred over a direct github link. This shortener lives in the kubernetes/k8s.io repo. 16 | ``` 17 | The super cool [prow tool](https://git.k8s.io/test-infra/prow/README.md) resides in the test-infra repo under the kubernetes organization 18 | ``` 19 | 20 | - If you are moving a document and leaving a tombstone file in it's place, please also set an end date for when the tombstone can be removed. 21 | ``` 22 | This file has moved to https://git.k8s.io/community/contributors/guide/README.md. 23 | <!-- 24 | This file is a placeholder to preserve links. Please remove after 3 months or the release of kubernetes 1.10, whichever comes first. 25 | --> 26 | ``` 27 | -------------------------------------------------------------------------------- /wg-policy/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Policy Working Group 10 | 11 | Provide an overall architecture that describes both the current policy related implementations as well as future policy related proposals in Kubernetes. Through a collaborative method, we want to present both dev and end user a universal view of policy architecture in Kubernetes. 12 | 13 | ## Meetings 14 | * Regular WG Meeting: [Thursdays at 17:00 PT (Pacific Time)](https://zoom.us/j/421702434) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=17:00&tz=PT%20%28Pacific%20Time%29). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1ihFfEfgViKlUMbY2NKxaJzBkgHh-Phk5hqKTzK-NEEs/edit?usp=sharing). 16 | 17 | ## Organizers 18 | 19 | * Howard Huang (**[@hannibalhuang](https://github.com/hannibalhuang)**), Huawei 20 | * Torin Sandall (**[@tsandall](https://github.com/tsandall)**), Styra 21 | * David Oppenheimer (**[@davidopp](https://github.com/davidopp)**), Google 22 | * Clayton Coleman (**[@smarterclayton](https://github.com/smarterclayton)**), Red Hat 23 | * Xuan Jia (**[@xuanjia](https://github.com/xuanjia)**), China Mobile 24 | 25 | ## Contact 26 | * [Slack](https://kubernetes.slack.com/messages/wg-policy) 27 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-policy) 28 | 29 | <!-- BEGIN CUSTOM CONTENT --> 30 | 31 | <!-- END CUSTOM CONTENT --> 32 | -------------------------------------------------------------------------------- /vendor/github.com/client9/misspell/case.go: -------------------------------------------------------------------------------- 1 | package misspell 2 | 3 | import ( 4 | "strings" 5 | ) 6 | 7 | // WordCase is an enum of various word casing styles 8 | type WordCase int 9 | 10 | // Various WordCase types.. likely to be not correct 11 | const ( 12 | CaseUnknown WordCase = iota 13 | CaseLower 14 | CaseUpper 15 | CaseTitle 16 | ) 17 | 18 | // CaseStyle returns what case style a word is in 19 | func CaseStyle(word string) WordCase { 20 | upperCount := 0 21 | lowerCount := 0 22 | 23 | // this iterates over RUNES not BYTES 24 | for i := 0; i < len(word); i++ { 25 | ch := word[i] 26 | switch { 27 | case ch >= 'a' && ch <= 'z': 28 | lowerCount++ 29 | case ch >= 'A' && ch <= 'Z': 30 | upperCount++ 31 | } 32 | } 33 | 34 | switch { 35 | case upperCount != 0 && lowerCount == 0: 36 | return CaseUpper 37 | case upperCount == 0 && lowerCount != 0: 38 | return CaseLower 39 | case upperCount == 1 && lowerCount > 0 && word[0] >= 'A' && word[0] <= 'Z': 40 | return CaseTitle 41 | } 42 | return CaseUnknown 43 | } 44 | 45 | // CaseVariations returns 46 | // If AllUpper or First-Letter-Only is upcased: add the all upper case version 47 | // If AllLower, add the original, the title and upcase forms 48 | // If Mixed, return the original, and the all upcase form 49 | // 50 | func CaseVariations(word string, style WordCase) []string { 51 | switch style { 52 | case CaseLower: 53 | return []string{word, strings.ToUpper(word[0:1]) + word[1:], strings.ToUpper(word)} 54 | case CaseUpper: 55 | return []string{strings.ToUpper(word)} 56 | default: 57 | return []string{word, strings.ToUpper(word)} 58 | } 59 | } 60 | -------------------------------------------------------------------------------- /contributors/design-proposals/node/kubelet-hypercontainer-runtime.md: -------------------------------------------------------------------------------- 1 | Kubelet HyperContainer Container Runtime 2 | ======================================= 3 | 4 | Authors: Pengfei Ni (@feiskyer), Harry Zhang (@resouer) 5 | 6 | ## Abstract 7 | 8 | This proposal aims to support [HyperContainer](http://hypercontainer.io) container 9 | runtime in Kubelet. 10 | 11 | ## Motivation 12 | 13 | HyperContainer is a Hypervisor-agnostic Container Engine that allows you to run Docker images using 14 | hypervisors (KVM, Xen, etc.). By running containers within separate VM instances, it offers a 15 | hardware-enforced isolation, which is required in multi-tenant environments. 16 | 17 | ## Goals 18 | 19 | 1. Complete pod/container/image lifecycle management with HyperContainer. 20 | 2. Setup network by network plugins. 21 | 3. 100% Pass node e2e tests. 22 | 4. Easy to deploy for both local dev/test and production clusters. 23 | 24 | ## Design 25 | 26 | The HyperContainer runtime will make use of the kubelet Container Runtime Interface. [Fakti](https://github.com/kubernetes/frakti) implements the CRI interface and exposes 27 | a local endpoint to Kubelet. Fakti communicates with [hyperd](https://github.com/hyperhq/hyperd) 28 | with its gRPC API to manage the lifecycle of sandboxes, containers and images. 29 | 30 | ![frakti](https://cloud.githubusercontent.com/assets/676637/18940978/6e3e5384-863f-11e6-9132-b638d862fd09.png) 31 | 32 | ## Limitations 33 | 34 | Since pods are running directly inside hypervisor, host network is not supported in HyperContainer 35 | runtime. 36 | 37 | ## Development 38 | 39 | The HyperContainer runtime is maintained by <https://github.com/kubernetes/frakti>. 40 | 41 | -------------------------------------------------------------------------------- /sig-cluster-ops/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Cluster Ops Special Interest Group 10 | 11 | Promote operability and interoperability of Kubernetes clusters. We focus on shared operations practices for Kubernetes clusters with a goal to make Kubernetes broadly accessible with a common baseline reference. We also organize operators as a sounding board and advocacy group. 12 | 13 | ## Meetings 14 | * Regular SIG Meeting: [Thursdays at 20:00 UTC](https://zoom.us/j/297937771) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=20:00&tz=UTC). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1IhN5v6MjcAUrvLd9dAWtKcGWBWSaRU8DNyPiof3gYMY/edit#). 16 | * [Meeting recordings](https://www.youtube.com/watch?v=7uyy37pCk4U&list=PL69nYSiGNLP3b38liicqy6fm2-jWT4FQR). 17 | 18 | ## Leadership 19 | 20 | ### Chairs 21 | The Chairs of the SIG run operations and processes governing the SIG. 22 | 23 | * Rob Hirschfeld (**[@zehicle](https://github.com/zehicle)**), RackN 24 | * Jaice Singer DuMars (**[@jdumars](https://github.com/jdumars)**), Microsoft 25 | 26 | ## Contact 27 | * [Slack](https://kubernetes.slack.com/messages/sig-cluster-ops) 28 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-ops) 29 | * [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fcluster-ops) 30 | 31 | <!-- BEGIN CUSTOM CONTENT --> 32 | 33 | <!-- END CUSTOM CONTENT --> 34 | -------------------------------------------------------------------------------- /events/2016/developer-summit-2016/cluster_federation_notes.md: -------------------------------------------------------------------------------- 1 | # Cluster Federation 2 | 3 | There's a whole bunch of reasons why federation is interesting. There's HA, there's geographic locality, there's just managing very large clusters. Use cases: 4 | 5 | * HA 6 | * Hybrid Cloud 7 | * Geo/latency 8 | * Scalability (many large clusters instead of one gigantic one) 9 | * visibility of multiple clusters 10 | 11 | You don't actually need federation for geo-location now, but it helps. The mental model for this is kind of like Amazon AZ or Google zones. Sometimes we don't care where a resource is but sometimes we do. Sometimes you want specific policy control, like regulatory constraints about what can run where. 12 | 13 | From the enterprise point of view, central IT is in control and knowledge of where stuff gets deployed. Bob thinks it would be a very bad idea for us to try to solve complex policy ideas and enable them, it's a tar pit. We should just have the primitives of having different regions and be able to say what goes where. 14 | 15 | Currently, you either do node labelling which ends up being complex and dependent on discipline. Or you have different clusters and you don't have common namespaces. Some discussion of Intel proposal for cluster metadata. 16 | 17 | Bob's mental model is AWS regions and AZs. For example, if we're building a big cassandra cluster, and you want to make sure that nodes aren't all in the same zone. 18 | 19 | Quinton went over a WIP implementation for applying policies, with a tool which applies policy before resource requests go to the scheduler. It uses an open-source policy language, and labels on the request. 20 | 21 | Notes interrupted here, hopefully other members will fill in. 22 | -------------------------------------------------------------------------------- /events/elections/2017/errordeveloper_bio.md: -------------------------------------------------------------------------------- 1 | # [Ilya Dmitrchenko](https://github.com/errordeveloper) 2 | 3 | ## Manifesto 4 | 5 | Ilya has been contributing to Kubernetes since 2014. The focus of his contributions has been on solving 6 | general cluster provisioning and bootstrap problems and making networking easier. For example in 2016, 7 | he did the groundwork on the initial version of `kubeadm`. 8 | 9 | Ilya is a DX engineer at Weaveworks and is based in London. From there he travels (mostly in Europe) to 10 | educate the wider community about the benefits of containers and orchestration with Kubernetes. Ilya 11 | would be delighted to represent the European users as a member of the steering committee. 12 | 13 | Most recently, he started participating in organised community activities whose aim is to solve the 14 | problems and the needs of end users who have Kubernetes in production or who are looking to put it in 15 | production. To that end, he is a member of the London Production User Council, and together with other 16 | contributors launched Kubernetes Office Hours. 17 | 18 | To learn more about Ilya's background and why he deeply cares about the community, please take a look at 19 | his [personal blog](https://medium.com/@errordeveloper/a-little-more-about-me-b0b6238ba7f8). 20 | 21 | 22 | ## Key Priorities 23 | 24 | - Customer success with open-source Kubernetes 25 | - Ease of use, in majority of general cases 26 | - Growth of the community, and fairness 27 | - Social and technical diversity 28 | 29 | ## More Info 30 | 31 | - [Personal projects](https://github.com/errordeveloper) 32 | - [Tweets](https://github.com/errordeveloper) 33 | - [Personal blog](https://medium.com/@errordeveloper/a-little-more-about-me-b0b6238ba7f8) 34 | -------------------------------------------------------------------------------- /committee-steering/governance/README.md: -------------------------------------------------------------------------------- 1 | # SIG Governance Template 2 | 3 | ## Goals 4 | 5 | The following documents outline recommendations and requirements for SIG governance structure and provide 6 | template documents for SIGs to adapt. The goals are to define the baseline needs for SIGs to self govern 7 | and organize in a way that addresses the needs of the core Kubernetes project. 8 | 9 | The documents are focused on: 10 | 11 | - Outlining organizational responsibilities 12 | - Outlining organizational roles 13 | - Outlining processes and tools 14 | 15 | Specific attention has been given to: 16 | 17 | - The role of technical leadership 18 | - The role of operational leadership 19 | - Process for agreeing upon technical decisions 20 | - Process for ensuring technical assets remain healthy 21 | 22 | ## How to use the templates 23 | 24 | When developing or modifying a SIG governance doc, the intention is for SIGs to use the templates (*under development*) 25 | as a common set of options SIGs may choose to incorporate into their own governance structure. It is recommended that 26 | SIGs start by looking at the [Recommendations and requirements] for SIG governance docs and consider what structure 27 | they think will work best for them before pulling items from the templates. 28 | 29 | The expectation is that SIGs will pull and adapt the options in the templates to best meet the needs of the both the SIG 30 | and project. 31 | 32 | - [Recommendations and requirements] 33 | 34 | ## Templates 35 | 36 | - [Short Template] 37 | 38 | ## FAQ 39 | 40 | See [frequently asked questions] 41 | 42 | [Recommendations and requirements]: sig-governance-requirements.md 43 | [Short Template]: sig-governance-template-short.md 44 | [frequently asked questions]: FAQ.md 45 | -------------------------------------------------------------------------------- /contributors/devel/logging.md: -------------------------------------------------------------------------------- 1 | ## Logging Conventions 2 | 3 | The following conventions for the glog levels to use. 4 | [glog](http://godoc.org/github.com/golang/glog) is globally preferred to 5 | [log](http://golang.org/pkg/log/) for better runtime control. 6 | 7 | * glog.Errorf() - Always an error 8 | 9 | * glog.Warningf() - Something unexpected, but probably not an error 10 | 11 | * glog.Infof() has multiple levels: 12 | * glog.V(0) - Generally useful for this to ALWAYS be visible to an operator 13 | * Programmer errors 14 | * Logging extra info about a panic 15 | * CLI argument handling 16 | * glog.V(1) - A reasonable default log level if you don't want verbosity. 17 | * Information about config (listening on X, watching Y) 18 | * Errors that repeat frequently that relate to conditions that can be corrected (pod detected as unhealthy) 19 | * glog.V(2) - Useful steady state information about the service and important log messages that may correlate to significant changes in the system. This is the recommended default log level for most systems. 20 | * Logging HTTP requests and their exit code 21 | * System state changing (killing pod) 22 | * Controller state change events (starting pods) 23 | * Scheduler log messages 24 | * glog.V(3) - Extended information about changes 25 | * More info about system state changes 26 | * glog.V(4) - Debug level verbosity (for now) 27 | * Logging in particularly thorny parts of code where you may want to come back later and check it 28 | 29 | As per the comments, the practical default level is V(2). Developers and QE 30 | environments may wish to run at V(3) or V(4). If you wish to change the log 31 | level, you can pass in `-v=X` where X is the desired maximum level to log. 32 | -------------------------------------------------------------------------------- /events/elections/2017/michaelrubin_bio.md: -------------------------------------------------------------------------------- 1 | # Michael Rubin Bio 2 | 3 | GitHub: @matchstick 4 | 5 | ## About Me 6 | 7 | I have been a software engineer, technical manager, and leader for 8 | ~20 years. I am passionate about helping projects and people thrive. 9 | Today I lead a number of Kubernetes teams at Google, including Storage, 10 | Networking, Multi-cluster, Node, and more. 11 | 12 | I love coding and technology, but even more than that I love mentoring 13 | others and helping them to have impact and grow professionally. This is 14 | why I choose to support teams and projects as a technical manager. 15 | 16 | My leadership style is to bring sharp focus to technical efforts, and 17 | to help others become successful leaders, themselves. I find that many 18 | technology problems are not purely technical, and one of my biggest 19 | strengths is my ability communicate, connect with people, and get to 20 | the root of a problem. People are not machines, and they need different 21 | skills than just pure engineering. 22 | 23 | During my 1.5 years with Kubernetes, I have worked directly and 24 | indirectly with several SIGs - Storage, Multi-cluster, Networking, 25 | Scheduling, and Node. I think I have brought clarity and structure to 26 | the efforts, helped organize priorities and roadmaps, and helped the 27 | teams and individuals grow. I have built lasting relationships with 28 | the people of Kubernete, and not just the code. 29 | 30 | As a member of the Steering Committee, I would focus on: 31 | 32 | * Cross SIG efforts and how to co-ordinate them 33 | * Getting more things out of core, but keeping them part of Kubernetes 34 | * Maintain the cool, open and inviting environment we have today 35 | * Delegate and empower others by adding structure (not process) 36 | 37 | -------------------------------------------------------------------------------- /contributors/devel/getting-builds.md: -------------------------------------------------------------------------------- 1 | # Getting Kubernetes Builds 2 | 3 | You can use [hack/get-build.sh](http://releases.k8s.io/HEAD/hack/get-build.sh) 4 | to get a build or to use as a reference on how to get the most recent builds 5 | with curl. With `get-build.sh` you can grab the most recent stable build, the 6 | most recent release candidate, or the most recent build to pass our ci and gce 7 | e2e tests (essentially a nightly build). 8 | 9 | Run `./hack/get-build.sh -h` for its usage. 10 | 11 | To get a build at a specific version (v1.1.1) use: 12 | 13 | ```console 14 | ./hack/get-build.sh v1.1.1 15 | ``` 16 | 17 | To get the latest stable release: 18 | 19 | ```console 20 | ./hack/get-build.sh release/stable 21 | ``` 22 | 23 | Use the "-v" option to print the version number of a build without retrieving 24 | it. For example, the following prints the version number for the latest ci 25 | build: 26 | 27 | ```console 28 | ./hack/get-build.sh -v ci/latest 29 | ``` 30 | 31 | You can also use the gsutil tool to explore the Google Cloud Storage release 32 | buckets. Here are some examples: 33 | 34 | ```sh 35 | gsutil cat gs://kubernetes-release-dev/ci/latest.txt # output the latest ci version number 36 | gsutil cat gs://kubernetes-release-dev/ci/latest-green.txt # output the latest ci version number that passed gce e2e 37 | gsutil ls gs://kubernetes-release-dev/ci/v0.20.0-29-g29a55cc/ # list the contents of a ci release 38 | gsutil ls gs://kubernetes-release/release # list all official releases and rcs 39 | ``` 40 | 41 | ## Install `gsutil` 42 | 43 | Example installation: 44 | 45 | ```console 46 | $ curl -sSL https://storage.googleapis.com/pub/gsutil.tar.gz | sudo tar -xz -C /usr/local/src 47 | $ sudo ln -s /usr/local/src/gsutil/gsutil /usr/bin/gsutil 48 | ``` 49 | -------------------------------------------------------------------------------- /sig-ui/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # UI Special Interest Group 10 | 11 | Covers all things UI related. Efforts are centered around Kubernetes Dashboard: a general purpose, web-based UI for Kubernetes clusters. It allows users to manage applications running in the cluster and troubleshoot them, as well as manage the cluster itself. 12 | 13 | ## Meetings 14 | * Regular SIG Meeting: [Thursdays at 18:00 CET (Central European Time)](https://groups.google.com/forum/#!forum/kubernetes-sig-ui) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=18:00&tz=CET%20%28Central%20European%20Time%29). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1PwHFvqiShLIq8ZpoXvE3dSUnOv1ts5BTtZ7aATuKd-E/edit?usp=sharing). 16 | 17 | ## Leadership 18 | 19 | ### Chairs 20 | The Chairs of the SIG run operations and processes governing the SIG. 21 | 22 | * Dan Romlein (**[@danielromlein](https://github.com/danielromlein)**), Google 23 | * Sebastian Florek (**[@floreks](https://github.com/floreks)**), Fujitsu 24 | 25 | ## Contact 26 | * [Slack](https://kubernetes.slack.com/messages/sig-ui) 27 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-ui) 28 | * [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fui) 29 | 30 | ## Subprojects 31 | 32 | The following subprojects are owned by sig-ui: 33 | - **dashboard** 34 | - Owners: 35 | - https://raw.githubusercontent.com/kubernetes/dashboard/master/OWNERS 36 | 37 | <!-- BEGIN CUSTOM CONTENT --> 38 | 39 | <!-- END CUSTOM CONTENT --> 40 | -------------------------------------------------------------------------------- /vendor/github.com/client9/misspell/ascii.go: -------------------------------------------------------------------------------- 1 | package misspell 2 | 3 | // ByteToUpper converts an ascii byte to upper cases 4 | // Uses a branchless algorithm 5 | func ByteToUpper(x byte) byte { 6 | b := byte(0x80) | x 7 | c := b - byte(0x61) 8 | d := ^(b - byte(0x7b)) 9 | e := (c & d) & (^x & 0x7f) 10 | return x - (e >> 2) 11 | } 12 | 13 | // ByteToLower converts an ascii byte to lower case 14 | // uses a branchless algorithm 15 | func ByteToLower(eax byte) byte { 16 | ebx := eax&byte(0x7f) + byte(0x25) 17 | ebx = ebx&byte(0x7f) + byte(0x1a) 18 | ebx = ((ebx & ^eax) >> 2) & byte(0x20) 19 | return eax + ebx 20 | } 21 | 22 | // ByteEqualFold does ascii compare, case insensitive 23 | func ByteEqualFold(a, b byte) bool { 24 | return a == b || ByteToLower(a) == ByteToLower(b) 25 | } 26 | 27 | // StringEqualFold ASCII case-insensitive comparison 28 | // golang toUpper/toLower for both bytes and strings 29 | // appears to be Unicode based which is super slow 30 | // based from https://codereview.appspot.com/5180044/patch/14007/21002 31 | func StringEqualFold(s1, s2 string) bool { 32 | if len(s1) != len(s2) { 33 | return false 34 | } 35 | for i := 0; i < len(s1); i++ { 36 | c1 := s1[i] 37 | c2 := s2[i] 38 | // c1 & c2 39 | if c1 != c2 { 40 | c1 |= 'a' - 'A' 41 | c2 |= 'a' - 'A' 42 | if c1 != c2 || c1 < 'a' || c1 > 'z' { 43 | return false 44 | } 45 | } 46 | } 47 | return true 48 | } 49 | 50 | // StringHasPrefixFold is similar to strings.HasPrefix but comparison 51 | // is done ignoring ASCII case. 52 | // / 53 | func StringHasPrefixFold(s1, s2 string) bool { 54 | // prefix is bigger than input --> false 55 | if len(s1) < len(s2) { 56 | return false 57 | } 58 | if len(s1) == len(s2) { 59 | return StringEqualFold(s1, s2) 60 | } 61 | return StringEqualFold(s1[:len(s2)], s2) 62 | } 63 | -------------------------------------------------------------------------------- /events/elections/2017/kris-nova_bio.md: -------------------------------------------------------------------------------- 1 | # Kris Nova 2 | 3 | ## What is important to me 4 | 5 | Mental, philosophical, and design diversity. Period. 6 | 7 | I truly believe that the best teams and projects are those that embrace unique and sometimes conflicting ways of thinking. 8 | 9 | Having a leadership board of people who all think the same way, and all are moving in the right direction is stale and stagnant. 10 | 11 | - I want to help foster diversity in Kubernetes in both our design process, but also our goals and philosophies. 12 | - I want to encourage my peers to put themselves into difficult, or testing situations in order to help grow and mature. 13 | - I want to let others know that it's okay to try something and fail as we all learn as a scientific community. 14 | 15 | 16 | ## Work in the community 17 | 18 | - I spend as much of my free time as humanly possible contributing to Kubernetes. 19 | - I take impromptu video calls with total strangers. 20 | - I helped run *sig-aws* even though it conflicted with my dayjob. 21 | - I created [kubicorn](https://github.com/kris-nova/kubicorn) in my free time and it has been reviewed as one of the best open source projects to contribute to in the space. 22 | 23 | ## Reasons to pick me 24 | 25 | ## I think differently. 26 | 27 | I question the world around me, and have been in a ton of different roles in engineering space. Including time in both genders. 28 | 29 | ## I believe that software comes first. 30 | 31 | I love kubernetes regardless of my employer, and will always contribute because I believe in it. 32 | I believe the way we continue to keep the project great is to focus on community, as well as writing kick ass software with a great user interface. 33 | 34 | ## tldr 35 | 36 | I embrace being different and want to clean up our code and improve user experience. -------------------------------------------------------------------------------- /contributors/devel/collab.md: -------------------------------------------------------------------------------- 1 | # On Collaborative Development 2 | 3 | ## Code reviews 4 | 5 | All changes must be code reviewed. For non-maintainers this is obvious, since 6 | you can't commit anyway. But even for maintainers, we want all changes to get at 7 | least one review, preferably (for non-trivial changes obligatorily) from someone 8 | who knows the areas the change touches. For non-trivial changes we may want two 9 | reviewers. The primary reviewer will make this decision and nominate a second 10 | reviewer, if needed. Except for trivial changes, PRs should not be committed 11 | until relevant parties (e.g. owners of the subsystem affected by the PR) have 12 | had a reasonable chance to look at PR in their local business hours. 13 | 14 | Most PRs will find reviewers organically. If a maintainer intends to be the 15 | primary reviewer of a PR they should set themselves as the assignee on GitHub 16 | and say so in a reply to the PR. Only the primary reviewer of a change should 17 | actually do the merge, except in rare cases (e.g. they are unavailable in a 18 | reasonable timeframe). 19 | 20 | If a PR has gone 2 work days without an owner emerging, please poke the PR 21 | thread and ask for a reviewer to be assigned. 22 | 23 | Except for rare cases, such as trivial changes (e.g. typos, comments) or 24 | emergencies (e.g. broken builds), maintainers should not merge their own 25 | changes. 26 | 27 | Expect reviewers to request that you avoid [common go style 28 | mistakes](https://github.com/golang/go/wiki/CodeReviewComments) in your PRs. 29 | 30 | ## Assigned reviews 31 | 32 | Maintainers can assign reviews to other maintainers, when appropriate. The 33 | assignee becomes the shepherd for that PR and is responsible for merging the PR 34 | once they are satisfied with it or else closing it. The assignee might request 35 | reviews from non-maintainers. 36 | -------------------------------------------------------------------------------- /events/elections/2017/alexpollitt_bio.md: -------------------------------------------------------------------------------- 1 | # Alex Pollitt 2 | 3 | I am excited to have been nominated for the steering committee. I recognize that doing 4 | the role justice will be a demanding and time consuming commitment, but I would like 5 | to do my part to help maintain and foster the growth of this amazing community of 6 | contributors and users. 7 | 8 | For those of you who don’t know me, I am one of the founders of Tigera, the company behind 9 | Calico, and active contributors to flannel, CNI, Kubernetes, and Istio. I’ve been working 10 | with the Kubernetes community since 2014 and have great respect for everyone I’ve had the 11 | chance to get to know along the way. 12 | 13 | Since the early days of the project, when friends used to ask, “which container orchestrator 14 | would you bet on?”, my answer was always Kubernetes – not because of the great design 15 | principles, but because of how the founding team and those already contributing welcomed 16 | others to take part and collaborate with an equal voice to move the project forward. For me, 17 | “Kubernetes” means the people and how they work together, as much as technology. 18 | 19 | One example I experienced was the k8s-sig-net efforts to agree a network policy API. In 20 | other communities, this might have descended into vendors trying to get one up on each 21 | other. Instead there was true collaboration, focusing on technical merit and meeting the needs 22 | of future users. It was awesome to play a part in that process and even though it was just one 23 | small corner of Kubernetes it’s a great illustration of why I love working in this community. 24 | 25 | If elected, I promise to do my utmost to foster and facilitate this kind of diverse, vendor 26 | neutral, merit based collaboration, empower and support contributors to shape the project, 27 | and maintain the spirit of this awesome community as it grows. 28 | -------------------------------------------------------------------------------- /events/elections/2017/timothysc_bio.md: -------------------------------------------------------------------------------- 1 | # Timothy St. Clair 2 | 3 | ## Contact Information 4 | 5 | - GitHub/Slack: [@timothysc](https://github.com/timothysc) 6 | - Email: tstclair@heptio.com 7 | - Twitter: [@timothysc](https://twitter.com/timothysc) 8 | 9 | ## Background 10 | 11 | I've been involved in the Kubernetes project since 2014, and prior to that I was an active member in the Mesos community, with over 10+ years of experience working on open source projects across a plethora of communities. During my tenure, I've been lucky enough to meet a number of great folks working on various SIGs: 12 | 13 | - SIG Scheduling & Testing (Lead) 14 | - SIG Scale, Cluster Life-cycle, API Machinery, Node (Contributor) 15 | 16 | ## Why I want to be on the Steering Committee (Optimize, Simplify, and Empower) 17 | 18 | Time is our most precious commodity, and few things can be more frustrating than wanting to contribute only to watch patches bit-rot, have legitimate issues sit unaddressed, or type `/retest` for the 10th time. My primary goal in running for a position on the steering committee is optimize processes such that no one feels like their time is wasted working on this project. As of today, the process that a contributor needs to follow is byzantine, and can be daunting for folks who are new to the community. (Optimize) 19 | 20 | However, it doesn't stop there. In order for the community to thrive, we need to continually reevaluate our processes to ensure what we are doing makes sense, and ensure those processes are simple and concise. (Simplify) 21 | 22 | Lastly, I want to help promote and empower folks in the community to take on some of the roles that have traditionally been filled by google. Once core aspects of the test and release process can be done by non-googlers I think we've reached a point where we have empowered the broader community. (Empower) 23 | 24 | ## Where I work 25 | 26 | Heptio 27 | -------------------------------------------------------------------------------- /generator/list.tmpl: -------------------------------------------------------------------------------- 1 | {{- template "header" }} 2 | # SIGs and Working Groups 3 | 4 | Most community activity is organized into Special Interest Groups (SIGs), 5 | time bounded Working Groups, and the [community meeting](communication.md#weekly-meeting). 6 | 7 | SIGs follow these [guidelines](governance.md) although each of these groups may operate a little differently 8 | depending on their needs and workflow. 9 | 10 | Each group's material is in its subdirectory in this project. 11 | 12 | When the need arises, a [new SIG can be created](sig-creation-procedure.md) 13 | 14 | ### Master SIG List 15 | 16 | | Name | Label | Chairs | Contact | Meetings | 17 | |------|-------|--------|---------|----------| 18 | {{- range .Sigs}} 19 | |[{{.Name}}]({{.Dir}}/README.md)|{{.Label}}|{{range .Leadership.Chairs}}* [{{.Name}}](https://github.com/{{.GitHub}}){{if .Company}}, {{.Company}}{{end}}<br>{{end}}|* [Slack](https://kubernetes.slack.com/messages/{{.Contact.Slack}})<br>* [Mailing List]({{.Contact.MailingList}})|{{- range .Meetings -}} 20 | * {{.Description}}: [{{.Day}}s at {{.Time}} {{.TZ}} ({{.Frequency}})]({{.URL}})<br> 21 | {{- end -}} 22 | {{- range .Subprojects -}} 23 | {{ $name := .Name }} 24 | {{- range .Meetings -}} 25 | * ({{ $name }}) {{.Description}}: [{{.Day}}s at {{.Time}} {{.TZ}} ({{.Frequency}})]({{.URL}})<br> 26 | {{- end -}} 27 | {{- end -}} 28 | {{- end }} 29 | 30 | ### Master Working Group List 31 | 32 | | Name | Organizers | Contact | Meetings | 33 | |------|------------|---------|----------| 34 | {{- range .WorkingGroups}} 35 | |[{{.Name}}]({{.Dir}}/README.md)|{{range .Leadership.Chairs}}* [{{.Name}}](https://github.com/{{.GitHub}}){{if .Company}}, {{.Company}}{{end}}<br>{{end}}|* [Slack](https://kubernetes.slack.com/messages/{{.Contact.Slack}})<br>* [Mailing List]({{.Contact.MailingList}})|{{range .Meetings}}* {{.Description}}: [{{.Day}}s at {{.Time}} {{.TZ}} ({{.Frequency}})]({{.URL}})<br>{{end}} 36 | {{- end }} 37 | -------------------------------------------------------------------------------- /events/elections/2017/jaicesingerdumars_bio.md: -------------------------------------------------------------------------------- 1 | # Jaice Singer DuMars 2 | 3 | ## Contact Information 4 | 5 | - GitHub: [@jdumars](https://github.com/jdumars) 6 | - Twitter: [@jaydumars](https://twitter.com/jaydumars) 7 | - LinkedIn: [Jaice Singer DuMars](https://www.linkedin.com/in/jasondumars/) 8 | - Works for: Microsoft 9 | 10 | ## Why me? 11 | 12 | The steering committee represents a unique convergence of my passion for servant leadership, organizational dynamics, inclusion, advocacy, and process optimization. It's always my highest purpose to be a voice and advocate for those I serve. And, if elected, I will faithfully serve the ever-changing, sometimes divergent, and always important needs of the Kubernetes community. 13 | 14 | ## Servant leadership 15 | 16 | Since my first moments in the community, I have sought out every opportunity I can to make things better. I wrote an article about this called [What Kubernetes means to me](http://bit.ly/k8s2me) that will shed some light on my journey to this point. My contributions to the community currently include leading the 1.8 release team, co-leading SIG Azure, SIG Architecture, and SIG Cluster Ops (although Rob Hirschfeld has been covering for me while I work on the release). I have facilitated every release retrospective since 1.3, and have improved my typing skills by note taking at countless SIG meetings. I also work behind the scenes on Community things with Sarah and Jorge. 17 | 18 | ## Career 19 | 20 | I've been in love with systems, networks, and the human elements of interconnectivity since I was a SysOp on a BBS as a teenager. My first hack was in grade school, making the Oregon Trail game say naughty things. In the time since, I have been a systems and network engineer, and held several engineering management directorships at companies large and small. At Microsoft, all I do is Kubernetes, so I definitely have the organizational support to carry out my duties on the committee. 21 | -------------------------------------------------------------------------------- /wg-machine-learning/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # Machine Learning Working Group 10 | 11 | Identify and fix gaps in Kubernetes to better support Machine Learning applications 12 | 13 | ## Meetings 14 | * Regular WG Meeting: [Thursdays at 13:00 PT (Pacific Time)](https://zoom.us/j/4799874685) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=13:00&tz=PT%20%28Pacific%20Time%29). 15 | * [Meeting notes and Agenda](https://goo.gl/gBCdt1). 16 | 17 | ## Organizers 18 | 19 | * Vishnu Kannan (**[@vishh](https://github.com/vishh)**), Google 20 | * Kenneth Owens (**[@kow3ns](https://github.com/kow3ns)**), Google 21 | * Balaji Subramaniam (**[@balajismaniam](https://github.com/balajismaniam)**), Intel 22 | * Connor Doyle (**[@ConnorDoyle](https://github.com/ConnorDoyle)**), Intel 23 | 24 | ## Contact 25 | * [Slack](https://kubernetes.slack.com/messages/wg-machine-learning) 26 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-machine-learning) 27 | 28 | <!-- BEGIN CUSTOM CONTENT --> 29 | A working group dedicated towards making Kubernetes work best for Machine Learning workloads. 30 | 31 | The charter for this working group as [proposed](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/kubernetes-dev/lOeMjOLilxI/wuQayFDvCQAJ) is as follows: 32 | 33 | * Assess the state of the art for ML workloads on K8s 34 | * Identify pain points users currently have with ML on k8s 35 | * Identify, prioritize and execute on improving k8s to better support ML workloads in the near, medium, and long term. 36 | 37 | TODO: Finalize and update the charter after the initial kick off meeting on 3/1/2018. 38 | <!-- END CUSTOM CONTENT --> 39 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-06-08.md: -------------------------------------------------------------------------------- 1 | # June 8, 2016 2 | 3 | - Intro by Michelle Noorali 4 | - Adnan Abdulhussein, Stacksmith lead at Bitnami, did a demo of Stacksmith 5 | - In the container world, updates to your application's stack or environment are rolled out by bringing down outdated containers and replacing them with an updated container image. Tools like Docker and Kubernetes make it incredibly easy to do this, however, knowing when your stack is outdated or vulnerable and starting the upgrade process is still a manual step. Stacksmith is a service that aims to solve this by maintaining your base Dockerfiles and proactively keeping them up-to-date and secure. This demo walked through how you can use Stacksmith with your application on GitHub to provide continuous delivery of your application container images. 6 | - Adnan is available as @prydonius on the Kubernetes slack as well as on [twitter](https://twitter.com/prydonius) for questions and feedback. 7 | - Feel free to leave feedback on the [Stacksmith](https://stacksmith.bitnami.com/) feedback tab. 8 | - Matt Farina gave an update on the SIG-Apps survey. 9 | - You can find a list of the current questions [here](https://docs.google.com/spreadsheets/d/1d4P_-lNGzw4jS9T4iizQBOtWT4O6e5yjDUygINigJnA/edit#gid=0) in a view only state. 10 | - If you are interested in submitting questions or being a part of the team that collects/analyzes the data, please reach out to @mattfarina on the Kubernetes slack channel. 11 | - Michelle Noorali gave an update on where you can find information and examples on PetSets. 12 | - Here are some links provided by Pranshanth from Google. 13 | - [github issue](https://github.com/kubernetes/kubernetes/issues/260#issuecomment-220395798) 14 | - [example pets](https://git.k8s.io/contrib/pets) 15 | - Feel free to get your hands dirty. We will be discussing the provided examples in the upcoming weeks. 16 | 17 | Watch the [recording](https://youtu.be/wXZAXemhGb0). 18 | -------------------------------------------------------------------------------- /events/2017/05-leadership-summit/announcement.md: -------------------------------------------------------------------------------- 1 | This is an announcement for the 2017 Kubernetes Leadership Summit, which will occur on June 2nd, 2017 in San Jose, CA. 2 | This event will be similar to the [Kubernetes Developer's Summit](/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md) in November 3 | 2016, but involving a smaller smaller audience comprised solely of leaders and influencers of the community. These leaders and 4 | influences include the SIG leads, release managers, and representatives from several companies, including (but not limited to) 5 | Google, Red Hat, CoreOS, WeaveWorks, Deis, and Mirantis. 6 | 7 | The summit will provide an avenue for leaders in the Kubernetes community to connect face to face and mindshare about future 8 | community development and community governance endeavors. 9 | 10 | This announcement serves to notify the broader community of the existence and goals of the event. 11 | 12 | This is an **invite-only event**. All invitees will receive a direct invitation from Cameron (czahedi *at* google *dot* com). 13 | 14 | ### Event Format 15 | 16 | The Leadership Summit will mirror the format of the Developer’s Summit, which was a "loosely-structured unconference”. We will have moderators/facilitators and discussion topics, alongside all-day completely unstructured / spontaneous breakouts. 17 | 18 | The various sessions will be proposed and voted on by the community in the weeks leading up to the event. This allows the 19 | community to motivate the events of the day without dedicating precious day-of time to choosing the sessions and making a 20 | schedule. 21 | 22 | ### Desired outcomes 23 | 24 | * Generate notes from the sessions to feed the project's documentation and knowledge base, and also to keep non-attendees plugged in 25 | * Make (and document) recommendations and decisions for the near-term and mid-term future of the project 26 | * Come up with upcoming action items, as well as leaders for those action items, for the various topics that we discuss 27 | -------------------------------------------------------------------------------- /events/2017/12-contributor-summit/current-state-of-client-libraries.md: -------------------------------------------------------------------------------- 1 | Story so far is described at https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/csi-client-structure-proposal.md 2 | - linked from https://github.com/kubernetes-client/community/blob/master/design-docs/clients-library-structure.md 3 | 4 | Would like libs to be more "fluent" - should join up with the native language features e.g. JavaDoc, per-platform 5 | 6 | OpenAPI (Swagger) has limitations which force ugly workarounds. 7 | - e.g. doesn't cover returning different types in response to a call e.g. a result or an error. 8 | - OpenAPI 3 fixes a number of these limitations 9 | 10 | Key difficulty is which verbs apply to which objects - Go doesn't natively have this concept. 11 | 12 | OpenAPI doc is produced by running an api-server, which knows how to dispatch verbs to objects, and having it generate the OpenAPI 13 | 14 | Should we deprecate SPDY in favour of websockets? (probably yes) 15 | 16 | What do people want in a client library? 17 | - Go lib smaller than 40MB 18 | - Go lib with dynamic types (this exists?) 19 | - Rust 20 | - C++ 21 | 22 | Are there client libs for things like service catalog? Where do those live? 23 | 24 | How can clients talk protobufs to api-server? Set the content-type. 25 | 26 | K8s protobuf def uses an 'envelope' type covering things like storage version 27 | 28 | Protobuf not self-describing so not great for api-server CRUD operations 29 | 30 | A few bits of extra information in the protobuf definition would be great - e.g. pluralisation 31 | 32 | Client SIG is relatively under-represented and relatively easy to join in - please come along! 33 | 34 | kubeconfig semantics are not standardised - when reimplemented in different languages this can give unexpected results. Example: URL with no scheme supported by Go but not Java 35 | 36 | How should clients deal with rolling authorisation certificates? 37 | 38 | There are type wrinkles, like "intorstring" and "quantity" -------------------------------------------------------------------------------- /events/elections/2017/calebamiles_bio.md: -------------------------------------------------------------------------------- 1 | # caleb miles 2 | 3 | ## Contact Information 4 | 5 | - GitHub/Slack: @calebamiles 6 | - Email: caleb.miles@coreos.com 7 | 8 | ### Problem solving style 9 | 10 | I am a huge fan of ideas which simplify and unify, possibly due to my 11 | undergraduate study of physics and mathematics. I believe that collaboration is 12 | incredibly important and that continuous feedback on incremental solutions are 13 | likely to produce the best outcome. I therefore try spend a lot of time talking 14 | with people about the problems that are important to them before stepping back 15 | to try to introduce a minimal solution based on their concerns. 16 | 17 | ### Problems that are important to me 18 | 19 | I believe that addressing the dual challenge of communicating what everyone is 20 | working on to other developers, and then explaining that work to users is one 21 | of the most pressing issues for Kubernetes today. 22 | 23 | I also believe that we need to invest in the contributor experience particularly 24 | by better supporting new contributors with mentorship programs, especially for 25 | the self taught, new graduates, and underrepresented communities. If we are 26 | going to be a successful and sustainable project we need to ensure that we 27 | maintain a healthy pipeline of new contributors while at the same time reducing 28 | the workload for more established contributors. 29 | 30 | Scaling contributions is another serious challenge for the project and I am very 31 | interested in working on helping to support the effort to rethink the Kubernetes 32 | release process. 33 | 34 | ### Roles held 35 | 36 | I joined the community in 2016 since then I have made shallow contributions to 37 | 38 | - SIG Contributor Experience 39 | - SIG Release 40 | - SIG PM 41 | - SIG Testing 42 | 43 | as well as serving in a minor capacity in the 1.5, 1.6, 1.7, and 1.8 releases. I 44 | currently help to facilitate 45 | 46 | - SIG PM, co lead and co founder 47 | - SIG Release, co lead and co founder 48 | 49 | ### Where I work 50 | 51 | CoreOS 52 | 53 | -------------------------------------------------------------------------------- /contributors/guide/release-notes.md: -------------------------------------------------------------------------------- 1 | # Adding Release Notes 2 | 3 | On the kubernetes/kubernetes repository, release notes are required for any pull request with user-visible changes, such as bug-fixes, feature additions, and output format changes. 4 | 5 | To meet this requirement, do one of the following: 6 | - Add notes in the release notes block, or 7 | - Update the release note label 8 | 9 | If you don't add release notes in the pull request template, the `do-not-merge/release-note-label-needed` label is added to your pull request automatically after you create it. There are a few ways to update it. 10 | 11 | To add a release-note section to the pull request description: 12 | 13 | For pull requests with a release note: 14 | 15 | ```release-note 16 | Your release note here 17 | ``` 18 | 19 | For pull requests that require additional action from users switching to the new release, include the string "action required" (case insensitive) in the release note: 20 | 21 | ```release-note 22 | action required: your release note here 23 | ``` 24 | 25 | For pull requests that don't need to be mentioned at release time, just write "NONE" (case insensitive): 26 | 27 | ```release-note 28 | NONE 29 | ``` 30 | 31 | The `/release-note-none` comment command can still be used as an alternative to writing "NONE" in the release-note block if it is left empty. 32 | 33 | To see how to format your release notes, view the kubernetes/kubernetes [pull request template](https://git.k8s.io/kubernetes/.github/PULL_REQUEST_TEMPLATE.md) for a brief example. pull request titles and body comments can be modified at any time prior to the release to make them friendly for release notes. 34 | 35 | Release notes apply to pull requests on the master branch. For cherry-pick pull requests, see the [cherry-pick instructions](contributors/devel/cherry-picks.md). The only exception to these rules is when a pull request is not a cherry-pick and is targeted directly to the non-master branch. In this case, a `release-note-*` label is required for that non-master pull request. -------------------------------------------------------------------------------- /hack/verify-generated-docs.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | 3 | # Copyright 2018 The Kubernetes Authors. 4 | # 5 | # Licensed under the Apache License, Version 2.0 (the "License"); 6 | # you may not use this file except in compliance with the License. 7 | # You may obtain a copy of the License at 8 | # 9 | # http://www.apache.org/licenses/LICENSE-2.0 10 | # 11 | # Unless required by applicable law or agreed to in writing, software 12 | # distributed under the License is distributed on an "AS IS" BASIS, 13 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 14 | # See the License for the specific language governing permissions and 15 | # limitations under the License. 16 | 17 | set -o errexit 18 | set -o nounset 19 | set -o pipefail 20 | 21 | CRT_DIR=$(pwd) 22 | VERIFY_TEMP=$(mktemp -d 2>/dev/null || mktemp -d -t k8s-community.XXXXXX) 23 | WORKING_DIR="${VERIFY_TEMP}/src/testgendocs" 24 | GOPATH="${VERIFY_TEMP}" 25 | mkdir -p "${WORKING_DIR}" 26 | 27 | function cleanup { 28 | rm -rf "${VERIFY_TEMP}" 29 | } 30 | trap cleanup EXIT 31 | 32 | git archive --format=tar "$(git write-tree)" | (cd "${WORKING_DIR}" && tar xf -) 33 | 34 | cd "${WORKING_DIR}" 35 | make 1>/dev/null 36 | 37 | mismatches=0 38 | break=$(printf "=%.0s" $(seq 1 68)) 39 | 40 | for file in $(ls ${CRT_DIR}/sig-*/README.md ${CRT_DIR}/wg-*/README.md ${CRT_DIR}/sig-list.md ${CRT_DIR}/OWNERS_ALIASES); do 41 | real=${file#$CRT_DIR/} 42 | if ! diff -q ${file} ${WORKING_DIR}/${real} &>/dev/null; then 43 | echo "${file} does not match ${WORKING_DIR}/${real}"; 44 | mismatches=$((mismatches+1)) 45 | fi; 46 | done 47 | 48 | if [[ ${mismatches} -gt "0" ]]; then 49 | echo "" 50 | echo "${break}" 51 | noun="mismatch was" 52 | if [ ${mismatches} -gt "0" ]; then 53 | noun="mismatches were" 54 | fi 55 | echo "${mismatches} ${noun} detected." 56 | echo "Do not manually edit sig-list.md or README.md files inside the sig folders." 57 | echo "Instead make your changes to sigs.yaml and then run \`make\`."; 58 | echo "${break}" 59 | exit 1; 60 | fi 61 | 62 | exit 0 63 | -------------------------------------------------------------------------------- /events/elections/2017/dougdavis_bio.md: -------------------------------------------------------------------------------- 1 | # Doug Davis 2 | 3 | - Github: [@duglin](https://github.com/duglin) 4 | - Works for: IBM 5 | 6 | ## Background 7 | 8 | I've been working on open source projects, and standards, for about 17 years, 9 | starting with being a co-initiator of the Apache Axis project; working on 10 | WS-* related projects and specifications, OpenStack, CloudFoundry, Docker 11 | and now Kubernetes, including as a co-lead of the Service-Catalog Incubator. 12 | I also founded the Web Services Testing Forum, a consortium of Web Service 13 | providers and consumers designed for interop testing of SOAP/WS-* 14 | specifications, as well as the [soaphub](http://soaphub.org) on-line 15 | collaboration chat tool used by several communities. 16 | 17 | Throughout this time the importance of an open, fair and streamlined 18 | collaboration process has really been a center piece of my activities and 19 | goals for these projects. 20 | 21 | ## Steering Committee 22 | 23 | The stated scope of the Steering Committee focuses on helping the 24 | Kubernetes community define and optimize many of the (sometimes less than 25 | glamorous, but necessary) processes and infrastructure that's critical 26 | to keeping a community like Kubernetes healthy and successful. 27 | 28 | Kubernetes, as one of the fastest growing OSS projects, needs to navigate 29 | and manage the complexities associated with this explosive growth very 30 | carefully. The importance of balancing the need for continued enhancements, 31 | managing stability of the code base, all while ensuring the community of 32 | developers and users feel their contributions (from code, issues and feedback) 33 | are welcome, respected and addressed in a timely fashion can not 34 | be understated. This will require people who can consider the challenges 35 | from multiple perspective, not just from a developer's. 36 | 37 | I believe that my background in the open communities I've been involved with 38 | have given me a good perspective on what works, what doesn't and which might 39 | be best for an organization like Kubernetes. 40 | 41 | -------------------------------------------------------------------------------- /events/elections/2017/vote_for_justinsb.md: -------------------------------------------------------------------------------- 1 | ## Vote for justinsb! 2 | 3 | You can see my full "manifesto" [here](https://groups.google.com/d/msg/kubernetes-dev/YawXYxGHWEg/IlLN-iD6CgAJ); we've been asked to provide a shorter summary here. 4 | 5 | This election is critical. The steering committee is not an honorary position; 6 | it has effectively unlimited powers. Serving is a duty, not a privilege, and I 7 | humbly ask for your vote. 8 | 9 | --- 10 | 11 | I have been involved with Kubernetes since before 1.0, primarily on AWS support 12 | (I am a lead of sig-aws), but also contributed the original multi-zone & 13 | NodePort support. I also started the kops project, to produce an open-source 14 | and consistent Kubernetes installation tool. I'm an independent, working with 15 | Kubernetes in my day job but not employed to contribute to it, so I contribute 16 | instead where I see a problem or an unmet need. 17 | 18 | If elected, I will serve wearing my own two hats: that of a developer on 19 | the project contributing because it is a positive personal experience, and that 20 | of an end-user of Kubernetes valuing a stable and straightforward product. 21 | 22 | I believe I bring particularly strong experience on non-GCE, non-Redhat 23 | platforms, and on the realities of maintaining projects outside the core repo. 24 | I think these are likely to be some of the most challenging areas for the 25 | steering committee. 26 | 27 | ## My manifesto: 28 | 29 | (Abbreviated from [here](https://groups.google.com/d/msg/kubernetes-dev/YawXYxGHWEg/IlLN-iD6CgAJ) ) 30 | 31 | * Reach decisions quickly & consistently; communicate them clearly. 32 | 33 | * Value a clear and efficient developer process. 34 | 35 | * Empower the release team with the goal of producing a more stable release. 36 | 37 | * Figure out how to delegate to SIGs without creating fiefdoms. 38 | 39 | * Streamline our processes. 40 | 41 | * Promote experimentation with alternative processes amongst our many projects, 42 | balancing against the need for a consistent experience, allow the best approaches to "bubble-up". 43 | 44 | -------------------------------------------------------------------------------- /events/elections/2017/adnanabdulhussein_bio.md: -------------------------------------------------------------------------------- 1 | # Adnan Abdulhussein 2 | 3 | - GitHub/Slack/Twitter: @prydonius 4 | - Email: adnan@bitnami.com 5 | 6 | ## Background 7 | 8 | I joined the Kubernetes community in 2016, and have contributed in a number of 9 | capacities since: 10 | 11 | - Core contributor of Helm 12 | - Co-leading the Kubernetes Charts project 13 | - Kicked off the Helm incubation process and community docs 14 | - Co-leading SIG Apps 15 | - Regularly speaking and advocating for Kubernetes 16 | 17 | Prior to my involvement in Kubernetes, I have been an active maintainer of 18 | Bitnami's open source container images. My work at Bitnami is heavily focused on 19 | making containers and Kubernetes both accessible and easy to use. 20 | 21 | I am honoured to be amongst the amazing group of people nominated for the 22 | Steering Committee. If elected, my goal will be to help Kubernetes grow into a 23 | rich and diverse community. 24 | 25 | ## Where I see myself contributing 26 | 27 | As someone who isn't completely focused on Kubernetes core, I think an important 28 | part of the project is the ecosystem around it. I am deeply interested in being 29 | part of discussions, as part of the Steering Committee, to define the vision of 30 | the project, and to decide what relevant sub-projects should be part of 31 | Kubernetes to continue building a strong ecosystem and brand. This also means 32 | making sure sub-projects have the resources they need (i.e. CI, documentation 33 | websites) to succeed and promote their roles in the overall project. 34 | 35 | The diversity and inclusivity is one of the things that I value the most about 36 | the Kubernetes community. I think it's important that we uphold these values 37 | when defining and practicing a Code of Coduct and refining the contributor 38 | experience. 39 | 40 | Another area of the Steering Commitee I'm interested in is furthering the 41 | transparency and accountability for SIGs. I believe improving the communication 42 | and enabling more knowledge sharing will empower both community and consumers. 43 | 44 | ## Where I work 45 | 46 | Bitnami 47 | -------------------------------------------------------------------------------- /mentoring/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | Title: Kubernetes Mentoring Initiative 3 | --- 4 | 5 | # Kubernetes Mentoring Initiatives 6 | 7 | This folder will be used for all mentoring initiatives for Kubernetes. 8 | 9 | --- 10 | ## Kubernetes Pilots 11 | 12 | We understand that everyone has different learning styles and we want to support as many of those as possible. Mentoring is vital to the growth of an individual and organization of every kind. For Kubernetes, the larger the project becomes, it's necessary to keep a continuous pipeline of quality contributors. 13 | 14 | *What's a Pilot?* 15 | A pilot is a Kubernetes mentor helping new and current members navigate the seas of our repos. 16 | 17 | ## Current mentoring activities: 18 | All are currently in an incubation phase. Please reach out to Paris Pittman (parispittman@google.com or Paris on Kubernetes slack channel) for more information on how to get involved. 19 | 20 | Mentors On Demand 21 | * [Meet Our Contributors](/mentoring/meet-our-contributors.md) 22 | 23 | Long Term Contributor Ladder Growth 24 | * [Group Mentoring Cohorts](/mentoring/group-mentoring.md) 25 | 26 | Students 27 | * [Google Summer of Code](google-summer-of-code.md) 28 | 29 | Groups Traditionally Underrepresented in Tech 30 | * [Outreachy](/sig-cli/outreachy.md) 31 | 32 | #### Inspiration and Thanks 33 | This is not an out of the box program but was largely inspired by the following: 34 | * [Ada Developer Academy](https://adadevelopersacademy.org/) 35 | * [Apache Mentoring Programme](https://community.apache.org/mentoringprogramme.html) 36 | * [exercism.io](https://github.com/OperationCode/exercism-io-mentoring) 37 | * [Google Summer of Code](https://developers.google.com/open-source/gsoc/) 38 | * [Outreachy](https://www.outreachy.org/) 39 | * [OpenStack Mentoring](https://wiki.openstack.org/wiki/Mentoring) 40 | 41 | Thanks to: 42 | * the many contributors who reviewed and participated in brainstorming, 43 | * founding mentees for their willingness to try this out, 44 | * founding Pilots (@chrislovecnm, @luxas, @kow3ns) 45 | 46 | We welcome PRs, suggestions, and help! 47 | -------------------------------------------------------------------------------- /events/elections/2017/mattfarina_bio.md: -------------------------------------------------------------------------------- 1 | # [Matt Farina](https://www.mattfarina.com) 2 | Technical leader, coder, author, presenter 3 | 4 | ## Governance and Organization 5 | 6 | The steering committee is [chartered](https://github.com/kubernetes/steering/blob/master/charter.md) with figuring out the governance and organization of the Kubernetes community. Matt has years of experience in both non-profit and open source organizations. He has served on the board for two non-profits along with being involved in open source projects with mature governance models (e.g., Drupal and OpenStack). 7 | 8 | Matt believes that governance should enable people to easily navigate an organization and be empowered to be part of the community. That groups within an organization, such as special interest groups (SIG) and working groups, should have clearly communicated scope. This helps everyone understand how the organization is laid out while helping to highlight gaps. 9 | 10 | He also believes in diversity. This includes diversity of ideas and uses for Kubernetes. Diversity brings out ideas that can often be missing in an echo chamber of similar people with similar uses cases. Diversity leads to a stronger Kubernetes that's more capable of meeting real world needs. 11 | 12 | Matt wants to see Kubernetes as a professional community with an enjoyable experience for both contributors and consumers. 13 | 14 | ## Technical Background 15 | 16 | Matt has been a contributor of open source for 15 years and a consumer of open source for over 20 years. In that time he has contributed to projects such as [Glide](https://glide.sh) (package manager), [Drupal](https://drupal.org), [OpenStack](https://www.openstack.org), and many others. While working in and out of open source Matt has had a focus on both software development and _user experience_. 17 | 18 | He has also authored technical books, hosted podcasts, and presented at numerous conferences. This has taught him how to clearly communicate with a wide variety of people. 19 | 20 | ## Quick Details 21 | 22 | * Co-founded and co-leads SIG Apps 23 | * Works for [Samsung SDS](https://samsung-cnct.github.io) 24 | -------------------------------------------------------------------------------- /events/elections/2017/pwittrock_bio.md: -------------------------------------------------------------------------------- 1 | # Phillip Wittrock Bio 2 | 3 | GitHub: @pwittrock 4 | 5 | ## Problem solving style 6 | 7 | - Incremental approach to problem solving 8 | - Try new things - build and iterate on minimalist solutions 9 | 10 | ## What I find important 11 | 12 | I care deeply about helping people feel positive about what they are doing and empowered to do more. 13 | Within the Kubernetes community, I would like to focus on helping ensure contributors': 14 | 15 | - time and contributions are impactful 16 | - time and contributions are recognized and appreciated 17 | - opinions are listened to and valued 18 | 19 | ## Where I see myself contributing 20 | 21 | I believe it is important for the processes for contribution and maintenance of the project 22 | to be well communicated and understood within the community. 23 | I would like to be involved in areas owned by the SC such as - helping to develop a 24 | SIG charter template, simplifying the contributor ladder, documenting resources the community has, 25 | and helping to find a home for unowned areas of the project. 26 | 27 | ## Roles held 28 | 29 | Since joining the community in 2015, I have made contributions in various roles 30 | (developer, SIG-lead, docs, release manager) across the project. Working 31 | in these capacities has given me insight into the challenges faced throughout the project. 32 | 33 | Areas of the project I have contributed to include: node, kubectl, service catalog, docs and release. 34 | 35 | ### Current SIG lead positions I hold 36 | 37 | - Co-founded SIG-cli 38 | - Co-founded SIG-release 39 | 40 | ### Emeritus SIG lead positions I have held (brief tenure) 41 | 42 | - Bootstrap SIG-contribX 43 | - Bootstrap SIG-docs 44 | 45 | ### Relevant non-technical contributions 46 | 47 | - (release) Changed management role from an individual to a team with defined roles 48 | - (release) Proposals for streamlining and automating various processes 49 | - Published community membership ladder developed from draft (draft by Brian Grant) 50 | - 1.4 release czar 51 | - Participated in 1.5, 1.6 and 1.7 releases 52 | 53 | ## Where I work 54 | 55 | Google -------------------------------------------------------------------------------- /sig-architecture/charter.md: -------------------------------------------------------------------------------- 1 | # SIG Architecture Charter 2 | 3 | This charter is a WIP. 4 | 5 | The Architecture SIG maintains and evolves the design principles of 6 | Kubernetes, and provides a consistent body of expertise necessary to 7 | ensure architectural consistency over time. 8 | 9 | The scope covers issues that span all the system's components, how 10 | they fit together, how they interact, etc. 11 | 12 | Specific areas of focus include: 13 | 14 | * Defining the scope of the Kubernetes project 15 | * [What is (and is not) Kubernetes](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/) 16 | * Maintaining, evolving, and enforcing the deprecation policy 17 | * [Deprecation policy](https://kubernetes.io/docs/reference/deprecation-policy/) 18 | * Documenting and evolving the system architecture 19 | * [Kubernetes Design and Architecture](../contributors/design-proposals/architecture/architecture.md) 20 | * Defining and driving necessary extensibility points 21 | * Establishing and documenting design principles 22 | * [Design principles](../contributors/design-proposals/architecture/principles.md) 23 | * Establishing and documenting conventions for system and user-facing APIs 24 | * [API conventions](/contributors/devel/api-conventions.md) 25 | * Developing necessary technical review processes, such as the proposal and API review processes 26 | * Driving improvement of overall code organization, including github orgs and repositories 27 | * Educating approvers/owners of other SIGs (e.g., by holding office hours) 28 | 29 | Out of scope: 30 | * Issues specific to a particular component or functional area, which would be the purview 31 | of some other SIG, except where they deviate from project-wide principles and conventions. 32 | * [Release support policy](/contributors/design-proposals/release/versioning.md) 33 | is owned by SIG Release 34 | 35 | TODO: 36 | * Formalize decision processes 37 | * Document initial reviewers and approvers 38 | * Clarify criteria for areas out of scope for the SIG 39 | * Document who owns client library, build, and release artifacts 40 | * Document who owns conformance definition, profiles, etc. 41 | -------------------------------------------------------------------------------- /sig-apps/minutes/2016-07-27.md: -------------------------------------------------------------------------------- 1 | # July 27, 2016 2 | 3 | * Intro by Matt 4 | * [Gerred Dillon](https://twitter.com/justicefries) presented a demo of [Deis](https://deis.com/) including features in the 2.2 release. 5 | * To turn an application into a container it uses Heroku buildpacks. 6 | * [slugbuilder](https://github.com/deis/slugbuilder) converts an application and buildpack into a container and puts the image into a private registry. Pod manifest, service manifest, etc are also created. 7 | * Q: Is slugbuilder a separate microservice others can use? 8 | A: Yes. It's a plugin to [builder](https://github.com/deis/builder) that can be used with other builders as well. For example, there is some way to incorporate an object store for storage of images. 9 | * Q: How does Deis use namespaces? 10 | A: There is a separate one for each application. Then other tools can deploy supporting services to the same namespace. 11 | * Q: What languages are used in Deis? 12 | A: Rails, Phoenix, Django, some PHP, and node are examples of apps today. There are currently not many Go applications. 13 | * Q: Will Deis add back-end services? 14 | A: Can't really say. They are getting plenty of requests for them. This may be a place helm will step in and be useful. 15 | * Deis 2.2 adds the ability to use Deployments which was showcased. This is optional and not the default right now. 16 | * Matt presented the results of the App Operator survey. 17 | * The raw details are available to [view or download](https://docs.google.com/spreadsheets/d/15SUL7QTpR4Flrp5eJ5TR8A5ZAFwbchfX2QL4MEoJFQ8/edit?usp=sharing). 18 | * A roll-up of some interesting points is [available]( 19 | https://docs.google.com/presentation/d/13votPnx9xKVBoQbLHz78I9EWFCosoioFqjTFeb4vB6M/edit?usp=sharing 20 | ). 21 | * The use of Kubernetes secrets was discussed. 47% of respondents use secrets. Secrets current storage mechanism is unencrypted at rest. This is a known limitation and we are waiting for some in the community to step in and provide support for systems like Hashicorp Vault or hardware security modules where appropriate. 22 | 23 | _Note, due to technical difficulties this meeting was not recorded._ 24 | -------------------------------------------------------------------------------- /committee-steering/governance/FAQ.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions 2 | 3 | ## Why the new structure? Why split the SIG Lead Role into 2 distinct roles? 4 | 5 | While developing the SIG governance requirements, 3 distinct sets of responsibilities were identified: 6 | 7 | - Setting technical direction and resolving technical discussions in subprojects of a SIG 8 | (e.g. intra-subproject escalation point) 9 | - Setting pure-technical scope across the SIG and resolving technical discussions that span subprojects 10 | (e.g. inter-subproject escalation point) 11 | - Managing the operational aspects of the SIG - defining and evolving process and structure. Identifying, or helping 12 | to identify, and defining additional SIG and subproject roles and responsibilities. 13 | 14 | While in many SIGs individuals may continue to have all 3 roles concurrently, splitting out the responsibilities 15 | into multiple roles enjoys the following advantages: 16 | 17 | - Doing so makes technical and non-technical leadership responsibilities unambiguous. Previously, the role of SIG Lead 18 | was not consistent across SIGs - in some cases it was a technical escalation point and in others the role had 19 | no ties to technical decision making. Calling out these responsibilities specifically makes the responsibilities 20 | of the roles clear across SIGs. 21 | - Doing so provides a more diverse set of opportunities for community members to take on leadership roles. The 22 | new structure explicitly provides room and roles for both pure technical leadership AND leadership focused on 23 | critical non-technical work. Being the most senior technical contributor will no longer be a requirement 24 | for taking on a leadership role in non-technical capacities. Likewise, the most senior technical contributors 25 | may now be documented as the escalation points for technical issues irrespective of their non-technical 26 | responsibilities. 27 | - Doing so provides SIG Leads an opportunity to scale themselves by sharing or transitioning parts of their workload 28 | to other members of the community that may be interested in taking on either pure-technical or non-technical 29 | leadership opportunities. 30 | -------------------------------------------------------------------------------- /events/elections/2017/rhirschfeld_bio.md: -------------------------------------------------------------------------------- 1 | # Rob Hirschfeld Bio 2 | 3 | * GitHub: [@zehicle](https://github.com/zehicle) 4 | * Twitter: [@zehicle](https://twitter.com/zehicle) 5 | * Blog: [RobHirschfeld.com](http://robhirschfeld.com) 6 | * I work at [RackN.com](https://RackN.com) and live in Austin, Texas. 7 | 8 | ## Governance Perspective: it's about people, not tech 9 | 10 | Open source infrastructure automation is a critical foundation for the Internet and, thus, advancing society as a whole. In a very practical way, protecting open software is essential to building a better world. I am seeking a seat on the Kubernetes Steering Committee because I bring special perspectives to governing the project. 11 | 12 | ## Leadership: Technical, Open Source and Business 13 | 14 | I’ve demonstrated practical and relevant experience to building open governance at this stage in our development. 15 | 16 | * **Open source project founder ([Digital Rebar](http://rebar.digital), Crowbar)**: I know the challenges of sustaining contribution 17 | * **Operator**: I’ve run infrastructure and founded the SIG Cluster Ops group to give a voice for operators. I focus professionally on helping promote SRE and DevOps practices. 18 | * **Founding OpenStack board member (4 terms)**: I’ve built open governance processes and done the hard work to build conformance and core definition (#DefCore) patterns. 19 | * **Start-up founder (RackN.com)**: I’ve done every role and am willing to get my hands dirty. I understand the needs for small companies trying to support large projects. 20 | * **Dell Executive**: I’ve been part of large organizations and know how to explain things in corporate speak to protect project interests. 21 | * **Technologist**: I still write code and build applications as needed so I understand the very specific concerns of delivering working platforms. 22 | 23 | ## TL;DR: Collaborative and Principled 24 | 25 | Most importantly, I’m collaborative by nature. I know how to stand my ground and fight without being a jerk or excluding people. I can be one of the advocates that the Kubernetes community needs as we build formal governance. 26 | 27 | _Governance means being able to say no and keep consensus._ 28 | -------------------------------------------------------------------------------- /sig-contributor-experience/migrated-from-wiki/effective-reviewable.md: -------------------------------------------------------------------------------- 1 | *Or, one weird trick to make Reviewable awesome* 2 | 3 | The Kubernetes team is still new to _Reviewable_. As you discover new cool features and workflows, add them here. Once we have built up a good number of tricks we can reorganize this list. 4 | 5 | - Hold off on publishing comments (using the "Publish" button) until you have completed your review. [(source)](@pwittrock) 6 | - When leaving comments, select a "disposition" (the button with your profile picture) to indicate whether the comment requires resolution, or is just advisory and hence requires no response. [(source)](@pwittrock) 7 | - Change a comment's "disposition" to "close" those to which the author didn't respond explicitly but did address with satisfactory changes to the code. Otherwise, the comment hangs out there awaiting a response; in contrast to GitHub's review system, _Reviewable_ doesn't consider a change to the target line to be a sufficient indicator of resolution or obsolescence, which is a safer design. Use the <kbd>y</kbd> to acknowledge the current comment, which indicates that no further response is necessary. 8 | - To "collapse" a whole file in the multi-file view, click the rightmost value in the revision range control. This is effectively saying, "Show no diffs." 9 | - Use the red/green "eye" icon to indicate completion of and to keep track of which files you have reviewed. The <kbd>x</kbd> keyboard shortcut toggles the completion status of the file currently focused in the status bar across the top. 10 | - Use the <kbd>p</kbd> and <kbd>n</kbd> keys to navigate to the previous and next unreviewed file—that is, those whose status is a red circle with a crossed white eye icon, meaning incomplete, as opposed to those with a green circle with a white eye, meaning complete. 11 | - Use the <kbd>j</kbd> and <kbd>k</kbd> keys to navigate to the previous and next comment. Use <kbd>S-j</kbd> and <kbd>S-k</kbd> to navigate between the previous and next _unaddressed_ comment. Usually as the reviewer, you use the latter to go back and check on whether your previous suggestions were addressed. 12 | - Reply with `+lgtm` to apply the "LGTM" label directly from _Reviewable_. -------------------------------------------------------------------------------- /sig-ibmcloud/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # IBMCloud Special Interest Group 10 | 11 | A Special Interest Group (SIG) for building, deploying, maintaining, supporting, and using Kubernetes on IBM Public and Private Clouds. 12 | 13 | ## Meetings 14 | * Regular SIG Meeting: [Wednesdays at 14:00 EST](https://zoom.us/j/9392903494) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=14:00&tz=EST). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1qd_LTu5GFaxUhSWTHigowHt3XwjJVf1L57kupj8lnwg/edit). 16 | 17 | ## Leadership 18 | 19 | ### Chairs 20 | The Chairs of the SIG run operations and processes governing the SIG. 21 | 22 | * Khalid Ahmed (**[@khahmed](https://github.com/khahmed)**), IBM 23 | * Richard Theis (**[@rtheis](https://github.com/rtheis)**), IBM 24 | * Sahdev Zala (**[@spzala](https://github.com/spzala)**), IBM 25 | 26 | ## Contact 27 | * [Slack](https://kubernetes.slack.com/messages/sig-ibmcloud) 28 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-ibmcloud) 29 | * [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fibmcloud) 30 | 31 | ## GitHub Teams 32 | 33 | The below teams can be mentioned on issues and PRs in order to get attention from the right people. 34 | Note that the links to display team membership will only work if you are a member of the org. 35 | 36 | The google groups contain the archive of Github team notifications. 37 | Mentioning a team on Github will CC its group. 38 | Monitor these for Github activity if you are not a member of the team. 39 | 40 | | Team Name | Details | Google Groups | Description | 41 | | --------- |:-------:|:-------------:| ----------- | 42 | | @kubernetes/sig-ibmcloud-misc | [link](https://github.com/orgs/kubernetes/teams/sig-ibmcloud-misc) | [link](https://groups.google.com/forum/#!forum/kubernetes-sig-ibmcloud-misc) | General Discussion | 43 | 44 | <!-- BEGIN CUSTOM CONTENT --> 45 | 46 | <!-- END CUSTOM CONTENT --> 47 | -------------------------------------------------------------------------------- /contributors/devel/cherry-picks.md: -------------------------------------------------------------------------------- 1 | # Overview 2 | 3 | This document explains how cherry picks are managed on release 4 | branches within the Kubernetes projects. 5 | 6 | ## Prerequisites 7 | * [Contributor License Agreement](http://git.k8s.io/community/CLA.md) 8 | is considered implicit for all code within cherry-pick pull requests, 9 | ***unless there is a large conflict***. 10 | * A pull request merged against the master branch. 11 | * [Release branch](https://git.k8s.io/release/docs/branching.md) exists. 12 | * The normal git and GitHub configured shell environment for pushing 13 | to your kubernetes `origin` fork on GitHub and making a pull request 14 | against a configured remote `upstream` that tracks 15 | "https://github.com/kubernetes/kubernetes.git", including 16 | `GITHUB_USER`. 17 | * Have `hub` installed, which is most easily installed via `go get 18 | github.com/github/hub` assuming you have a standard golang development 19 | environment. 20 | 21 | ## Initiate a Cherry Pick 22 | * Run the [cherry pick script](https://git.k8s.io/kubernetes/hack/cherry_pick_pull.sh). 23 | This example applies a master branch PR #98765 to the remote branch 24 | `upstream/release-3.14`: `hack/cherry_pick_pull.sh upstream/release-3.14 25 | 98765` 26 | * Your cherrypick PR targeted to the release branch will immediately get the 27 | `do-not-merge/cherry-pick-not-approved` label. The release branch owner 28 | will triage PRs targeted to the branch. Normal rules apply for code merge. 29 | * Reviewers `/lgtm` and owners `/approve` as they deem appropriate. 30 | * The approving release branch owner is responsible for applying the 31 | `cherrypick-approved` label. 32 | 33 | ## Cherry Pick Review 34 | 35 | Cherry pick pull requests are reviewed differently than normal pull requests. In 36 | particular, they may be self-merged by the release branch owner without fanfare, 37 | in the case the release branch owner knows the cherry pick was already 38 | requested - this should not be the norm, but it may happen. 39 | 40 | ## Searching for Cherry Picks 41 | 42 | See the [cherrypick queue dashboard](http://cherrypick.k8s.io/#/queue) for 43 | status of PRs labeled as `cherrypick-candidate`. 44 | -------------------------------------------------------------------------------- /events/elections/2017/derekcarr_bio.md: -------------------------------------------------------------------------------- 1 | # Derek Carr 2 | 3 | - GitHub: @derekwaynecarr 4 | - Employer: Red Hat 5 | 6 | ## Roles Held 7 | 8 | - Co-founder, lead: sig-node, wg-resource-management 9 | - Participate: api-machinery, autoscaling, federation, scheduling, 10 | service-catalog 11 | 12 | ## About me 13 | 14 | I joined in 2014 as an early external contributor. After the first developer 15 | summit, I realized I had a lot to learn from the experience of others. My first 16 | PR enabled people to contribute to the project by running Kubernetes in a VM. 17 | Mentors in the community helped multiply the quality of my contributions. With 18 | their help, I designed and implemented namespaces, quota, limits, and much of 19 | the supporting internal machinery like admission control, indexers, and clients 20 | prior to the 1.0 release. 21 | 22 | As the project grew, SIGs developed to support specialized collaboration. I 23 | co-lead SIG node and advocate for expanded workload support and improvements to 24 | node reliability. To improve cross-SIG collaboration, I co-founded the Resource 25 | Management Working Group to define a multi-release roadmap across SIGs (node, 26 | scheduling, storage, etc). The cross-SIG working group concept has been adopted 27 | across the community. I participate in multiple incubator projects with code 28 | and coaching on technology and process. As every maintainer acknowledges, it is 29 | impossible to know everything about Kubernetes. I prioritize mentoring others to 30 | help them grow their scope and sustain the project. 31 | 32 | My experience reflects both a breadth and depth of commitment across Kubernetes 33 | that would benefit the committee. I have a pragmatic approach to problem 34 | solving that builds from the expertise of others and adopts minimal solutions 35 | that have the best potential outcome. I iterate and improve. As a member of 36 | the community, I hope the steering committee adheres to the same general 37 | approach. 38 | 39 | ## Where I see myself contributing 40 | 41 | - Responsibly grow contributor pool across all disciplines 42 | - Clarify scope, structure, and responsibilities of SIGs and roles within 43 | - Enhance Code of Conduct to nurture an inclusive, diverse, and open community -------------------------------------------------------------------------------- /events/2016/developer-summit-2016/KubDevSummitVoting.md: -------------------------------------------------------------------------------- 1 | ###Kubernetes Developer's Summit Discussion Topics Voting 2 | ### 3 | A voting poll for discussion topic proposals has been created, and the link to the poll can be found [here][poll]. 4 | 5 | The poll will close on 10/07/16 at 23:59:59 PDT. 6 | 7 | #### How Does it Work? 8 | #### 9 | The voting uses the Condorcet method, which relies on relative rankings to pick winners. You can read more about the Condorcet method and the voting service we're using on the [CIVS website][civs]. 10 | 11 | There are 27 topics to choose from, and you will rank them from 1 (favorite) to 27 (least favorite). You can also mark "no opinion" on topics that you don't wish to include in the ranking. 12 | 13 | The poll on CIVS has just the topic titles for ease of viewing. For topic descriptions, please see this [spreadsheet][topics]. The topic order on the voting service should mirror the order on the spreadsheet. 14 | 15 | You will note the message saying "*Only the 15 favorite choices will win the poll*". CIVS requires a number be selected for winners, and we have arbitrarily chosen 15. The final schedule may include more or less than 15 of the submitted topics. 16 | 17 | ##### A Small Request 18 | ##### 19 | 20 | In order to make the poll accessible via URL, it has to be made "public". This means than any unique IP address can vote, which can be easily exploited for multiple votes. 21 | 22 | We fully expect the community to behave with sportsmanship and only vote once, and as such we almost didn't bring this concern up to begin with. However, we have chosen to explicitly address it, in order to reiterate the importance of everyone's voice receiving equal weight in a community-driven event. 23 | 24 | #### After the Poll 25 | #### 26 | A schedule will be made from the winning topics with 27 | some editorial license, and the schedule will be announced to the group 28 | at least a week before the event. 29 | 30 | [//]: # (Reference Links) 31 | [civs]: <http://civs.cs.cornell.edu/> 32 | [poll]: <http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_9ef4ac5e58c4cab1&akey=7cc2652f9715b525> 33 | [topics]: <https://docs.google.com/spreadsheets/d/1bmp6uLG8H32MVz02-zsieeKKZDZITw-8B6UjOaNTXOA/edit?usp=sharing> -------------------------------------------------------------------------------- /sig-cli/migrated-from-wiki/contributor-guide-building-your-kubernetes-tool.md: -------------------------------------------------------------------------------- 1 | # Client Tool Release Publishing Guidelines 2 | 3 | Projects should publish releases for client side tools. 4 | 5 | ## Go Projects 6 | 7 | ### Static Linking 8 | 9 | See [Go executables are statically linked, except when they are not](http://matthewkwilliams.com/index.php/2014/09/28/go-executables-are-statically-linked-except-when-they-are-not/). 10 | 11 | 12 | - How to compile a statically linked binary: `go` file must be compiled without cgo support. 13 | 14 | ```sh 15 | # Disable cgo 16 | export CGO_ENABLED=0 17 | ``` 18 | 19 | - How to check if a binary is statically linked 20 | 21 | ```sh 22 | # List dynamic dependencies (shared libraries): 23 | # 1. if it's dynamically linked, you'll see 24 | $ ldd <your_tool> 25 | linux-vdso.so.1 => (0x00007ffe937ea000) 26 | libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0a7dae5000) 27 | libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0a7d720000) 28 | /lib64/ld-linux-x86-64.so.2 (0x00007f0a7dd03000) 29 | # 2. if it's statically linked, you'll see 30 | $ ldd <your_tool> 31 | not a dynamic executable 32 | 33 | # Recognize the type of data in a file 34 | # 1. if it's dynamically linked, you'll see 35 | $ file <your_tool> 36 | /usr/local/your_tool: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=86c6d2ff21297a06cc7319244f35e2671612beae, not stripped 37 | # 2. if it's statically linked, you'll see 38 | $ file <your_tool> 39 | /usr/local/your_tool: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped 40 | ``` 41 | 42 | ### Targets 43 | Build your release binary for the following targets: 44 | 45 | - darwin-amd64 46 | - linux-386 47 | - linux-amd64 48 | - linux-armv6l 49 | - linux-ppc64le 50 | - windows-amd64 51 | 52 | ### Packaging 53 | 54 | Package binaries into a tar.gz file and make available on GitHub releases page. 55 | 56 | # Service Side Release Publishing Guidelines 57 | 58 | ### Packaging 59 | 60 | Server side programs should be packaged into container images. Stateless services should be run as Deployments (as opposed to Replication Controllers). 61 | 62 | # Documentation Guidelines 63 | 64 | TODO: Write this 65 | -------------------------------------------------------------------------------- /events/elections/2017/idvoretskyi_bio.md: -------------------------------------------------------------------------------- 1 | # Ihor Dvoretskyi 2 | 3 | Twitter: https://twitter.com/idvoretskyi 4 | 5 | GitHub: https://github.com/idvoretskyi 6 | 7 | Anywhere else: @idvoretskyi 8 | 9 | ## About me 10 | 11 | I'm a [Developer Advocate for Cloud Native Computing Foundation](https://www.cncf.io/blog/2017/09/18/meet-cncfs-newest-developer-advocate/), open source lover, passionate about the technologies and open source adoption; with the deep technical background, together with program and product management experience in the open source world. In a previous life, I’ve been a System Administrator and DevOps Engineer, passionate about the Cloud technologies. Later, I’ve joined Mirantis, one of the largest players in the OpenStack world, where I’ve started my collaboration with OpenStack community. 12 | 13 | I've enjoyed Kubernetes since the early days. I've started researching it in mid-2014 when it was publicly announced; I've been using for my projects it in mid-2015 when it had reached its 1.0 milestone; and I've started contributing (as an individual contributor) to Kubernetes in late-2015, when I felt that my knowledge and experience might be useful for the project. 14 | 15 | As a Kubernetes Community member, I'm mostly focused on Product- and Project-management areas, with the primary interest in the features and roadmap scope. 16 | For Kubernetes 1.3, 1.4 and 1.5 I've been unofficially involved in the release process with the features tracking and management. 17 | Since Kubernetes 1.6 release cycle (and continued these efforts during 1.7 and 1.8), I've joined the release teams as the release manager, responsible for the features. 18 | Finally, I've been one of the co-founders of [SIG-PM](https://github.com/kubernetes/community/tree/master/sig-product-management), responsible for managing Kubernetes-as-a-project and Kubernetes-as-a-product. 19 | 20 | Besides that, as an individual with OpenStack community background, I'm co-leading [SIG-OpenStack](https://github.com/kubernetes/community/blob/master/sig-openstack/README.md), building the relationships between two major open source communities. 21 | 22 | ## What's next? 23 | 24 | As a vendor-neutral Kubernetes contributor, I'm going to continue my work on enhancing Kubernetes as an open source project, technology stack, and one of the largest open source communities in the world. 25 | -------------------------------------------------------------------------------- /contributors/devel/staging.md: -------------------------------------------------------------------------------- 1 | # Staging Directory and Publishing 2 | 3 | The [staging/ directory](https://git.k8s.io/kubernetes/staging) of Kubernetes contains a number of pseudo repositories ("staging repos"). They are symlinked into Kubernetes' [vendor/ directory](https://git.k8s.io/kubernetes/vendor/k8s.io) for Golang to pick them up. 4 | 5 | We publish the staging repos using the [publishing bot](https://git.k8s.io/publishing-bot). It uses `git filter-branch` essentially to [cut the staging directories into separate git trees](https://de.slideshare.net/sttts/cutting-the-kubernetes-monorepo-in-pieces-never-learnt-more-about-git) and pushing the new commits to the corresponding real repositories in the [kubernetes organization on Github](https://github.com/kubernetes). 6 | 7 | The list of staging repositories and their published branches are listed in [publisher.go inside of the bot](https://git.k8s.io/publishing-bot/cmd/publishing-bot/publisher.go). Though it is planned to move this out into the k8s.io/kubernetes repository. 8 | 9 | At the time of this writing, this includes the branches 10 | 11 | - master, 12 | - release-1.8 / release-5.0, 13 | - and release-1.9 / release-6.0 14 | 15 | of the following staging repos in the k8s.io org: 16 | 17 | - api 18 | - apiextensions-apiserver 19 | - apimachinery 20 | - apiserver 21 | - client-go 22 | - code-generator 23 | - kube-aggregator 24 | - metrics 25 | - sample-apiserver 26 | - sample-controller 27 | 28 | Kubernetes tags (e.g., v1.9.1-beta1) are also applied automatically to the published repositories, prefixed with kubernetes- (e.g., kubernetes-1.9.1-beta1). The client-go semver tags (on client-go only!) including release-notes are still done manually. 29 | 30 | The semver tags are still the (well tested) official releases. The kubernetes-1.x.y tags have limited test coverage (we have some automatic tests in place in the bot), but can be used by early adopters of client-go and the other libraries. Moreover, they help to vendor the correct version of k8s.io/api and k8s.io/apimachinery. 31 | 32 | If further repos under staging are need, adding them to the bot is easy. Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS). 33 | 34 | Currently, the bot is hosted on the CI cluster of Redhat's OpenShift (ready to be moved out to a public CNCF cluster if we have that in the future). 35 | -------------------------------------------------------------------------------- /contributors/guide/contributor-cheatsheet.md: -------------------------------------------------------------------------------- 1 | # Kubernetes Cheat Sheet 2 | 3 | A list of common resources when contributing to Kubernetes. 4 | 5 | | Repo | PRs | Issues | Notes | 6 | | ---- | --- | ------ | ----- | 7 | | [Kubernetes](https://github.com/kubernetes/kubernetes) | [PRs](https://github.com/kubernetes/kubernetes/pulls) | [Issues](https://github.com/kubernetes/kubernetes/issues) | [Meeting Notes](http://bit.ly/kubenotes) 8 | | [Community](https://github.com/kubernetes/community) | [PRs](https://github.com/kubernetes/community/pulls) | [Issues](https://github.com/kubernetes/community/issues) | 9 | | [Docs](https://github.com/kubernetes/website) | [PRs](https://github.com/kubernetes/website/pulls) | [Issues](https://github.com/kubernetes/website/issues) 10 | 11 | ## Getting Started 12 | 13 | - [Contributor Guide](https://github.com/kubernetes/community/blob/master/contributors/guide/README.md) 14 | 15 | ## Workflow 16 | 17 | - [Gubernator Dashboard - k8s.reviews](https://k8s-gubernator.appspot.com/pr) 18 | - [Submit Queue](https://submit-queue.k8s.io) 19 | - [Bot commands](https://go.k8s.io/bot-commands) 20 | - [Release Buckets](http://gcsweb.k8s.io/gcs/kubernetes-release/) 21 | - Developer Guide 22 | - [Cherry Picking Guide](/contributors/devel/cherry-picks.md) - [Queue](http://cherrypick.k8s.io/#/queue) 23 | - [https://k8s-code.appspot.com/](https://k8s-code.appspot.com/) - Kubernetes Code Search, maintained by [@dims](https://github.com/dims) 24 | 25 | 26 | ## SIGs and Working Groups 27 | 28 | - [Master SIG list](/sig-list.md#master-sig-list) 29 | 30 | ## Community 31 | 32 | - [Calendar](https://calendar.google.com/calendar/embed?src=cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com) 33 | - [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) 34 | - [kubernetes-users](https://groups.google.com/forum/#!forum/kubernetes-users) 35 | - [Slack channels](http://slack.k8s.io/) 36 | - [StackOverflow](https://stackoverflow.com/questions/tagged/kubernetes) 37 | - [YouTube Channel](https://www.youtube.com/c/KubernetesCommunity/) 38 | 39 | ## Tests 40 | 41 | - [Current Test Status](https://prow.k8s.io/) 42 | - [Aggregated Failures](https://storage.googleapis.com/k8s-gubernator/triage/index.html) 43 | - [Test Grid](https://k8s-testgrid.appspot.com/) 44 | 45 | ## Other 46 | 47 | - [Developer Statistics](https://k8s.devstats.cncf.io) 48 | -------------------------------------------------------------------------------- /events/2016/Kubernetes_1st_Bday.md: -------------------------------------------------------------------------------- 1 | # Kubernetes 1st Birthday Announcement 2 | 3 | Dear Kubernauts, 4 | 5 | Happy birthday! The Kubernetes community is celebrating the first anniversary for the v1.0 release on July 21st, 2016. We are reaching out to you as the chief point(s) of contact for your local Kubernetes meetup to encourage you to throw a Kubernetes birthday party! 6 | 7 | This is very exciting for the Kubernetes community, and we are happy to support your party planning efforts. We have swag we can provide (including awesome Kubernetes party hats!) and we will do our best to support your other endeavors. 8 | 9 | Since the actual anniversary is on July 21st, that date will likely be receiving the majority of the press and social media attention. But, by no means do you need to force your meetup to happen on July 21st; any time in late July or early August works great! We’re just hoping to get more people excited about Kubernetes and get users and developers meeting across the world. 10 | 11 | You may additionally be interested in joining the [Kubernetes Meetup leads mailing list](https://groups.google.com/forum/#!members/kubernetes-meetup-leads) where you can meet other organizers and swap tips. The [CNCF](https://cncf.io/community) is also working with Kubernetes meetups to offer support for things like Meetup.com fees and events, including financial support up to $250 for some official meetups. For more information on that effort, you can contact [Chris Aniszczyk](mailto:caniszczyk@linuxfoundation.org) and [Brett Preston](mailto:bpreston@linuxfoundation.org). 12 | 13 | Please contact us via [this Google form](https://docs.google.com/forms/d/1B17ckkz-FYEFhkQ2ZD8PZBH1ZnSCdpS366lB3a6MAtE/viewform) with any questions / requests / suggestions for your meetup. Alternatively, you can reach out to us directly (czahedi@google.com and sarahnovotny@google.com). We hope to hear from you soon! 14 | 15 | Lastly, if you know other people working with Kubernetes, please send this invitation their way! It could be a great chance for them to plug into a Meetup.com group or the mailing list above. 16 | 17 | And lest we forget, I’m Cameron Zahedi. I’ll be working with Sarah on her Kubernetes community endeavors, and I’m happy to help (or find the right person to help!) wherever possible. 18 | 19 | Cheers, 20 | 21 | Cameron and Sarah (on behalf of the Kubernetes Community.) 22 | 23 | 24 | -------------------------------------------------------------------------------- /vendor/github.com/client9/misspell/legal.go: -------------------------------------------------------------------------------- 1 | // Package misspell corrects commonly misspelled English words in source files. 2 | package misspell 3 | 4 | // Legal provides licensing info. 5 | const Legal = ` 6 | Execept where noted below, the source code for misspell is 7 | copyright Nick Galbreath and distribution is allowed under a 8 | MIT license. See the following for details: 9 | 10 | * https://github.com/client9/misspell/blob/master/LICENSE 11 | * https://tldrlegal.com/license/mit-license 12 | 13 | Misspell makes uses of the Golang standard library and 14 | contains a modified version of Golang's strings.Replacer 15 | which are covered under a BSD License. 16 | 17 | * https://golang.org/pkg/strings/#Replacer 18 | * https://golang.org/src/strings/replace.go 19 | * https://github.com/golang/go/blob/master/LICENSE 20 | 21 | Copyright (c) 2009 The Go Authors. All rights reserved. 22 | 23 | Redistribution and use in source and binary forms, with or without 24 | modification, are permitted provided that the following conditions are 25 | met: 26 | 27 | * Redistributions of source code must retain the above copyright 28 | notice, this list of conditions and the following disclaimer. 29 | * Redistributions in binary form must reproduce the above 30 | copyright notice, this list of conditions and the following disclaimer 31 | in the documentation and/or other materials provided with the 32 | distribution. 33 | * Neither the name of Google Inc. nor the names of its 34 | contributors may be used to endorse or promote products derived from 35 | this software without specific prior written permission. 36 | 37 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 38 | "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 39 | LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 40 | A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 41 | OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 42 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 43 | LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 44 | DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 45 | THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 46 | (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 47 | OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 48 | ` 49 | -------------------------------------------------------------------------------- /events/elections/2017/aaronschlesinger_bio.md: -------------------------------------------------------------------------------- 1 | # Aaron Schlesinger 2 | 3 | - Github: [arschles](https://github.com/arschles) 4 | - Twitter: [@arschles](https://twitter.com/arschles) 5 | 6 | # About 7 | 8 | I'm a Sr. Software Engineer, Microsoft Azure Containers Group. 9 | 10 | I'm a passionate engineer, teacher and leader with over 10 years software engineering and 11 | architecture experience. 12 | 13 | I believe that Kubernetes will truly succeed when we improve the developer and 14 | user experience. 15 | 16 | # Experience 17 | 18 | I've made contributions to [helm](https://github.com/kubernetes/helm), [helm charts](https://github.com/kubernetes/charts), [minikube](https://github.com/kubernetes/minikube), [service-catalog](https://github.com/kubernetes-incubator/service-catalog) and I am a co-lead of SIG-Service-Catalog. 19 | 20 | Outside of Kubernetes, I've spent over 10 years speaking at conferences, teaching Go & Scala, 21 | building large systems, sitting on standards bodies, and contributing to other open source 22 | projects. 23 | 24 | # Promises 25 | 26 | Here are my promises to the community should I be elected to the committee. 27 | 28 | Above all, I want Kubernetes to be a nice place to work. That means: 29 | 30 | - Engineers can build or improve things easily 31 | - Engineers have clear expectations how & (generally) when they will get feedback on their work 32 | - Engineers get constructive feedback on their work 33 | - Everyone is treated with respect, and can resolve interpersonal problems amicably 34 | 35 | Holistically, most of these points are true most of the time, but Kubernetes is growing so 36 | fast and is so diverse that all of them are not always guaranteed right now. 37 | 38 | I realize no community can achieve everything all the time, but I believe we can do better 39 | together. 40 | 41 | I want to improve the following immediately: 42 | 43 | - Improve user _and_ developer documentation 44 | - Create clearer guidelines on how reviews should happen 45 | - Clarify how to rise as a contributor 46 | 47 | Additionally, I'll contribute best to the committee as a representative of end users 48 | and developers. 49 | 50 | I will keep the same promises in the steering committee as I do in SIG-Service-Catalog: 51 | 52 | - **I will always solicit user and developer experiences before making decisions** 53 | - **I will always tackle user and developer problems before anything else** 54 | -------------------------------------------------------------------------------- /project-managers/README.md: -------------------------------------------------------------------------------- 1 | ## Kubernetes PM 2 | 3 | kubernetes-pm is a github team that will help to manage and maintain the project in ways other than just writing code. Specifically, members of the kubernetes-pm team are 4 | expected to: 5 | 6 | * Add/change routing labels to issues (eg: area/foo, kind/foo, priority/foo, sig/foo) 7 | * Apply release-note labels to PRs (until that is automated or eliminated) 8 | * Set the milestone on a PR or issue 9 | * Assign issues to the correct people for immediate triage/work 10 | * Assign PRs to be reviewed by the correct people 11 | * Close duplicate, stale, misplaced issues 12 | * Close support issues, with a redirect to Stack Overflow 13 | 14 | They should **NOT**: 15 | 16 | * Manually apply merge labels to PRs (lgtm, approved) or press merge button 17 | * Apply priority labels to PRs 18 | * Apply cherrypick labels to PRs 19 | * Edit text of other people's PRs and issues, including deleting comments 20 | * Modify anyone else's release note 21 | * Create, edit, delete labels 22 | * Create, edit, close, delete milestones 23 | * Create, edit, delete releases 24 | * Create, edit, delete PR statuses 25 | * Edit wiki 26 | 27 | Abuse and misuse will result in prompt removal from the Project Managers group and loss of privileges. 28 | 29 | ## Joining the group 30 | 31 | The following is the provisional process for adding people to the group: 32 | 33 | 1. Join kubernetes-sig-contribex at googlegroups.com. Send a message to that group that states: 34 | 1. Your github id. 35 | 1. What you are working on with respect to the project. 36 | 1. Any official management or leadership responsibilities you may have (e.g., manager of a team that includes the following contributors: ….). 37 | 1. What you plan to do with the powers, including specific labels, SIGs, system components, github teams, etc. 38 | 1. How long you think you need the powers. 39 | 1. Any questions you have about appropriate application of the powers (e.g., policy for assigning priorities to issues, policy for assigning and unassigning issues, which parts of the system are covered by which teams). 40 | 41 | 42 | The Contributor Experience working-group leads or Brian Grant (@bgrant0607) will approve or deny your request. 43 | 44 | Some prerequisites may need to be completed prior to being added to the github team, such as clarifying relevant policies in our contributor documentation. 45 | 46 | Thanks for helping to manage the project! 47 | -------------------------------------------------------------------------------- /vendor/github.com/client9/misspell/notwords.go: -------------------------------------------------------------------------------- 1 | package misspell 2 | 3 | import ( 4 | "bytes" 5 | "regexp" 6 | "strings" 7 | ) 8 | 9 | var ( 10 | reEmail = regexp.MustCompile(`[a-zA-Z0-9_.%+-]+@[a-zA-Z0-9-.]+\.[a-zA-Z]{2,6}[^a-zA-Z]`) 11 | reHost = regexp.MustCompile(`[a-zA-Z0-9-.]+\.[a-zA-Z]+`) 12 | reBackslash = regexp.MustCompile(`\\[a-z]`) 13 | ) 14 | 15 | // RemovePath attempts to strip away embedded file system paths, e.g. 16 | // /foo/bar or /static/myimg.png 17 | // 18 | // TODO: windows style 19 | // 20 | func RemovePath(s string) string { 21 | out := bytes.Buffer{} 22 | var idx int 23 | for len(s) > 0 { 24 | if idx = strings.IndexByte(s, '/'); idx == -1 { 25 | out.WriteString(s) 26 | break 27 | } 28 | 29 | if idx > 0 { 30 | idx-- 31 | } 32 | 33 | var chclass string 34 | switch s[idx] { 35 | case '/', ' ', '\n', '\t', '\r': 36 | chclass = " \n\r\t" 37 | case '[': 38 | chclass = "]\n" 39 | case '(': 40 | chclass = ")\n" 41 | default: 42 | out.WriteString(s[:idx+2]) 43 | s = s[idx+2:] 44 | continue 45 | } 46 | 47 | endx := strings.IndexAny(s[idx+1:], chclass) 48 | if endx != -1 { 49 | out.WriteString(s[:idx+1]) 50 | out.Write(bytes.Repeat([]byte{' '}, endx)) 51 | s = s[idx+endx+1:] 52 | } else { 53 | out.WriteString(s) 54 | break 55 | } 56 | } 57 | return out.String() 58 | } 59 | 60 | // replaceWithBlanks returns a string with the same number of spaces as the input 61 | func replaceWithBlanks(s string) string { 62 | return strings.Repeat(" ", len(s)) 63 | } 64 | 65 | // RemoveEmail remove email-like strings, e.g. "nickg+junk@xfoobar.com", "nickg@xyz.abc123.biz" 66 | func RemoveEmail(s string) string { 67 | return reEmail.ReplaceAllStringFunc(s, replaceWithBlanks) 68 | } 69 | 70 | // RemoveHost removes host-like strings "foobar.com" "abc123.fo1231.biz" 71 | func RemoveHost(s string) string { 72 | return reHost.ReplaceAllStringFunc(s, replaceWithBlanks) 73 | } 74 | 75 | // RemoveBackslashEscapes removes characters that are preceeded by a backslash 76 | // commonly found in printf format stringd "\nto" 77 | func removeBackslashEscapes(s string) string { 78 | return reBackslash.ReplaceAllStringFunc(s, replaceWithBlanks) 79 | } 80 | 81 | // RemoveNotWords blanks out all the not words 82 | func RemoveNotWords(s string) string { 83 | // do most selective/specific first 84 | return removeBackslashEscapes(RemoveHost(RemoveEmail(RemovePath(StripURL(s))))) 85 | } 86 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Kubernetes Community 2 | 3 | Welcome to the Kubernetes community! 4 | 5 | This is the starting point for joining and contributing to the Kubernetes community - improving docs, improving code, giving talks etc. 6 | 7 | To learn more about the project structure and organization, please refer to [Project Governance] information. 8 | 9 | ## Communicating 10 | 11 | The [communication](communication/) page lists communication channels like chat, 12 | issues, mailing lists, conferences, etc. 13 | 14 | For more specific topics, try a SIG. 15 | 16 | ## SIGs 17 | 18 | Kubernetes is a set of subprojects, each shepherded by a Special Interest Group (SIG). 19 | 20 | A first step to contributing is to pick from the [list of kubernetes SIGs](sig-list.md). 21 | 22 | A SIG can have its own policy for contribution, 23 | described in a `README` or `CONTRIBUTING` file in the SIG 24 | folder in this repo (e.g. [sig-cli/CONTRIBUTING](sig-cli/CONTRIBUTING.md)), 25 | and its own mailing list, slack channel, etc. 26 | 27 | If you want to edit details about a SIG (e.g. its weekly meeting time or its leads), 28 | please follow [these instructions](./generator) that detail how our docs are auto-generated. 29 | 30 | ## Learn to Build 31 | 32 | Links in [contributors/devel/README.md](contributors/devel/README.md) 33 | lead to many relevant technical topics. 34 | 35 | ## Contribute 36 | 37 | The [Contributor Guide](contributors/guide/README.md) provides detailed instruction on how to get your ideas and bug fixes seen and accepted, including: 38 | 1. How to [file an issue] 39 | 1. How to [find something to work on] 40 | 1. How to [open a pull request] 41 | 42 | ## Membership 43 | 44 | We encourage all contributors to become members. We aim to grow an active, healthy community of contributors, reviewers, and code owners. Learn more about requirements and responsibilities of membership in our [Community Membership] page. 45 | 46 | [Project Governance]:/governance.md 47 | [Developer's Guide]: contributors/devel/development.md 48 | [Contributor Guide]: 49 | contributors/guide/README.md 50 | [file an issue]: 51 | /contributors/guide/README.md#file-an-issue 52 | [find something to work on]: 53 | contributors/guide/README.md#find-something-to-work-on 54 | [open a pull request]: 55 | contributors/guide/README.md#open-a-pull-request 56 | [Community Membership]:/community-membership.md 57 | 58 | [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/CONTRIBUTING.md?pixel)]() 59 | -------------------------------------------------------------------------------- /contributors/design-proposals/storage/containerized-mounter.md: -------------------------------------------------------------------------------- 1 | # Containerized Mounter with Chroot for Container-Optimized OS 2 | 3 | ## Goal 4 | 5 | Due security and management overhead, our new Container-Optimized OS used by GKE 6 | does not carry certain storage drivers and tools needed for such as nfs and 7 | glusterfs. This project takes a containerized mount approach to package mount 8 | binaries into a container. Volume plugin will execute mount inside of container 9 | and share the mount with the host. 10 | 11 | 12 | ## Design 13 | 14 | 1. A docker image has storage tools (nfs and glusterfs) pre-installed and uploaded 15 | to gcs. 16 | 2. During GKE cluster configuration, the docker image is pulled and installed on 17 | the cluster node. 18 | 3. When nfs or glusterfs type mount is invoked by kubelet, it will run the mount 19 | command inside of a container with the pre-install docker image and the mount 20 | propagation set to “shared. In this way, the mount inside the container will 21 | visible to host node too. 22 | 4. A special case for NFSv3, a rpcbind process is issued before running mount 23 | command. 24 | 25 | ## Implementation details 26 | 27 | * In the first version of containerized mounter, we use rkt fly to dynamically 28 | start a container during mount. When mount command finishes, the container is 29 | normally exited and will be garbage-collected. However, in case the glusterfs 30 | mount, because a gluster daemon is running after command mount finishes util 31 | glusterfs unmount, the container started for mount will continue to run until 32 | glusterfs client finishes. The container cannot be garbage-collected right away 33 | and multiple containers might be running for some time. Due to shared mount 34 | propagation, with more containers running, the number of mounts will increase 35 | significantly and might cause kernel panic. To solve this problem, a chroot 36 | approach is proposed and implemented. 37 | * In the second version, instead of running a container on the host, the docker 38 | container’s file system is exported as a tar archive and pre-installed on host. 39 | Kubelet directory is shared mount between host and inside of the container’s 40 | rootfs. When a gluster/nfs mount is issued, a mounter script will use chroot to 41 | change to the container’s rootfs and run the mount. This approach is very clean 42 | since there is no need to manage a container’s lifecycle and avoid having large 43 | number of mounts. 44 | -------------------------------------------------------------------------------- /sig-aws/README.md: -------------------------------------------------------------------------------- 1 | <!--- 2 | This is an autogenerated file! 3 | 4 | Please do not edit this file directly, but instead make changes to the 5 | sigs.yaml file in the project root. 6 | 7 | To understand how this file is generated, see https://git.k8s.io/community/generator/README.md 8 | --> 9 | # AWS Special Interest Group 10 | 11 | Covers maintaining, supporting, and using Kubernetes hosted on AWS Cloud. 12 | 13 | ## Meetings 14 | * Regular SIG Meeting: [Fridays at 9:00 PT (Pacific Time)](https://zoom.us/my/k8ssigaws) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29). 15 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1-i0xQidlXnFEP9fXHWkBxqySkXwJnrGJP9OGyP2_P14/edit). 16 | 17 | ## Leadership 18 | 19 | ### Chairs 20 | The Chairs of the SIG run operations and processes governing the SIG. 21 | 22 | * Justin Santa Barbara (**[@justinsb](https://github.com/justinsb)**) 23 | * Kris Nova (**[@kris-nova](https://github.com/kris-nova)**), Heptio 24 | * Bob Wise (**[@countspongebob](https://github.com/countspongebob)**), AWS 25 | 26 | ## Contact 27 | * [Slack](https://kubernetes.slack.com/messages/sig-aws) 28 | * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-aws) 29 | * [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Faws) 30 | 31 | ## Subprojects 32 | 33 | The following subprojects are owned by sig-aws: 34 | - **cloud-provider-aws** 35 | - Owners: 36 | - https://raw.githubusercontent.com/kubernetes/cloud-provider-aws/master/OWNERS 37 | 38 | ## GitHub Teams 39 | 40 | The below teams can be mentioned on issues and PRs in order to get attention from the right people. 41 | Note that the links to display team membership will only work if you are a member of the org. 42 | 43 | The google groups contain the archive of Github team notifications. 44 | Mentioning a team on Github will CC its group. 45 | Monitor these for Github activity if you are not a member of the team. 46 | 47 | | Team Name | Details | Google Groups | Description | 48 | | --------- |:-------:|:-------------:| ----------- | 49 | | @kubernetes/sig-aws-misc | [link](https://github.com/orgs/kubernetes/teams/sig-aws-misc) | [link](https://groups.google.com/forum/#!forum/kubernetes-sig-aws-misc) | General Discussion | 50 | 51 | <!-- BEGIN CUSTOM CONTENT --> 52 | ## Participate 53 | For information on how to participate in this community, read our [contribution guidelines](CONTRIBUTING.md). 54 | <!-- END CUSTOM CONTENT --> 55 | -------------------------------------------------------------------------------- /contributors/devel/cri-validation.md: -------------------------------------------------------------------------------- 1 | # Container Runtime Interface (CRI) Validation Testing 2 | 3 | CRI validation testing provides a test framework and a suite of tests to validate that the Container Runtime Interface (CRI) server implementation meets all the requirements. This allows the CRI runtime developers to verify that their runtime conforms to CRI, without needing to set up Kubernetes components or run Kubernetes end-to-end tests. 4 | 5 | CRI validation testing is currently Alpha and is hosted at the [cri-tools](https://github.com/kubernetes-incubator/cri-tools) repository. Performance benchmarking will be added in the future. We encourage the CRI developers to report bugs or help extend the test coverage by adding more tests. 6 | 7 | ## Install 8 | 9 | The test suites can be installed easily via `go get` command: 10 | 11 | ```sh 12 | go get github.com/kubernetes-incubator/cri-tools/cmd/critest 13 | ``` 14 | 15 | Then `critest` binary can be found in `$GOPATH/bin`. 16 | 17 | *Note: ensure GO is installed and GOPATH is set before installing critest.* 18 | 19 | ## Running tests 20 | 21 | ### Prerequisite 22 | 23 | Before running the test, you need to _ensure that the CRI server under test is running and listening on a Unix socket_. Because the validation tests are designed to request changes (e.g., create/delete) to the containers and verify that correct status is reported, it expects to be the only user of the CRI server. Please make sure that 1) there are no existing CRI-managed containers running on the node, and 2) no other processes (e.g., Kubelet) will interfere with the tests. 24 | 25 | ### Run 26 | 27 | ```sh 28 | critest validation 29 | ``` 30 | 31 | This will 32 | 33 | - Connect to the shim of CRI container runtime 34 | - Run the tests using `ginkgo` 35 | - Output the test results to STDOUT 36 | 37 | critest connects to `/var/run/dockershim.sock` by default. For other runtimes, the endpoint can be set in two ways: 38 | 39 | - By setting flags `--runtime-endpoint` and `--image-endpoint` 40 | - By setting environment variables `CRI_RUNTIME_ENDPOINT` and `CRI_IMAGE_ENDPOINT` 41 | 42 | ## Additional options 43 | 44 | - `--focus`, `-f`: Only run the tests that match the regular expression. 45 | - -`-ginkgo-flags`, `-g`: Space-separated list of arguments to pass to Ginkgo test runner. 46 | - `--image-endpoint`, `-i`: Set the endpoint of image service. Same with runtime-endpoint if not specified. 47 | - `--runtime-endpoint`, `-r`: Set the endpoint of runtime service. Default to `/var/run/dockershim.sock`. 48 | - `--skip`, `-s`: Skip the tests that match the regular expression. 49 | -------------------------------------------------------------------------------- /events/2017/12-contributor-summit/steering-committee-update.md: -------------------------------------------------------------------------------- 1 | Steering Committee Update 2 | -------------------------- 3 | 4 | Notes by @jberkus 5 | 6 | Showed list of Steering Committee backlog. 7 | 8 | We had a meeting, and the two big items we'd been pushing on hard were: 9 | 10 | * votining in the proposals in the bootstrap committee 11 | * how we're going to handle incubator and contrib etc. 12 | 13 | Incubator/contrib: one of our big concerns are what the the consequences for projects and ecosystems. 14 | We're still discussing it, please be patient. In the process of solving the incubator process, we have to answer 15 | what is kubernetes, which is probably SIGs, but what's a SIG, and who decides, and ... we end up having to examine 16 | everything. In terms of deciding what is and isn't kubernetes, we want to have that discussion in the open. 17 | We also recognize that the project has big technical debt and is scary for new contributors. 18 | 19 | We're also trying to figure out how to bring in new people in order to have them add, instead of contributing 20 | to chaos. So we need contributors to do mentorship. We also need some tools for project management, if anyone 21 | wants to work on these. 22 | 23 | We're also going to be working on having a code of conduct for the project, if you 24 | want to be part of that discussion you can join the meetings. For private concerns: steering-private@kubernetes.io. 25 | One of the challenges is deciding how enforcement will work. We've had a few incidents over the last 2 years, 26 | which were handled very quietly. But we're having more people show up on Slack who don't know norms, 27 | so feel free to educate people on what the community standards are. As our project expands across various 28 | media, we need to track the behavior of individuals. 29 | 30 | Q: "Can SIGs propose a decision for some of the stuff on the backlog list and bring it to the SC?" 31 | A: "Yes, please!" 32 | 33 | The other big issue is who owns a SIG and how SIG leaders are chosen. The project needs to delegate more things to the 34 | SIGs but first we need to have transparency around the SIG governance process. 35 | 36 | Q: "As for What Kubernetes Is: is that a living document we can reference?" 37 | A: "There's an old one. I have a talk on Friday about updating it." 38 | 39 | There's also the question of whether we're involved in "ecosystem projects" like those hosted by the CNCF. Things will change 40 | but the important thing is to have a good governance structure so that we can make transparent decisions as things change. 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | -------------------------------------------------------------------------------- /events/2017/12-contributor-summit/scaling-new-contributors.md: -------------------------------------------------------------------------------- 1 | # Scaling New Contributors 2 | *Lead: Vishnu Kannan* 3 | *Notetaker: Chris Love* 4 | 5 | New pull requests are plateauing in k/k 6 | Takes much longer for a PR to get through 7 | 8 | Contributor Experience 9 | 3 mo for PR merged - minor PR that was a fix 10 | Nobody reviewed - was ignored 11 | PRs are lacking process to get them on milestones 12 | Lack of organization and understanding PR process 13 | There is a need for a sig buyin 14 | We have a explicate state machine, instead of a implicate state machine 15 | We do have a well defined process for new contributors to follow 16 | We need to have committed resources to a PR, 17 | File an issue first, then file a PR 18 | When the needs sig is there, the issue will be processed and you can find out which sig 19 | 20 | What is the problem 21 | No time to review PRs 22 | 23 | Mentoring Program 24 | Mentoring program overview 25 | Common theme is that we do not have time to review PR 26 | Bootcamps for new contributors 27 | 28 | Lot of Common Complaints 29 | 30 | Tests did not pass what happened 31 | Devstats 32 | Everyone needs to look at the stats 33 | We are currently bottlenecked at approvers not reviews 34 | 35 | How to fix the problem 36 | SIG Leads are too busy 37 | Have another role within the sigs for mentors 38 | Can we label the issues in terms of complexity 39 | Sig-cli has it documented in a contributor guide 40 | Incentivizing mentoring 41 | How do we help take the load off of the approvers pool, how do we improve reviews 42 | How many times a reviewer say lgtm 43 | Reviewer performance 44 | We need to document what a good review looks like 45 | Guidance on progress to contributor -> reviewer -> maintainer 46 | How does maintain a good citizenship in the community 47 | Put the documentation into kubernetes.io 48 | Simple use-case examples on how to get a PR in 49 | Give contributors some responsibilities 50 | Planned workshop on how to get a PR merged 51 | Contributor based workshop 52 | Ask questions on #kubernetes-dev 53 | We need to document how to get answers 54 | We need to move our documents into kubernetes.io 55 | Sigs may not want to have new contributors 56 | We need to cleanup those who are inactive in k/k - OWNERS and MAINTAINERS 57 | How do we create incentives? 58 | If they are autosigned an issue and do not respond - we need to measure that metric 59 | How do we fix the release process in terms of what is in a release, because we do not have a target we do not know what we are shooting at 60 | We need to figure out what new contributors are working on 61 | Start off by using kubernetes then become contributors 62 | --------------------------------------------------------------------------------