- 20 Jul, 2017 30 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49114, 48810) Move generators to staging/src/k8s.io/kube-gen Reason number one for people trying the impossible of vendoring kube: reuse of the generators.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix master disk size variable usage
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix too extensive logging in Stackdriver Logging e2e tests Since logging pod now includes a cache, printing it out makes build-log unusable.
-
gmarek authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49212, 49203, 49255) Update wordpress to 4.8.0 **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49212, 49203, 49255) If the init fails for whatever reason, plugin is nil and cannot be used. **What this PR does / why we need it**: Addressing ``` === RUN TestCanSupport E0719 13:48:19.829849 2289 driver-call.go:232] init command failed, status: Successx, reason: --- FAIL: TestCanSupport (0.00s) flexvolume_test.go:180: Can't find the plugin by name panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x11fc5b5] ``` **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # N/A **Special notes for your reviewer**: N/A **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Bump rescheduler version to v0.3.1 **What this PR does / why we need it**: Bump Rescheduler version to v0.3.1 to log to STDERR. **Which issue this PR fixes** Fixes https://github.com/kubernetes/contrib/issues/2518 **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Tolerate Flavor information for computing instance type **What this PR does / why we need it**: Current devstack seems to return "id", and an upcoming change using nova's microversion will be returning "original_name": https://blueprints.launchpad.net/nova/+spec/instance-flavor-api So let's just inspect what is present and use that to figure out the instance type. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix on-premises term in error string and comments for aws provider **What this PR does / why we need it**: fix for correct terminology of "on-premises" over "on-premise" **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: n/a **Special notes for your reviewer**: Updated error string while doing a scrub for the incorrect term in the docs (kubernetes/kubernetes.github.io#4413). **Release note**: ```release-note NONE ```
-
Dr. Stefan Schimanski authored
-
Dr. Stefan Schimanski authored
-
Dr. Stefan Schimanski authored
-
Dr. Stefan Schimanski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue fix naming for testgrid to pick up cmd test junit Fixes #47613 The file name for testgrid to pick up should match regex `'junit(_[^_]+)?(_\d+-\d+)?(_\d+)?.xml'` Name before is `junit-test-cmd.xml` Name after is `junit_test-cmd.xml` ```release-note NONE ``` /assign @krzyzacy
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49083, 45540, 46862) Respect KUBE_BUILD_PLATFORMS set by user **What this PR does / why we need it**: Currently the only(?) toggle available for custom arch builds is KUBE_FASTBUILD. We should allow the user to specify a list of arch(es) in the environment variable KUBE_BUILD_PLATFORMS. Example: KUBE_BUILD_PLATFORMS="linux/amd64 linux/arm64" hack/build-cross.sh **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # Fixes #20365 **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49083, 45540, 46862) Add extra logging to azure API get calls **What this PR does / why we need it**: This PR adds extra logging for external calls to the Azure API, specifically get calls. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # This will help troubleshoot problems arising from the usage of this cloudprovider. For example, it looks like #43516 is caused by a call to the cloudprovider taking too much time.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49083, 45540, 46862) update golang version to go1.8 Signed-off-by:sakeven <jc5930@sina.cn> **What this PR does / why we need it**: There are some code breaking the compatibility with golang 1.6. Now kubernetes only support golang 1.8. We need to update golang version check script. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #49082 **Special notes for your reviewer**: **Release note**: ``` NONE ```
-
Luke Heidecke authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49218, 48253, 48967, 48460, 49230) use informers for quota evaluation of core resources where possible Not all quota evaluators are using shared informers. This updates them all to have the option of doing it. Fixes https://github.com/kubernetes/kubernetes/issues/49233 ``` resource quota uses shared informers for core types ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49218, 48253, 48967, 48460, 49230) Fix the Azure file to work within different cloud environments **What this PR does / why we need it**: Fix the Azure file plugin to work within different cloud environments. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #46081 cc @rootfs @brendandburns
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49218, 48253, 48967, 48460, 49230) additional backoff in azure cloudprovider Fixes #48971 **What this PR does / why we need it**: We want to be able to opt in to backoff retry logic for kubelet-originating request behavior: node IP address resolution and node load balancer pool membership enforcement. **Special notes for your reviewer**: The use-case for this is azure cloudprovider clusters with large node counts, especially during cluster installation, or other scenarios when lots of nodes come online at once and attempt to register all resources with the backend API. To allow clusters at scale more control over the API request rate in-cluster, backoff config has the ability to meaningful slow down this rate, when appropriate. **Release note**: ```additional backoff in azure cloudprovider ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49218, 48253, 48967, 48460, 49230) allow impersonate serviceaccount in cli We can impersonate four kinds of resources according to the code: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/filters/impersonation.go#L83 **Release note**: ``` allow impersonate serviceaccount in cli ``` Fixes: https://github.com/kubernetes/kubernetes/issues/48260
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49218, 48253, 48967, 48460, 49230) Restrict the visibility of two generated packages in pkg/client/ These two packages are deprecated. Please use the client-go copy of these two packages. Currently staging/copy.sh copied these two packages to client-go. I'll send follow-up PRs to let code-gen output to client-go directly and remove these two packages. The purpose of this PR is to prevent more imports of these packages while I refactor the codegen.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48377, 48940, 49144, 49062, 49148) add some more deprecation warnings to cluster Part of https://github.com/kubernetes/kubernetes/issues/49213 @kubernetes/sig-cluster-lifecycle-misc
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48377, 48940, 49144, 49062, 49148) Add cos-dev-61-9733-0-0 to the benchmark tests Ref: https://github.com/kubernetes/kubernetes/issues/42926 m60 has docker 1.13.1 while m61 has 17.03. This PR adds m61 to the benchmark tests so that we will have more data to compare. PS: We will support fetching the latest image in an image family in the node e2e tests in the future. **Release note**: ``` None ``` /assign @yujuhong /cc @kewu1992 @abgworrall
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48377, 48940, 49144, 49062, 49148) fixit: break sig-cluster-lifecycle tests into subpackage this is part of fixit week. ref #49161 @kubernetes/sig-cluster-lifecycle-misc
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48377, 48940, 49144, 49062, 49148) support fc volume attach and detach **What this PR does / why we need it**: Support FC volume attach and detach to enforce RWO access **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #48953 **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
huzhifeng authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add PriorityClass API object under new "scheduling" API group **What this PR does / why we need it**: This PR is a part of a series of PRs to add pod priority to Kubernetes. This PR adds a new API group called "scheduling" with a new API object called "PriorityClass". PriorityClass maps the string value of priority to its integer value. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: Given the size of this PR, I will add the admission controller for the PriorityClass in a separate PR. **Release note**: ```release-note Add PriorityClass API object under new "scheduling" API group ``` ref/ #47604 ref/ #48646
-
Davanum Srinivas authored
Currently the only(?) toggle available for custom arch builds is KUBE_FASTBUILD. We should allow the user to specify a list of arch(es) in the environment variable KUBE_BUILD_PLATFORMS. Example: KUBE_BUILD_PLATFORMS="linux/amd64 linux/arm64" hack/build-cross.sh Fixes #20365
-
- 19 Jul, 2017 10 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47509, 46821, 45319, 49121, 49125) Tolerate a missing MasterName (for GKE) When testing, GKE created clusters don't provide a `MasterName`, so don't throw a warning and give up when that happens. ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47509, 46821, 45319, 49121, 49125) gce: don't add kubelet bearer token to known tokens
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47509, 46821, 45319, 49121, 49125) api types: fix protobuf names that are different from JSON name This PR fixes the naming of protobuf fields that are mismatched when compared to the JSON names. Because protobuf names aren't actually used during serialization, just the index, I think we can update these safely without changing the over the wire encoding (note that generated.pb.go doesn't change). Can someone verify that fixing the name won't impact backward compatibility? cc @kubernetes/sig-api-machinery-pr-reviews Fixes https://github.com/kubernetes/kubernetes/issues/45183 ```release-notes None ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47509, 46821, 45319, 49121, 49125) volume i/o tests for storage plugins **What this PR does / why we need it**: Addresses issues [25268](https://github.com/kubernetes/kubernetes/issues/25268) and [28367](https://github.com/kubernetes/kubernetes/issues/28367), though it may be weak re. the streaming i/o issue. @matchstick **Special notes for your reviewer**: This is a new file. Plugins other than NFS, GlusterFS, iSCSI, and Ceph-RBD code will need to be supported in a separate PR. ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Bump e2e mounttest image version to 0.8 Reduce the number of image files required for e2e test run ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue test/OWNERS: add zmerlynn ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Switch from gazel to kazel **What this PR does / why we need it**: switches to `kazel`, where all new development will be focused. Part of the effort for switching from `gazel` to `gazelle`. I'm imagining that we'll use `kube::util::go_install_from_commit` to version `gazelle` as well. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: x-ref #47558 **Release note**: ```release-note NONE ``` /release-note-none /assign @mikedanese @spxtr
-
Davanum Srinivas authored
Current devstack seems to return "id", and an upcoming change using nova's microversion will be returning "original_name": https://blueprints.launchpad.net/nova/+spec/instance-flavor-api So let's just inspect what is present and use that to figure out the instance type.
-
deads2k authored
-
Zach Loafman authored
-