adcca3e663
Automatic merge from submit-queue Curating Owners: examples/mysql-wordpress-pd cc @jeffmendoza In an effort to expand the existing pool of reviewers and establish a two-tiered review process (first someone lgtms and then someone experienced in the project approves), we are adding new reviewers to existing owners files. If You Care About the Process: ------------------------------ We did this by algorithmically figuring out who’s contributed code to the project and in what directories. Unfortunately, that doesn’t work well: people that have made mechanical code changes (e.g change the copyright header across all directories) end up as reviewers in lots of places. Instead of using pure commit data, we generated an excessively large list of reviewers and pruned based on all time commit data, recent commit data and review data (number of PRs commented on). At this point we have a decent list of reviewers, but it needs one last pass for fine tuning. Also, see https://github.com/kubernetes/contrib/issues/1389. TLDR: ----- As an owner of a sig/directory and a leader of the project, here’s what we need from you: 1. Use PR https://github.com/kubernetes/kubernetes/pull/35715 as an example. 2. The pull-request is made editable, please edit the `OWNERS` file to remove the names of people that shouldn't be reviewing code in the future in the **reviewers** section. You probably do NOT need to modify the **approvers** section. Names asre sorted by relevance, using some secret statistics. 3. Notify me if you want some OWNERS file to be removed. Being an approver or reviewer of a parent directory makes you a reviewer/approver of the subdirectories too, so not all OWNERS files may be necessary. 4. Please use ALIAS if you want to use the same list of people over and over again (don't hesitate to ask me for help, or use the pull-request above as an example)
Kubernetes Examples: releases.k8s.io/HEAD
This directory contains a number of examples of how to run real applications with Kubernetes.
Demonstrations of how to use specific Kubernetes features can be found in our documents.
Maintained Examples
Maintained Examples are expected to be updated with every Kubernetes release, to use the latest and greatest features, current guidelines and best practices, and to refresh command syntax, output, changed prerequisites, as needed.
| Name | Description | Notable Features Used | Complexity Level | |
|---|---|---|---|---|
| Guestbook | PHP app with Redis | Replication Controller, Service | Beginner | |
| WordPress | WordPress with MySQL | Deployment, Persistent Volume with Claim | Beginner | |
| Cassandra | Cloud Native Cassandra | Daemon Set | Intermediate |
Note: Please add examples to the list above that are maintained.
See Example Guidelines for a description of what goes in this directory, and what examples should contain.