-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge https://github.com/kubernetes/autoscaler:master (04b1402) into master #308
Merge https://github.com/kubernetes/autoscaler:master (04b1402) into master #308
Conversation
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. |
191d1fe
to
56fb6d8
Compare
56fb6d8
to
dd620e1
Compare
dd620e1
to
cf9cc43
Compare
Rename migInstancesState to migInstancesStateCount in gce cache
cf9cc43
to
2be8374
Compare
…and for listing migInstances add metrics for inconsistent mig count
add metrics for function duration for listing gce instances and metrics for inconsistent mig count when gce bulk instance listing is enabled
…tor-scale-up Extract few steps from ScaleUpOrchestrator main logic
fix(clusterapi): HasInstance with namespace prefix
…le-down BookCapacity for ProvisioningRequest pods
…vertical-pod-autoscaler/pkg/updater/golang-1.22.5 Bump golang from 1.22.4 to 1.22.5 in /vertical-pod-autoscaler/pkg/updater
…vertical-pod-autoscaler/pkg/recommender/golang-1.22.5 Bump golang from 1.22.4 to 1.22.5 in /vertical-pod-autoscaler/pkg/recommender
…vertical-pod-autoscaler/pkg/admission-controller/golang-1.22.5 Bump golang from 1.22.4 to 1.22.5 in /vertical-pod-autoscaler/pkg/admission-controller
…pace Add option to ignore namespaces
Update CA FAQ to point to the new location of dependency update script.
Update args to match update-deps.sh usage API module may have different k8s dependency from CA itself.
2be8374
to
511449b
Compare
…es-patch-2 kwok CAS: update README docs to include helm repo add
this is going to require a manual rebase, i'm not sure what is happening here yet |
ad7fc44
to
065c5f1
Compare
fix(hetzner): deprecated server type will break on 2024-09-06
* Add backoff mechanism for ProvReq retry * Add flags for intital and max backoff time, and cache size * Review remarks * Add LRU cache * Review remark
This change carries files and modifications that are used by OpenShift release infrastructure and related files. * spec file * dockerfiles * vertical-pod-autoscaler/Dockerfile.rhel * 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 * update vendor folders * add vendor folder for balancer * add Snyk file to exclude vendor directories and problematic cloud providers on scan # Conflicts: # cluster-autoscaler/cloudprovider/azure/OWNERS
…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 removes the `go test -i ...` command from the hack/test-go.sh file. this option is deprecated in the go command and attempts to install dependencies of the test. when this is enabled with the build tags we are using, it appears to make the test builds unstable in CI.
this change adds all the cloudproviders except clusterapi to the list of ignored directories in for the cluster-autoscaler tests. this is being done so that the tests match our build tags and do not cause errors when passing the package list to the test script.
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.
…ge to be consistent with ART for 4.17 Reconciling with https://github.com/openshift/ocp-build-data/tree/4c1326094222f9209876f06833179a1b9178faf7/images/vertical-pod-autoscaler.yml
…ge to be consistent with ART for 4.17 Reconciling with https://github.com/openshift/ocp-build-data/tree/39d776b80aa929c42b98e8c50c25162b97b14e06/images/vertical-pod-autoscaler.yml
…iner image to be consistent with ART for 4.18 Reconciling with https://github.com/openshift/ocp-build-data/tree/1c7e6e27058c4590e342ecabe8bc96feeb68e7e5/images/atomic-openshift-cluster-autoscaler.yml
…ge to be consistent with ART for 4.18 Reconciling with https://github.com/openshift/ocp-build-data/tree/827ab4ccce9cbbcf82c9dbaf6398b61d6cff8d7a/images/vertical-pod-autoscaler.yml
065c5f1
to
500c138
Compare
@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. |
setting this to manual rebase since it will require intervention /label rebase/manual |
this is superseded by #319 /close |
@elmiko: Closed this PR. 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-sigs/prow repository. |
No description provided.