- 07 Jul, 2016 17 commits
-
-
Mike Danese authored
Signed-off-by:Mike Danese <mikedanese@google.com>
-
Mike Danese authored
Signed-off-by:Mike Danese <mikedanese@google.com>
-
k8s-merge-robot authored
Automatic merge from submit-queue Make kubectl help strings consistent
-
k8s-merge-robot authored
Automatic merge from submit-queue Reformat kubectl completion example text
-
k8s-merge-robot authored
Automatic merge from submit-queue "was not created" should be "was created" In file pkg\client\restclient/request_test.go, line #1089, "t.Errorf("expected object was not created")" , here "was not created" should be "was created" because the if condition is "if wasCreated". -
k8s-merge-robot authored
Automatic merge from submit-queue delete the redundant word "a" In file docs/reporting-security-issues.md, line #37, "If you believe you have discovered a vulnerability or a have a security incident to report", here the second "a" is redundant, should be deleted.
-
k8s-merge-robot authored
Automatic merge from submit-queue kubectl convert --local prints info message to stderr fix #28298
-
k8s-merge-robot authored
Automatic merge from submit-queue fix some typos Just a minor typos fix. Signed-off-by:bin liu <liubin0329@gmail.com>
-
k8s-merge-robot authored
Automatic merge from submit-queue daemon/controller.go: remove unused func enqueueAllDaemonSets
-
k8s-merge-robot authored
Automatic merge from submit-queue Collect cluster state into a single type. Mostly just makes it easier to read and, hopefully, extend.
-
k8s-merge-robot authored
Automatic merge from submit-queue [client-gen] stop update release_1_3 clientset; create release_1_4 We'll bump the version after we cut 1.3 release. I'll keep this PR assigned to myself in the mean time. @lavalamp
-
k8s-merge-robot authored
Automatic merge from submit-queue kubectl should print usage at the bottom Override the Usage: output using SetUsageTemplate. Just moved the strings in the template to make sure we print Usage: at the bottom of the output and not at the top. Fixes issue #7496
-
k8s-merge-robot authored
Automatic merge from submit-queue getting emailAddress from TLS cert Kubernetes if using TLS cert to perform authentication will use the CommonName field of the cert as the authenticating user. In https://github.com/kubernetes/kubernetes/blob/master/plugin/pkg/auth/authenticator/request/x509/x509.go#L106, alternative methods are defined to use emailAddress or DNSName as the authenticating user. The method that uses the emailAddress is not comprehensive as this information can be encoded in different places of the certificate. This PR fixes this.
-
k8s-merge-robot authored
Automatic merge from submit-queue Add spec.Name() to the configmap GetVolumeName() This is to base the name on the volume not just on the source configMap. If you have 2 volumes that both have the same configMap as a source, the volume is see as being in the attached state (it's state is looked up based on GetVolumeName()). Fixes #28502
-
k8s-merge-robot authored
Automatic merge from submit-queue Copy FEDERATIONS_DOMAIN_MAP to a local variable since the helper script doesn't allow overwriting the existing variable. cc @kubernetes/sig-cluster-federation []()
-
k8s-merge-robot authored
Automatic merge from submit-queue Revert "Declare out of disk when there is no free inodes" Reverts kubernetes/kubernetes#28176 Fixes #28481
-
k8s-merge-robot authored
Automatic merge from submit-queue E2E: Add UpdatePod function in e2e framework and change the test to use it. Fix https://github.com/kubernetes/kubernetes/issues/28096. Some e2e tests need to update pod, but the pod update is a bit complex because of potential conflict. #28096 happened just because the test only called pod `Update` once. This PR move the update pod logic into a util function `UpdatePod` in e2e framework, and change the tests to use it. Mark P2 because the original issue is P0, but in fact happens not quite frequently. :) []() the test to use it.
-
- 06 Jul, 2016 23 commits
-
-
k8s-merge-robot authored
Automatic merge from submit-queue Document known issues for v1.3.0
-
Madhusudan.C.S authored
Copy FEDERATIONS_DOMAIN_MAP to a local variable since the helper script doesn't allow overwriting the existing variable.
-
Madhusudan.C.S authored
Copy FEDERATIONS_DOMAIN_MAP to a local variable since the helper script doesn't allow overwriting the existing variable.
-
Matt Liggett authored
-
Matt Liggett authored
-
Matt Liggett authored
-
Matt Liggett authored
-
Matt Liggett authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Add test/test_owners.csv, for automatic assignment of test failures. This file will be read by the munger -- see kubernetes/contrib#1264 This also includes a simple script to do minor automatic updates to the CSV. I'd like to get `update_owners.py` into a more usable state -- right now the CSV is based directly on the Google Sheets data. It has 9 outdated tests and is missing 80 new tests. I can randomly assign new tests to people on kubernetes-maintainers, but are there any caveats to how the assignment should work? Should they be load balanced? Should some people in the group not receive issues? Etc. -
k8s-merge-robot authored
Automatic merge from submit-queue Test for certificate error and prompt to regenerate This resolves an issue where if the `${DOCKER_MACHINE_NAME}` VM was ever removed from `docker-machine` the build process would enter an infinite loop, with the following error being redirected to `/dev/null`. >Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.102:2376": open /Users/weeks/.docker/machine/machines/kube-dev/server.pem: no such file or directory You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'. Be advised that this will trigger a Docker daemon restart which will stop running containers. Now the output is tested for the error string and if found prompts the user if they want to regenerate the certificate. Another option would be setting the `--force` flag on `docker-machine regenerate-certs`, so user intervention wouldn't be required. /cc @mhbauer <!-- Reviewable:start --> --- This change is [<img src="http://reviewable.k8s.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](http://reviewable.k8s.io/reviews/kubernetes/kubernetes/24992) <!-- Reviewable:end --> -
k8s-merge-robot authored
Automatic merge from submit-queue Updating release notes v1.2.2..v1.2.3 v1.2.3..v1.2.4 v1.2.4..v1.2.5 v1.2.0..v1.3.0-alpha.1 v1.3.0-alpha.1..v1.3.0-alpha.2 v1.3.0-alpha.2..v1.3.0-alpha.3 v1.3.0-alpha.3..v1.3.0-alpha.4 v1.3.0-alpha.4..v1.3.0-alpha.5 v1.3.0-alpha.5..v1.3.0-beta.1 v1.3.0-beta.1..v1.3.0-beta.2 v1.3.0-beta.2..v1.3.0-beta.3 First pass. -
Madhusudan.C.S authored
-
Ryan Hitchman authored
-
Eli Young authored
This makes the description wrap properly in 80-character terminals.
-
krousey authored
Revert "update jwt-go to v3.0.0-4-g01aeca5"
-
Random-Liu authored
the test to use it.
-
Chao Xu authored
-
krousey authored
-
Brandon Weeks authored
If the docker-machine certificates get in a bad state, the current behavior causes an infinite loop waiting for `docker-machine env` to return. Now it will echo the certificate error and prompt the user to regenerate.
-
k8s-merge-robot authored
Automatic merge from submit-queue kubectl/autoscale: fix tips when validating --max flag While autoscaling, it was not clear what was the reason of failed --max flag validation. This fix divides reasons to: - value not provided or too low - value of max is lower than value of min bug 1336632 Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=1336632
-
ronnielai authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix minor typo Fix for a really minor typo in development.md @thockin PTAL.
-
Angus Salkeld authored
This is to base the name on the volume not just on the source configMap. If you have 2 volumes that both have the same configMap as a source, the volume is see as being in the attached state (it's state is looked up based on GetVolumeName()). See bug #28502
-