- 18 Mar, 2019 6 commits
-
-
Jordan Liggitt authored
-
Kubernetes Prow Robot authored
Clear conntrack entries on 0 -> 1 endpoint transition with externalIPs
-
Kubernetes Prow Robot authored
Remove reference to USE_RELEASE_NODE_BINARIES.
-
Kubernetes Prow Robot authored
fix kubeadm init output
-
fabriziopandini authored
-
Kubernetes Prow Robot authored
Stop vsphere cloud provider from spamming logs with `failed to patch IP`
-
- 17 Mar, 2019 3 commits
-
-
Kubernetes Prow Robot authored
fix kubeadm external CA Mode
-
fabriziopandini authored
-
Kubernetes Prow Robot authored
Kubeadm insecure port
-
- 16 Mar, 2019 8 commits
-
-
Jordan Liggitt authored
This reverts commit 5b64a986.
-
Kubernetes Prow Robot authored
kubelet watch-manager test, restore watch-based manager default
-
Kubernetes Prow Robot authored
Don't follow non-local redirects from HTTP probes
-
Kubernetes Prow Robot authored
disable HTTP2 ingress test
-
Kubernetes Prow Robot authored
Fix panic when removing docker images
-
Kubernetes Prow Robot authored
kubeadm: Allow certain certs/keys to be missing on the secret
-
Kubernetes Prow Robot authored
upgrade to go1.12.1
-
Kubernetes Prow Robot authored
Revert "Speculative workaround for #74890"
-
- 15 Mar, 2019 16 commits
-
-
Rafael Fernández López authored
Under certain circumstances, specially when using an insecure external etcd cluster (no certificates), or when using external certificates ( no CA key), some keys inside the kubeadm-certs secret data can contain the key with an empty value on the map. When downloading certs just ignore those that are blank and inform the user about it.
-
Kubernetes Prow Robot authored
Refactor the node perf tests to run on non-amd64 cluster
-
Tim Allclair authored
-
Tim Allclair authored
-
Benjamin Elder authored
-
Benjamin Elder authored
-
Benjamin Elder authored
-
Benjamin Elder authored
-
Minhan Xia authored
-
Kubernetes Prow Robot authored
Update Cluster Autscaler version to 1.14.0-beta.2
-
Jacob Tanenbaum authored
As part of the endpoint creation process when going from 0 -> 1 conntrack entries are cleared. This is to prevent an existing conntrack entry from preventing traffic to the service. Currently the system ignores the existance of the services external IP addresses, which exposes that errant behavior This adds the externalIP addresses of udp services to the list of conntrack entries that get cleared. Allowing traffic to flow Signed-off-by:Jacob Tanenbaum <jtanenba@redhat.com>
-
Kubernetes Prow Robot authored
Bump CSI version
-
Łukasz Osipiuk authored
-
Lubomir I. Ivanov authored
-
Hemant Kumar authored
-
Kubernetes Prow Robot authored
Ensure ownership when deleting a load balancer security group
-
- 14 Mar, 2019 7 commits
-
-
Kubernetes Prow Robot authored
Deflake nodelease test
-
Peter Hornyack authored
This variable was used for development purposes and was accidentally introduced in https://github.com/kubernetes/kubernetes/commit/f0f78299348afcf770d4e8d89dcea82f80811b28. This is its only use in the tree: https://github.com/kubernetes/kubernetes/search?q=USE_RELEASE_NODE_BINARIES&unscoped_q=USE_RELEASE_NODE_BINARIES
-
Kubernetes Prow Robot authored
kubelet: updated logic of verifying a static critical pod
-
Fabio Rapposelli authored
Fixes: #75236
-
Kubernetes Prow Robot authored
apiextensions: commit generated openapi definitions
-
Jordan Liggitt authored
-
Pengfei Ni authored
-