mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue Reuse fields and labels This should significantly reduce memory allocations in apiserver in large cluster. Explanation: - every kubelet is refreshing watch every 5-10 minutes (this generally is not causing relist - it just renews watch) - that means, in 5000-node cluster, we are issuing ~10 watches per second - since we don't have "watch heartbets", the watch is issued from previously received resourceVersion - to make some assumption, let's assume pods are evenly spread across pods, and writes for them are evenly spread - that means, that a given kubelet is interested in 1 per 5000 pod changes - with that assumption, each watch, has to process 2500 (on average) previous watch events - for each of such even, we are currently computing fields. This PR is fixing this problem. |
||
---|---|---|
.. | ||
apiserver | ||
cluster-dns | ||
cockroachdb | ||
elasticsearch | ||
experimental/persistent-volume-provisioning | ||
explorer | ||
guestbook | ||
guestbook-go | ||
https-nginx | ||
javaee | ||
javaweb-tomcat-sidecar | ||
job | ||
k8petstore | ||
kubectl-container | ||
meteor | ||
mysql-cinder-pd | ||
mysql-wordpress-pd | ||
newrelic | ||
nodesjs-mongodb | ||
openshift-origin | ||
phabricator | ||
podsecuritypolicy/rbac | ||
runtime-constraints | ||
selenium | ||
sharing-clusters | ||
spark | ||
storage | ||
storm | ||
sysdig-cloud | ||
volumes | ||
BUILD | ||
OWNERS | ||
README.md | ||
doc.go | ||
examples_test.go | ||
guidelines.md | ||
pod | ||
scheduler-policy-config-with-extender.json | ||
scheduler-policy-config.json | ||
simple-nginx.md |
README.md
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.