Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): no.

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): documentation, yaml, hack/generate-docs

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version): 1.4.5

Environment:

Cloud provider or hardware configuration: local install

OS (e.g. from /etc/os-release): CentOS 7

Kernel (e.g. uname -a):3.10.0-327.28.3.el7.x86_64

Install tools: manual

Others:

What happened:

Download 1.4.5 release tarball from Github:

https://github.com/kubernetes/kubernetes/releases/download/v1.4.5/kubernetes.tar.gz

Unpack it and look at documentation folder docs/yaml/kubectl/...

Inside that folder user can see bunch of yaml files that have content:

This file is autogenerated, but we've stopped checking such files into the
repository to reduce the need for rebases. Please run hack/generate-docs.sh to
populate this file.

What you expected to happen:

In my opinion, those placeholders should be replaced with real generated documentation at the time of release. So, somewhere in release scripts call to generate documentation is missing.

How to reproduce it (as minimally and precisely as possible):

$ wget https://github.com/kubernetes/kubernetes/releases/download/v1.4.5/kubernetes.tar.gz
$ tar zxf kubernetes.tar.gz
$ cat kubernetes/docs/yaml/kubectl/kubectl_api-versions.yaml

Anything else do we need to know:

Issue 2:
I noticed that while connections between pods were usually nearly instant, sometimes they took a few seconds and they sometimes hung altogether, so I started poking around. I quickly found that kube-proxy is taking up between 80% - 100% of a CPU on each system that it's running on. The logs weren't very interesting, but then I checked the iptables rules:

# sudo iptables -L -t nat | wc -l
164757

The rules themselves:

# sudo iptables -L -t nat
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 KUBE-PORTALS-CONTAINER all -- any any anywhere anywhere /* handle ClusterIPs; NOTE: this must be before the NodePort rules */
1 60 KUBE-PORTALS-CONTAINER all -- any any anywhere anywhere /* handle ClusterIPs; NOTE: this must be before the NodePort rules */
4 258 KUBE-PORTALS-CONTAINER all -- any any anywhere anywhere /* handle ClusterIPs; NOTE: this must be before the NodePort rules */
6 547 KUBE-PORTALS-CONTAINER all -- any any anywhere anywhere /* handle ClusterIPs; NOTE: this must be before the NodePort rules */
12 1632 KUBE-PORTALS-CONTAINER all -- any any anywhere anywhere /* handle ClusterIPs; NOTE: this must be before the NodePort rules */
...

The OUTPUT chain is just as bad as the PREROUTING chain. The KUBE-* chains are all sane, having one rule per service port.

For now, I've set up a cron job to periodically flush PREROUTING and OUTPUT (and recreate the proper 4 rules to hopefully avoid any downtime), but this is obviously a poor workaround.

I'm running release 1.0.6 on CentOS 6.