![]() The codec factory should support two distinct interfaces - negotiating for a serializer with a client, vs reading or writing data to a storage form (etcd, disk, etc). Make the EncodeForVersion and DecodeToVersion methods only take Encoder and Decoder, and slight refactoring elsewhere. In the storage factory, use a content type to control what serializer to pick, and use the universal deserializer. This ensures that storage can read JSON (which might be from older objects) while only writing protobuf. Add exceptions for those resources that may not be able to write to protobuf (specifically third party resources, but potentially others in the future). |
||
---|---|---|
.. | ||
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.