-
Notifications
You must be signed in to change notification settings - Fork 303
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
Add missing features to ingress metrics #1233
Conversation
Hi @spencerhance. 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. |
/assign @freehan |
/assign @prameshj Pavithra, any chance you have bandwidth to review this? |
/ok-to-test |
Would it be better to split into 2 PRs - one with metrics that can be cherrypicked to 1.9 and one with those that cannot? |
StaticIPNameKey: "user-spec-static-ip", | ||
staticIPKey: "user-spec-static-ip", | ||
StaticGlobalIPNameKey: "user-spec-static-ip", | ||
staticIPKey: "user-spec-static-ip", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: should this value be an ip address?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both of the annotations represent the name of the address, rather than the address itself
57a10f6
to
ddf0e15
Compare
@prameshj Good call! I removed redirects from this. Once it is merged I'll submit a follow up PR. |
@@ -191,15 +201,24 @@ func featuresForIngress(ing *v1beta1.Ingress) []feature { | |||
if val, ok := ingAnnotations[staticIPKey]; ok && val != "" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean user has to specify both staticIPKey and StaticGlobalIPNameKey in order to use a given ip address name? Why do we need 2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, no staticIPKey is used as a status annotation
ddf0e15
to
53a667b
Compare
pkg/metrics/features.go
Outdated
|
||
// Check for regional static IP | ||
// We do this separately from the global static IP because regional static IP | ||
// does not support the StaticIPKey annotation or a managed regional IP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you rephrase this to say - "Controller does not populate StaticIPKey annotation when processing Regional static IP"?
Also, these annotations are also defined in annotations/ingress.go. Do they need to be redefined in features.go?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@skmatti what was the reason for this? Was there a circular dependency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was to enable backporting for the metrics PR to the release branches that do not have the annotations defined. Maybe it does not apply for these metrics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I removed the annotation
fd32fc2
to
4989b38
Compare
pkg/metrics/features.go
Outdated
|
||
// Check for regional static IP | ||
// We do this separately from the global static IP because Controller does not | ||
// populate StaticIPKey annotation when processing Regional static IP regional static IP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
These features have been implemented but are currently not included in the metrics - SSLPolicy - Regional Static IP - Custom Health Checks
4989b38
to
355178a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: freehan, spencerhance 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 |
Cherry-pick #1233 [Add missing features to ingress metrics] into release-1-9
Cherry-pick #1233 [Add missing features to ingress metrics] into release-1-10
These features have been implemented but are currently not included in the metrics
This PR adds metrics for them
All of them can be cherry-picked to v1.9 + v1.10
HTTPS Redirects will be added in a follow up since it is currently 1.10 only