Skip to content

Bug 1949050: Pull upstream changes for 1.21#60

Merged
openshift-merge-robot merged 46 commits intoopenshift:masterfrom
damemi:1.21-bump
Apr 22, 2021
Merged

Bug 1949050: Pull upstream changes for 1.21#60
openshift-merge-robot merged 46 commits intoopenshift:masterfrom
damemi:1.21-bump

Conversation

@damemi
Copy link

@damemi damemi commented Apr 21, 2021

No description provided.

seanmalloy and others added 30 commits March 1, 2021 09:23
For roughly the past year damemi has been the only active approver for
the descheduler. Therefore move the inactive approvers to emeritus
status. This will help clarify to contributors who should be assigned to
pull requests.
Set the maintainer field to use the more generic SIG scheduling name and
email address.
Add table of contents generator/verify script
Add ARM32v7 in addition to the currently supported architectures. This
will allow running descheduler on Raspberry Pi v3 devices.
…approvers

Move Inactive Maintainers to Emeritus Status
The resources.cpuRequest and resources.memoryRequest varialbes are
not valid in the helm chart values.yaml file. The correct varialbe
name for setting the requests and limits is resources.

Also, fixed white space alignment in the markdown table.
…lector-fix

(TopologySpread) Evict pods with selectors that match multiple nodes
…s-fix

Correct Helm Chart Docs For Container Requests and Limits
Similar to ReplicaSet, ReplicationController, and Jobs pods with a
StatefulSet metadata.ownerReference are considered for eviction.
Document this, so that it is clear to end users.
…et-docs

Document That Descheduler Considers StatefulSets For Eviction
The master branch always represents the next release of the
descheduler. Therefore applying the descheduler k8s manifests
from the master branch is not considered stable. It is best for
users to install descheduler using the released tags.
…-docs

Use Tags In Kustomize Documentation
Added EvictSystemCriticalPods flag to descheduler
* Added v0.21 references to README
* Update k8s manifests with v0.21.0 references
* Added table with list of supported architectures by release
Ran "make gen" using Go 1.16.1. Some changes were merged, but "make gen"
was not run. This fixes the problem.

See below PR for reference:
kubernetes-sigs#523
Copy link
Author

@damemi damemi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/cc @ingvagabund
we can get some 1.21 soak while we're waiting for the kind image to actually release upstream 1.21

@ingvagabund
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 21, 2021
@damemi damemi changed the title Pull upstream changes for 1.21 Bug 1949050: Pull upstream changes for 1.21 Apr 21, 2021
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Apr 21, 2021
@openshift-ci-robot
Copy link

@damemi: This pull request references Bugzilla bug 1949050, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.8.0) matches configured target release for branch (4.8.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @zhouying7780

Details

In response to this:

Bug 1949050: Pull upstream changes for 1.21

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.

@damemi
Copy link
Author

damemi commented Apr 21, 2021

/retest

@openshift-ci-robot
Copy link

@damemi: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 1949050 has not been moved to the MODIFIED state.

Details

In response to this:

Bug 1949050: Pull upstream changes for 1.21

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.