Track dry-run and apply in metrics#74997
Conversation
There was a problem hiding this comment.
Since this is supposed to be a list of strings, and we currently only support one string, maybe you should keep it as the input string?
4bfece2 to
85aabaa
Compare
jpbetz
left a comment
There was a problem hiding this comment.
Generally looks good. Just one observation/question.
648d3e7 to
8fe34eb
Compare
|
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
|
I'm not exactly sure why this is considered an API changing PR, I think because I made changes to |
|
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/apis/OWNERS#L11 adds the kind/api-change label, which is what the bot watches for |
There was a problem hiding this comment.
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/instrumentation.md for guidelines, prefer dry_run
There was a problem hiding this comment.
I'll update this, thanks. I only put "dryRun" to conform with the existing "contentType" label
There was a problem hiding this comment.
I agree that consistency should matter more here.
There was a problem hiding this comment.
It looks terrible to have both, but you should probably do what sig instrumentation wants; leave a comment, though.
|
two nits, lgtm otherwise |
d39b0da to
8cc1ff6
Compare
|
/retest |
| if errs := validation.ValidateDryRun(nil, dryRun); len(errs) > 0 { | ||
| return "invalid" | ||
| } | ||
|
|
There was a problem hiding this comment.
strings.Join(sets.NewString(dryRun...).List(),",") will dedupe and sort for you if you want to collapse onto that
|
one comment about the synthetic verb, and one optional comment about using
|
bffc92e to
077dd28
Compare
|
/retest |
a3edbb0 to
6e512eb
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jennybuckley, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/milestone 1.14 |
|
@jennybuckley: You must be a member of the kubernetes/kubernetes-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. DetailsIn 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/test-infra repository. |
|
/milestone 1.14 |
|
@lavalamp: The provided milestone is not valid for this repository. Milestones in this repository: [ Use DetailsIn 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/test-infra repository. |
|
/milestone v1.14 |
|
/retest |
What type of PR is this?
/kind feature
/sig api-machinery
/wg apply
/priority important-soon
What this PR does / why we need it:
Example value of the metric from kube-up
Which issue(s) this PR fixes:
Tracked in #73723
Does this PR introduce a user-facing change?: