Skip to content
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

Introduce the metric controller. #4913

Merged

Conversation

markusthoemmes
Copy link
Contributor

Ref #4403

Proposed Changes

The metric controller reacts on the lifecycle of metric objects and currently makes sure that metric collecting is started when a metric is created and stopped if one is deleted. As updating is not really a distinct use-case we want to handle differently, this also introduces a 'CreateOrUpdate' function to the collector, which appropriately acts if the collection was already running or not.

This is a stepping stone towards removing the in-memory handling of metric entities. The controller is not yet hooked up though.

Release Note

NONE

/assign @vagababov

The metric controller reacts on the lifecycle of metric objects and currently makes sure that metric collecting is started when a metric is created and stopped if one is deleted. As updating is not really a distinct use-case we want to handle differently, this also introduces a 'CreateOrUpdate' function to the collector, which appropriately acts if the collection was already running or not.

This is a stepping stone towards removing the in-memory handling of metric entities. The controller is not yet hooked up though.
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jul 24, 2019
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 24, 2019
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@markusthoemmes: 0 warnings.

In response to this:

Ref #4403

Proposed Changes

The metric controller reacts on the lifecycle of metric objects and currently makes sure that metric collecting is started when a metric is created and stopped if one is deleted. As updating is not really a distinct use-case we want to handle differently, this also introduces a 'CreateOrUpdate' function to the collector, which appropriately acts if the collection was already running or not.

This is a stepping stone towards removing the in-memory handling of metric entities. The controller is not yet hooked up though.

Release Note

NONE

/assign @vagababov

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.

@knative-prow-robot knative-prow-robot added area/API API objects and controllers area/autoscale labels Jul 24, 2019
pkg/autoscaler/collector.go Show resolved Hide resolved
pkg/autoscaler/collector.go Show resolved Hide resolved
pkg/autoscaler/collector.go Show resolved Hide resolved
Copy link
Contributor

@vagababov vagababov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 25, 2019
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: markusthoemmes, vagababov

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot merged commit 293a571 into knative:master Jul 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/API API objects and controllers area/autoscale cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants