- 19 Feb, 2019 22 commits
-
-
Kubernetes Prow Robot authored
Fix golint failures on cmd/apis/extensions/...
-
Kubernetes Prow Robot authored
Fix reconstruction of FC volumes
-
Kubernetes Prow Robot authored
kubeadm: graduate control plane join phase
-
Kubernetes Prow Robot authored
Don't return CSI driver unregistration error
-
Kubernetes Prow Robot authored
Remove todos from init upload certs
-
Anago GCB authored
-
Kubernetes Prow Robot authored
Use Request Object interfaces instead of static scheme that is more appropriate for CRDs
-
Kubernetes Prow Robot authored
Remove race condition with run-test
-
Kubernetes Prow Robot authored
kubeadm: Don't load deprecated configs
-
Rostislav M. Georgiev authored
Currently kubeadm supports a couple of configuration versions - v1alpha3 and v1beta1. The former is deprecated, but still supported. To discourage users from using it and to speedup conversion to newer versions, we disable the loading of deprecated configurations by all kubeadm sub-commands, but "kubeadm config migrate". v1alpha3 is still present and supported at source level, but cannot be used directly with kubeadm and some of its internal APIs. The added benefit to this is, that users won't need to lookup for an old kubeadm binary after upgrade, just because they were stuck with a deprecated config version for too long. To achieve this, the following was done: - ValidateSupportedVersion now has an allowDeprecated boolean parameter, that controls if the function should return an error upon detecting deprecated config version. Currently the only deprecated version is v1alpha3. - ValidateSupportedVersion is made package private, because it's not used outside of the package anyway. - BytesToInitConfiguration and LoadJoinConfigurationFromFile are modified to disallow loading of deprecated kubeadm config versions. An error message, that points users to kubeadm config migrate is returned. - MigrateOldConfig is still allowed to load deprecated kubeadm config versions. - A bunch of tests were fixed to not expect success if v1alpha3 config is supplied. Signed-off-by:Rostislav M. Georgiev <rostislavg@vmware.com>
-
Kubernetes Prow Robot authored
Fix golint failures
-
Kubernetes Prow Robot authored
fixes: some wrong comments
-
Kubernetes Prow Robot authored
Fix websocket e2e tests for https endpoints
-
RA489 authored
-
Kubernetes Prow Robot authored
Fix broken list of 'Service/Publishing services - service types'
-
Kubernetes Prow Robot authored
Add code comments to guard inadvertent removal of insecure-bind-address
-
Kubernetes Prow Robot authored
Correcting error on source codes
-
Kubernetes Prow Robot authored
Add e2e test for scale sub-resource of statefulsets
-
Kubernetes Prow Robot authored
Merge pull request #73961 from mattjmcnaughton/mattjmcnaughton/clarify-NetworkPolicy-policyTypes-in-docs Clarify NetworkPolicy policyTypes in docs
-
Kubernetes Prow Robot authored
Change kubelet metrics to conform metrics guidelines
-
Kubernetes Prow Robot authored
Correct the count of evictionsNumber
-
Yago Nobre authored
-
- 18 Feb, 2019 18 commits
-
-
Kubernetes Prow Robot authored
allow apiservers to override the list of decorators
-
Kubernetes Prow Robot authored
Handling for use_custom_instance_list in dump_nodes_with_logexporter
-
Kubernetes Prow Robot authored
remove unnecessary scheme from config struct
-
Kubernetes Prow Robot authored
prevent unhandled errors on colliding poststarthook registration
-
Kubernetes Prow Robot authored
Ensure prometheus metrics are not registered twice
-
David Eads authored
-
David Eads authored
-
David Eads authored
-
Kubernetes Prow Robot authored
kubeadm: drop applyFlags.newK8sVersion field
-
Kubernetes Prow Robot authored
kubeadm: Replace MigrateOldConfigFromFile
-
Justin SB authored
Though the flags are deprecated, the deprecation process revealed that the flag is important for health checks in more secure environments. Add a link to #43784 to help developers understand why the flags have not yet been removed. Issue #43784 Issue #74172 Issue #59018
-
Kubernetes Prow Robot authored
kubeadm: use non-formatting constructor for new error
-
Dmitry Rozhkov authored
since it's not a command line flag. Use a variable instead.
-
Kubernetes Prow Robot authored
Windows networking tests
-
renxiang authored
-
Kubernetes Prow Robot authored
Provision vsphere volume as per zone
-
danielqsj authored
-
Mikkel Oscar Lyderik Larsen authored
Signed-off-by:Mikkel Oscar Lyderik Larsen <mikkel.larsen@zalando.de>
-