- 28 Jul, 2017 17 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47738, 49196, 48907, 48533, 48822) Fix TODO: rename podInfraContainerID to sandboxID **What this PR does / why we need it**: Code-cleanup in kubelet to use consistent naming for sandbox ID. Not super urgent, but thought it would be nice to knock off some TODOs. **Which issue this PR fixes** Fixes a TODO in the code, no associated issue. **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47738, 49196, 48907, 48533, 48822) Fix a dead link in cluster/update-storage-objects.sh **What this PR does / why we need it**: This PR fixes a dead link in cluster/update-storage-objects.sh. **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 (batch tested with PRs 47738, 49196, 48907, 48533, 48822) Bumps go-oidc version to include fix for jwt header parsing **What this PR does / why we need it**: This bumps the go-oidc dependency to use a fix merged in https://github.com/coreos/go-oidc/pull/153 for OIDC providers that don't set an `Expires` header **Which issue this PR fixes** : Partially addresses #42654 Also related: https://github.com/coreos/go-oidc/issues/136 **Special notes for your reviewer**: None **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47738, 49196, 48907, 48533, 48822) Move e2e dependent images from kubernetes/kubernetes.github.io repo **What this PR does / why we need it**: Move e2e dependent images from kubernetes/kubernetes.github.io repo **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #48530 **Special notes for your reviewer**: **Release note**: ```NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47738, 49196, 48907, 48533, 48822) ParseEncryptionConfiguration: simplify code **What this PR does / why we need it**: Reorder `if`-s to make code a bit more readable. It also improves godoc comment and error message. **Release note**: ```release-note NONE ``` PTAL @sakshamsharma
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49238, 49595, 43494, 47897, 48905) adds an admission plugin initializer to the sample apiserver. **What this PR does / why we need it**: this PR adds an admission plugin initializer to the sample apiserver. the plugin initializer is going to be used by an admission plugin that will use generated informers/listers to list the cluster-scoped resources. #47868 **Release note**: ``` NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49238, 49595, 43494, 47897, 48905) remove dead code in rbac helper **What this PR does / why we need it**: validated in `case len(r.PolicyRule.NonResourceURLs) > 0:` . **Which issue this PR fixes**: #49540 **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49238, 49595, 43494, 47897, 48905) Should not set struct pointer directly to interface which may cause potential panic fix https://github.com/kubernetes/kubernetes/issues/43127 to avoid potential kubelet panic. In our old implemention, interface `kubeDeps.EventClient ` (interface) will never equals to `nil` even if `eventClient `(struct pointer )was set to `nil`. `kubeDeps.ExternalKubeClient` and `kubeDeps.KubeClient` also have same potential risk.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49238, 49595, 43494, 47897, 48905) bug fixes in GCE cloud provider fixes: #49657 #49150 ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49238, 49595, 43494, 47897, 48905) Add apps/v1beta2.ReplicaSet ~Depends on #48746~ (merged) ~Depends on #49357~ (merged) xref: #49135 ```release-note Add a new API object apps/v1beta2.ReplicaSet ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue fix pdb validation bug on spec **What this PR does / why we need it**: When working on issue #48691, I found a bug on current [pdb validation on spec](https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/policy/validation/validation.go#L41-L42). This validation is to check `PodDisruptionBudgetSpec` instead of the whole obj. Currently when doing updates, this check will fail as always. **Which issue this PR fixes** : fix #48691 **Special notes for your reviewer**: **Release note**: ```release-note fix pdb validation bug on PodDisruptionBudgetSpec ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update the link to client-gen doc The doc itself also needs update, i'll create an issue.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49665, 49689, 49495, 49146, 48934) Add Integration tests for Inter-Pod Affinity(AntiAffinity) Signed-off-by:vikaschoudhary16 <choudharyvikas16@gmail.com> **What this PR does / why we need it**: Adds integration tests for inter-pod affinity(anti-affinity) **Special notes for your reviewer**: Once after @bsalamat 's #48847 gets merged, changes in this PR will be restructured according to the merged changes. ref/ #48176 #48847 @kubernetes/sig-scheduling-pr-reviews @davidopp @k82cn
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49665, 49689, 49495, 49146, 48934) openapi: refactor into more generic structure **What this PR does / why we need it**: Refactor the openapi schema to be a more generic structure that can be "visited" to get more specific types. Will be used by validation. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: #44589 **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49665, 49689, 49495, 49146, 48934) make it possible to allow discovery errors for controllers Update the discovery client to return partial discovery information *and* an error. Since we can aggregate API servers, discovery of some resources can fail independently. Callers of this function who want to tolerate the errors can, existing callers will still get an error and fail in normal blocks. @kubernetes/sig-api-machinery-misc @sttts
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 49665, 49689, 49495, 49146, 48934) Reverting deprecation of vCenter port in vSphere Cloud Provider **What this PR does / why we need it**: This PR reverts back the deprecation of vCenter port made with PR: kubernetes#42024 We observed an issue when kubernetes cluster is deployed on the vCenter with non-default Port. When VC is configured with non default port govmomi requests were going to default port 443. This is not valid, as confirmed in https://github.com/vmware/govmomi/issues/802 **Which issue this PR fixes** fixes # https://github.com/vmware/kubernetes/issues/220 **Special notes for your reviewer**: Verified with deploying Kubernetes Cluster on the vCenter with port (7443). Used following vsphere.conf file on master and worker nodes ``` # cat vsphere.conf [Global] user = "Administrator@vsphere.local" password = "Admin!23" server = "10.192.87.209" port = "7443" insecure-flag = "1" datacenter = "Datacenter" datastore = "storage1" working-dir = "kubernetes" [Disk] scsicontrollertype = pvscsi ``` Created Storage Class, PV, PVC and Pod. Verified Attach, Detach, Create and Delete Volume Operations are working as expected. Also verified with completely removing port from vsphere.conf file. default 443 is used in this case. ``` # cat vsphere.conf [Global] user = "Administrator@vsphere.local" password = "Admin!23" server = "10.192.66.216" insecure-flag = "1" datacenter = "Datacenter" datastore = "storage1" working-dir = "kubernetes" [Disk] scsicontrollertype = pvscsi ``` **Release note**: ```release-note NONE ``` @luomiao @BaluDontu @tusharnt @rohitjogvmw
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix log-dump script wrt logexporter
-
- 27 Jul, 2017 5 commits
-
-
Chao Xu authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Change e2e-framework behavior to retry retriable API errors Fixes https://github.com/kubernetes/kubernetes/issues/46195 We shouldn't return with failure just because api call failed during polling. Happens from time to time, for e.g https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-kubemark-5-gce/16896 /cc @wojtek-t
-
divyenpatel authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Tune Cinder approvers I don't want to be single approver for cinder PRs, @anguslees is OpenStack maintainer and should be able to help with Cinder. Any other volunteers from @kubernetes/sig-storage-pr-reviews or @k8s-sig-openstack-pr-reviews? Note: @justinsb **is** still reviewer, he was just listed twice. ```release-note NONE ```
-
vikaschoudhary16 authored
Signed-off-by:vikaschoudhary16 <choudharyvikas16@gmail.com>
-
- 26 Jul, 2017 18 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add OWNERS file for Calico add-on **What this PR does / why we need it**: Adds @caseydavenport and @fasaxc as owners to the Calico add-on. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # No related issue. **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Shyam Jeedigunta authored
-
Casey Davenport authored
-
deads2k authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48360, 48469, 49576, 49516, 49558) Update maintainers for Juju charm layers **What this PR does / why we need it**: Update maintainers of harm layers to reflect ... reality **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: **Special notes for your reviewer**: **Release note**: ```NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48360, 48469, 49576, 49516, 49558) Let garbage collector send orphaning patches in parallel Garbage collector sends orphaning patches in parallel now.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48360, 48469, 49576, 49516, 49558) apimachinery: fix meta/v1alpha1.Table deepcopy
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48360, 48469, 49576, 49516, 49558) Rev Calico's Typha daemon to v0.2.3 in add-on deployment. **What this PR does / why we need it**: This PR revs the version of Calico's Typha daemon used in the calico-policy-controller add-on to the latest bug-fix release, which incorporates a [critical bug fix](https://github.com/projectcalico/typha/issues/28). **Which issue this PR fixes** fixes #49473 **Release note**: ```release-note Rev version of Calico's Typha daemon used in add-on to v0.2.3 to pull in bug-fixes. ```
-
Minhan Xia authored
Fixes bug where the network used in the cloud provider was not taken from the /etc/gce.conf configuration. This can result in firewalls, routes and other network resources being created on the wrong network.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Set snat to false **What this PR does / why we need it**: - the [version](https://github.com/containernetworking/plugins/commit/e8bea554c5ec9a433d4353c03f7f31b068185c1c) of the portmap plugin included with calico CNI version `v1.9.1` doesn't have `noSnat` config option, it has `snat` which is not specified (which is the case without this PR), [will be set to true by default](https://github.com/containernetworking/plugins/tree/master/plugins/meta/portmap#usage) , so we need to explicitly set it to `false` CC @caseydavenport
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47357, 49514, 49271, 49572, 49476) enhance kubectl run error message Before this change: $ kubectl run nginx error: Invalid image name "": invalid reference format After this change: $ kubectl run nginx error: --image is required **Release note**: ``` NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47357, 49514, 49271, 49572, 49476) Updates etcd-client to 3.1.10 I have no idea why azure sdk update became transitive but godeps we're restored before update Fixes: https://github.com/kubernetes/kubernetes/issues/49386 xref: https://github.com/kubernetes/kubernetes/pull/49393 ``` NONE ``` /cc @kubernetes/sig-scalability-pr-reviews @kubernetes/sig-api-machinery-misc @hongchaodeng @wojtek-t
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47357, 49514, 49271, 49572, 49476) set default adminid for rbd deleter if unset **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 #49225 **Special notes for your reviewer**: /cc @BastiPaeltz @sjenning **Release note**: ```release-note set default adminid for rbd deleter if unset ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47357, 49514, 49271, 49572, 49476) Move client cert bootstrap code into pkg/kubelet/... Keeps it better encapsulated. @deads2k
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47357, 49514, 49271, 49572, 49476) Using only the exit code to decide when to fall back on logs We expect the exit code to be non-zero if the the container process was OOM killed. Remove the check that uses the "Reason" field.
-
Janet Kuo authored
-
p0lyn0mial authored
the plugin initializer is going to be used by an admission plugin that will use generated informers/listers to list the cluster-scoped resources.
-
Janet Kuo authored
test/e2e_federation/replicaset.go complains: ambiguous selector cluster.ReplicaSets
-