Merge https://github.com/kubernetes/autoscaler:cluster-autoscaler-1.34.0 (dd28ada) into main #356
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![cloud-team-rebase-bot[bot]](https://avatars.githubusercontent.com/u/74064623?s=60&v=4){kind=small}
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @cloud-team-rebase-bot[bot]. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
Add "volumeattachments". See similar changes in kubernetes@e79b5b8
…-groups Add created node group to considered node groups during scale-up
Update deployment.yaml to add volumeattachments permission
|
unlikely this will work, but might as well try /ok-to-test |
openshift-ci
bot
added
ok-to-test
cloud-team-bot
bot
force-pushed
the
rebase-bot-main
branch
from
608b295 to
1e2080a
Compare
Fix(VPA): updater in-place metrics initialization
fix(VPA): Do not update webhook CA when registerWebhook is disabled
Signed-off-by: Yuriy Losev <[email protected]>
Signed-off-by: Yuriy Losev <[email protected]>
Signed-off-by: Yuriy Losev <[email protected]>
[VPA] Use factory start to fill caches instead of separate informers
cloud-team-bot
bot
force-pushed
the
rebase-bot-main
branch
from
1e2080a to
7149ebf
Compare
…t-success OCI provider: Avoid interpreting HTTP 404 as success on delete
…-cloud-endpoint-reloving fix bug 8168 GetEndpoint resolving fail
…e-terminate-by-default feat: cordon node before terminate by default
this change adds debug logs at level 5 to aid in triaging failed node balancing. It adds logs to help determine why two node groups are not considered as similar. These logs can be quite noisy so the logging level has been set to 5 by default.
AEP-7862: Decouple Startup CPU Boost from VPA modes - updates
* add h4d pricing * fix go fmt * revert gofmt on other files
cluster-autoscaler: add logging for failed node balancing
…r-ca Add capacity buffers scalable objects, limits and fake pods injection
cloud-team-rebase-bot
bot
changed the title
cloud-team-bot
bot
force-pushed
the
rebase-bot-main
branch
from
fc57b3d to
9145380
Compare
openshift-ci
bot
removed
the
do-not-merge/invalid-owners-file
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* deprecate * fix
Update versions to correct values
Deprecate ProvisioningRequest v1beta1 (kubernetes#8549)
Fix capacity buffers injector order in pod list processor
cloud-team-rebase-bot
bot
changed the title
cloud-team-bot
bot
force-pushed
the
rebase-bot-main
branch
from
9145380 to
aee39d7
Compare
openshift-ci
bot
added
the
do-not-merge/invalid-owners-file
This change carries files and modifications that are used by OpenShift release infrastructure and related files. * spec file * dockerfiles * vertical-pod-autoscaler/Dockerfile.rhel * vertical-pod-autoscaler/Dockerfile.openshift * images/cluster-autoscaler/Dockerfile * images/cluster-autoscaler/Dockerfile.rhel * hack scripts (ci and build related) * Makefile * JUnit tools * update gitignore * update/remove OWNERS files * ci-operator config yaml * remove gitignore file from vertical-pod-autoscaler (allow vendor addition) * add Snyk file to exclude vendor directories and problematic cloud providers on scan # Conflicts: # OWNERS_ALIASES # cluster-autoscaler/OWNERS # vertical-pod-autoscaler/OWNERS
Add vendor folders * cluster-autoscaler * balancer * vertical-pod-autoscaler * vertical-pod-autoscaler/e2e
…otation The delete annotation upstream has a different format, but is now inferred dynamically from the API group. If we update this in MAO to use the new format, we can drop this old key
This change re-adds the machine api support for labels and taints on node groups. The code was removed upstream as it is openshift specific, see this pull request[0]. It also adds in the functionality of the upstream override annotation for labels and taints[1] to support https://issues.redhat.com/browse/MIXEDARCH-259 [0]: kubernetes#5249 [1]: kubernetes#5382
the upstream annotations for the scale from zero capacity resources is slighty different than the openshift implementation. the largest difference is the addition of a gpu type annotation. openshift does not yet utilize this annotation and thus this patch should be carried until the machineset controllers for the various providers on openshift have been modified to use the new annotations. another important change is the modification of the memory annotation. previously in openshift we expected this value to be a count of memory in Mebibytes. the conversion function and tests have been modified to allow continued openshift operation. this change can be dropped when the annotations in openshift have been updated, the progress for this effort can be followed at https://issues.redhat.com/browse/OCPCLOUD-944
…ider This change corrects the behavior for parsing taints from the unstructured scalable resource. This is required on OpenShift as our implementation is slightly different from the upstream.
Also: * Add unit tests for upstream annotations * Update unit tests using upstream annotations new values
This OWNERS file is no longer autogenerated by Cluster Infrastructure owner-gen tooling.
…iner image to be consistent with ART for 4.21 Reconciling with https://github.com/openshift/ocp-build-data/tree/4fbe3fab45239dc4be6f5d9d98a0bf36e0274ec9/images/atomic-openshift-cluster-autoscaler.yml
…ge to be consistent with ART for 4.21 Reconciling with https://github.com/openshift/ocp-build-data/tree/4fbe3fab45239dc4be6f5d9d98a0bf36e0274ec9/images/vertical-pod-autoscaler.yml
cloud-team-bot
bot
force-pushed
the
rebase-bot-main
branch
from
aee39d7 to
1b9cc5f
Compare
|
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing
|
|
@cloud-team-rebase-bot[bot]: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.