![]() Automatic merge from submit-queue kube-apiserver options should be decoupled from impls A few months ago we refactored options to keep it independent of the implementations, so that it could be used in CLI tools to validate config or to generate config, without pulling in the full dependency tree of the master. This change restores that by separating server_run_options.go back to its own package. Also, options structs should never contain non-serializable types, which storagebackend.Config was doing with runtime.Codec. Split the codec out. Fix a typo on the name of the etcd2.go storage backend. Finally, move DefaultStorageMediaType to server_run_options. @nikhiljindal as per my comment in #24454, @liggitt because you and I discussed this last time |
||
---|---|---|
.. | ||
apiserver | ||
aws_ebs | ||
azure_file | ||
blog-logging | ||
cassandra | ||
celery-rabbitmq | ||
cephfs | ||
cluster-dns | ||
elasticsearch | ||
experimental/persistent-volume-provisioning | ||
explorer | ||
fibre_channel | ||
flexvolume | ||
flocker | ||
glusterfs | ||
guestbook | ||
guestbook-go | ||
hazelcast | ||
https-nginx | ||
iscsi | ||
javaee | ||
javaweb-tomcat-sidecar | ||
job | ||
k8petstore | ||
kubectl-container | ||
meteor | ||
mysql-cinder-pd | ||
mysql-galera | ||
mysql-wordpress-pd | ||
newrelic | ||
nfs | ||
nodesjs-mongodb | ||
openshift-origin | ||
phabricator | ||
rbd | ||
redis | ||
rethinkdb | ||
runtime-constraints | ||
selenium | ||
sharing-clusters | ||
spark | ||
storm | ||
vitess | ||
doc.go | ||
examples_test.go | ||
guidelines.md | ||
OWNERS | ||
pod | ||
README.md | ||
scheduler-policy-config-with-extender.json | ||
scheduler-policy-config.json | ||
simple-nginx.md |
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.2/examples/README.md).Documentation for other releases can be found at releases.k8s.io.
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.