Bug 1874056: 1.19.0 bump #39
Conversation
…pointer Promote Namespaces field to a pointer
Changing the maintainer for the helm chart to SIG scheduling instead of an individual person.
…t-update Update Maintainer Details In Helm Chart
Use WithXXX methods to extend the list of constraints to also provide a reasonable error message.
Redefine IsEvictable to be customizable for a particular strategy
Add table of contents to README
…torage-pods flags and promote then to policy v1alpha1 fields
…gs-under-descheduler-polic Deprecate node-selector, max-pods-to-evict-per-node and evict-local-storage-pods flags and promote then to policy v1alpha1 fields
Bump k8s Modules For k8s 1.19
Add KUBECONFIG Export To Contributing Docs
…ization-use-clientset-in-testing LowNodeUtilization: use clientset in testing, drop all custom reactors
As part of the k8s 1.19 release cycle the Go version is being bumped to 1.15.0. Updating the descheduler to use Go 1.15 prior to the descheduler v0.19.0 release. See below issues for reference: * kubernetes/release#1421 * kubernetes/kubernetes#93484
Update To Go 1.15.0
* Added v0.19 references to README * Update k8s manifests with v0.19.0 references
Update Docs and Manifests for v0.19.0
|
/cc @ingvagabund The one thing I'm not sure of is the upstream switch to go 1.15, I'm not clear on if our build tooling is on 1.15 yet |
1.14 at most |
|
/lgtm |
openshift-ci-robot
added
the
bugzilla/severity-urgent
|
@damemi: This pull request references Bugzilla bug 1874056, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci-robot
added
the
bugzilla/valid-bug
|
@damemi: All pull requests linked via external trackers have merged: Bugzilla bug 1874056 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This pulls the upstream 1.19.0 changes into master