-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Metrics: Fix namespace in nginx_ingress_controller_ssl_expire_time_seconds
.
#10274
Metrics: Fix namespace in nginx_ingress_controller_ssl_expire_time_seconds
.
#10274
Conversation
|
✅ Deploy Preview for kubernetes-ingress-nginx canceled.
|
Welcome @alexey-gavrilov-flant! |
Hi @alexey-gavrilov-flant. Thanks for your PR. I'm waiting for a kubernetes 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/test-infra repository. |
4153bee
to
1a7544e
Compare
@strongjz Could you please see my changes and advance ci to the next step? |
@rikatz Could you please see my changes and advance ci to the next step? |
1a7544e
to
a7cbd31
Compare
/check-required-labels |
/auto-cc |
a7cbd31
to
ee332b1
Compare
/auto-cc |
Hi, Very few readers can completely understand the current state and the change proposed in this PR. If you think its worth it, then you can post screenshots of current view and the screenshots of view after changed code. It will help make the PR clear to readers. |
070b4d9
to
7dc34fa
Compare
Thank you for reviewing @sathieu! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexey-gavrilov-flant, Gacko 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 |
nginx_ingress_controller_ssl_expire_time_seconds
.nginx_ingress_controller_ssl_expire_time_seconds
.
With this understanding (the namespace was already defined for the metric but never set) we can safely cherry-pick this change to |
/cherry-pick release-1.10 |
/cherry-pick release-1.11 |
@Gacko: once the present PR merges, I will cherry-pick it on top of release-1.10 in a new PR and assign it to you. 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. |
@Gacko: once the present PR merges, I will cherry-pick it on top of release-1.11 in a new PR and assign it to you. 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. |
/kind bug |
/unhold |
@Gacko: new pull request created: #11985 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. |
@Gacko: new pull request created: #11986 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. |
What this PR does / why we need it:
now the metric in the namespace label gives the value of where the controller is located but not the ingress itself, which is misleading for an engineer who studies the NGINXCertificateExpiry alert created on the basis of the nginx_ingress_controller_ssl_expire_time_seconds metric.
Types of changes
Which issue/s this PR fixes
The hotfix will improve the NGINXCertificateExpiry alert. After the fix, it will contain information about the space where the ingress was created and the name of the secret, instead of where the ingress controller is, which is more convenient for understanding where to look for a faulty secret with a certificate.
How Has This Been Tested?
build and manually check the values of labels that are passed to Prometheus.
Checklist: