![]() hypothesis: The old userspace proxier would internally retry connections. The new one does not. When this test comes up, the firewall might not yet be open or something is causing a long delay and a timeout. I can't repro this failure locally, so I am shooting in the dark. It's sort of plausible. evidence: I can SSH into the jenkins master that is hung and I can see the hung curl. I can run that curl by hand and it works. I can see that my shell is in the same netns as that hung curl. |
||
---|---|---|
.. | ||
aws_ebs | ||
blog-logging | ||
cassandra | ||
celery-rabbitmq | ||
cephfs | ||
cluster-dns | ||
elasticsearch | ||
explorer | ||
extensions | ||
fibre_channel | ||
flocker | ||
glusterfs | ||
guestbook | ||
guestbook-go | ||
hazelcast | ||
high-availability | ||
https-nginx | ||
iscsi | ||
javaee | ||
javaweb-tomcat-sidecar | ||
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 | ||
pod | ||
README.md | ||
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.1/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.