*: Cut v2.7.0 #1896
Merged
*: Cut v2.7.0 #1896
Conversation
This file contains 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
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
approved
Adds deletionTimestamp metric, for nodes. Signed-off-by: Pranshu Srivastava <rexagod@gmail.com>
Add node deletionTimestamp metric
--config flag defines the path to the kube-state-metrics options config file.
Reload KSM on-the-fly when a change is detected in the configuration. Meta changes (will squash)
Add end-to-end testing to verify hot-reloading for event-based changes stemming from the config file. Also, * sent in a doc fix that was missed earlier: https://github.com/kubernetes/kube-state-metrics/pull/1890/files#diff-380eca5a922c0ddbf67f04daefc6823e7ef0e197434d3a826d39c7063cdfa6d6R15, * updated fsnotify and viper dependencies (v1.6.0 and v1.14.0 respectively). Signed-off-by: Pranshu Srivastava <rexagod@gmail.com>
rexagod
reviewed
Nov 16, 2022
Incorporate Viper
Closed
5 tasks
|
I fell sick last week, so will work on this release next week. Apologies for the delay. |
mrueg
force-pushed
the
prep-release-2.7
branch
from
82c7ace
to
4c36180
Compare
k8s-ci-robot
added
size/XL
mrueg
force-pushed
the
prep-release-2.7
branch
from
4c36180
to
5058046
Compare
update kube_node_status_{capacity/allocatable} doc to clarify difference
Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>
dgrisonnet
reviewed
Nov 22, 2022
|
No worries at all! I think we still wanted to have #1851 in the release anyway. |
mrueg
force-pushed
the
prep-release-2.7
branch
from
5058046
to
4ffaf18
Compare
Add rexagod as reviewer
|
No need to put pressure on yourself to have it done for 2.7, we can defer it to the next release and increase the release frequency |
|
/lgtm @mrueg feel free to remove the hold when you are ready |
k8s-ci-robot
added
do-not-merge/hold
Issue: kubernetes#1711 Problem: kube-state-metrics supports up to (latest k8s release - 3) k8s version. Since v1.25 has been release we can update it to start using autoscaler/v2. Solution: update packages to start using autoscaler/v2 Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>
Start using autoscaling/v2 for HorizontalPodAutoscaler
Co-authored-by: Damien Grisonnet <damien.grisonnet@epita.fr>
mrueg
force-pushed
the
prep-release-2.7
branch
from
4ffaf18
to
8a76eb0
Compare
k8s-ci-robot
removed
the
lgtm
Add ingress class metrics
Signed-off-by: Manuel Rüger <manuel@rueg.eu>
mrueg
force-pushed
the
prep-release-2.7
branch
from
8a76eb0
to
095bf79
Compare
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgrisonnet, mrueg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
|
Thank you for driving this all the way, Manuel! 🎉 |
Vantone
pushed a commit
to Vantone/kube-state-metrics
that referenced
this pull request
Mar 1, 2024
*: Cut v2.7.0
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.
What this PR does / why we need it:
Next release to be cut this Thursday / promoted Friday. Please let me know if I missed anything important.
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
None
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):See ChangeLog.md