- 08 Dec, 2016 40 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 36310, 37349, 38319, 38402, 38338) Fix space issue in volumePath with vSphere Cloud Provider I tried to create a kubernetes deployment with vSphere volume with volume path "[datastore] kubevols/redis-master". In this case the cloud provider queries the getDeviceNameFromMount() to return the path of the volume mounted. Since getDeviceNameFromMount() queries the filesystem to get the mount references, it returns a volume path "[datastore]\\040kubevols/redis-master". Later the kubelet searches for this volume path in both the actual and desired states. Th actual and desired states contains volume with path "[datastore] kubevols/redis-master". So, it couldn't find such volume path and therefore kubernetes stalls unable to make any progress further similar to one described in #37022. This PR will fix the space issue in volume path by replacing \\040 to empty space. This fixes #37712. Also fixes #38148 @kerneltime @pdhamdhere
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 36310, 37349, 38319, 38402, 38338) Use the `serviceShard` variable in the service shard block, not the `service` variable. cc @kubernetes/sig-federation
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 36310, 37349, 38319, 38402, 38338) add summarizing discovery controller and handlers Requires https://github.com/kubernetes/kubernetes/pull/38304 . This adds discovery support to the new `kubernetes-discovery` that runs based on a controller wired up to the `APIService.apiregistration.k8s.io`. It also adds in plumbing for `local-up-cluster.sh` to register the "normal" kube resources. @kubernetes/sig-api-machinery @sttts
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue replace HTTP status code with HTTP status code const <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: replace HTTP status code with HTTP status code const Thanks! **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue [Federation] Make federation etcd PVC size configurable This one implements one of the many TODO items pending in the previous set of kubefed PRs. The design doc PR is at https://github.com/kubernetes/kubernetes/pull/34484 cc @kubernetes/sig-cluster-federation @madhusudancs **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ``` [Federation] kubefed init now has a new flag, --etcd-pv-capacity, which can be used to configure the persistent volume capacity for etcd. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Customizable vagrant rsync args and excludes <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: There are some annoyances with Vagrant+rsync currently. When using rsync file synchronization with Vagrant, the whole kubernetes repo directory is copied over into the virtual machine. This includes the _output directory, which tends to be gigabytes in size, while often just _output/release-tars (a few hundred MB) would be enough. Furthermore, if the some of the directories contains a recursive symlink, rsync with the default args will keep descending and copying files endlessly until filling up the VM disk. **The improvement**: Making the rsync args and excluded dirs/files customizable via KUBERNETES_VAGRANT_RSYNC_ARGS and KUBERNETES_VAGRANT_RSYNC_EXLUDE, respectively, allows the developer to prevent the issues mentioned above. A new KUBERNETES_VAGRANT_USE_RSYNC variable is also added to control whether Vagrant should force usage of rsync as the file synchronization backend. The args/exclude customizations only take effect when KUBERNETES_VAGRANT_USE_RSYNC is 'true'. **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubedns: use initial resource listing as ready signal Fix #35140. Set up the ready signal after the first resource listing finished for both endpoints and services instead of listen on kubernetes service. @bprashanth @bowei @thockin **Release note**: ``` ```
-
Madhusudan.C.S authored
-
deads2k authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 38377, 36365, 36648, 37691, 38339) Exponential back off when volume delete fails **What this PR does / why we need it**: This PR implements ability in pv_controller to back off when deleting a volume fails from plugin API. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: Partly fixes #38295 , but I think volume delete is most problematic thing happening in pv_controller without any sort of backoff. After this change the attempts of volume deletion look like: ``` controller : I1208 00:18:35.532061 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 controller : I1208 00:20:50.578325 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 controller : I1208 00:23:05.563488 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 controller : I1208 00:25:20.599158 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 controller : I1208 00:27:35.560009 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 controller : I1208 00:29:50.594967 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 controller : I1208 00:32:05.539168 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 controller : I1208 00:34:20.581665 16388 aws_util.go:55] Error deleting EBS Disk volume aws://us-east-1d/vol-abcdefg: VolumeInUse: Volume vol-abcdefg is currently attached to i-1234567 ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 38377, 36365, 36648, 37691, 38339) Do not create selector and namespaces in a loop where possible With 1000 nodes and 5000 pods (5 pods per node) with anti-affinity a lot of CPU wasted on creating LabelSelector and sets.String (map). With this change we are able to deploy that number of pods in ~25 minutes. Without - it takes 30 minutes to deploy 500 pods with anti-affinity configured.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 38377, 36365, 36648, 37691, 38339) controller: sync stuck deployments in a secondary queue @kubernetes/deployment this makes Deployments not depend on a tight resync interval in order to estimate progress.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 38377, 36365, 36648, 37691, 38339) Backoff correctly when adopting replica sets/pods @kubernetes/deployment ptal Fixes https://github.com/kubernetes/kubernetes/issues/34534
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 38377, 36365, 36648, 37691, 38339) HPA e2e tests: fixed problem w/blocking channel.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix local-cluster-up on Mac and discovery on all systems - use cfssl on the host, not from Docker. Solves a number of permission problem with selinux and Mac - fix discovery startup
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add secrets to Density and Load tests cc @jeremyeder @timstclair @sjug
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 35939, 38381, 37825, 38306, 38110) split easy controllers from giant start func continues work from https://github.com/kubernetes/kubernetes/pull/37976 to separate controller initialization.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 35939, 38381, 37825, 38306, 38110) Add test for multi-threaded use of ratelimiter Adds a test to help prevent #38273 from occurring again
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 35939, 38381, 37825, 38306, 38110) Moved start-kubemark-master.sh from test/kubemark/ to test/kubemark/r…
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue apiserver(s): do not create self-signed certs if port is zero
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Minor cleanup: fix typos Fix some typos.
-
xilabao authored
-
Dr. Stefan Schimanski authored
-
Dr. Stefan Schimanski authored
-
Marek Grabowski authored
re-run godep license
-
deads2k authored
-
Dr. Stefan Schimanski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 37701, 36702, 37145, 37424, 38261) replace err with nil when err is nil <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: When err is nil ,replace err with nil, that can make code more readable Thanks. **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 37701, 36702, 37145, 37424, 38261) function name change function name change
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 37701, 36702, 37145, 37424, 38261) Fix for #34422: bump C* version to 3.9 Fix for #34422
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 37701, 36702, 37145, 37424, 38261) Limit unbound label cardinality on request errors This converts all request errors to the string `<error>` instead of passing the full error string. Error strings can have arbitrary values and thus have a cardinality that is not suitable for a metric use case. Inspecting individual errors is a logging use case which can be handled separately by registering a client error handler. @kubernetes/sig-instrumentation
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update selenium docker images **What this PR does / why we need it**: Updates selenium docker images (2.47 was released a year ago) **Which issue this PR fixes** - **Special notes for your reviewer**: - **Release note**: `NONE`
-
Dr. Stefan Schimanski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 35884, 37305, 37369, 37429, 35679) fix repeat request for auth reference to #27851 When use basic-auth/RBAC, don't set the users in .kube/config ``` # cat ~/.kube/config apiVersion: v1 clusters: - cluster: insecure-skip-tls-verify: true server: https://127.0.0.1:6443 name: ubuntu contexts: - context: cluster: ubuntu namespace: default user: test name: ubuntu current-context: ubuntu kind: Config preferences: {} users: [] ``` kubectl request for username/password time after time ``` $ kubectl get nodes Please enter Username: admin Please enter Password: ****** Please enter Username: admin Please enter Password: ****** ``` -
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 35884, 37305, 37369, 37429, 35679) fix mixleading warning message regarding kube-proxy nodeIP initializa… The current warning message implies that the operator should restart kube-proxy with some flag related to node IP which can be very misleading.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 35884, 37305, 37369, 37429, 35679) fix typo in predicates
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 35884, 37305, 37369, 37429, 35679) LICENSE: revert modifications to Apache license
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue print log error <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: when failed to load CA,will print both "Loaded CA:" and "Error loading root CA certificate date:" ,but only need to print "Error loading root CA certificate date:" in fact. **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ``` release-note ```
-
Dmitry Shulyak authored
Change-Id: Ib8e62df92a3ea6b8ee6b90cb0b73af71332481d7
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Added support for HOME environment variable on Windows **What this PR does / why we need it**: On Windows the HOME environment variable should be taken in account when trying to find the home directory. Several tools already support the HOME environment variable, notably git-bash. It would be very convenient to have the kubernete tools (including minikube) to also support the environment variable. The current situation **Special notes for your reviewer**: **Release note**: ``` ```
-