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

flow-control-api spec #1028

Merged

Conversation

pmoogi-redhat
Copy link
Contributor

As a cluster admin I want to be able to set a flow control policy or logging rate limiting policy : drop as if logging rate exceeds rate limits provided (bytes/sec) on selected containers, ignore by dropping entire logs from selected group of containers.

*A cluster-wide default for all containers (optional)
*A special rate for containers in named namespaces
*A special rate for containers matching a label selector
*Rates are per-container and measured in bytes/sec, the default value -1 means no limits are applied (default behaviour), 0 - means ignore entirely that set of selected containers logs belonging to a defined group

Rates are enforced by dropping log data if it exceeds the rate. Cluster Logging Forwarder Spec applies RateLimiting policies to its input sources of logs and also its output endpoints connecting to a given persistent storage.

JIRA Reference [Epic] - https://issues.redhat.com/browse/LOG-884
JIRA Reference [Story] - https://issues.redhat.com/browse/LOG-2207

@pmoogi-redhat
Copy link
Contributor Author

@alanconway please review

Copy link
Contributor

@alanconway alanconway left a comment

Choose a reason for hiding this comment

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

Made some suggested changes, you can apply them automatically via github. Important points:

  • changed input.limit to input.perContainerLimit
  • changed limit.maxBytesPerSecond to input.MaxRecordsPerSecond

enhancements/cluster-logging/flow-control-api.md Outdated Show resolved Hide resolved
enhancements/cluster-logging/flow-control-api.md Outdated Show resolved Hide resolved
enhancements/cluster-logging/flow-control-api.md Outdated Show resolved Hide resolved
enhancements/cluster-logging/flow-control-api.md Outdated Show resolved Hide resolved
enhancements/cluster-logging/flow-control-api.md Outdated Show resolved Hide resolved
enhancements/cluster-logging/flow-control-api.md Outdated Show resolved Hide resolved
@alanconway
Copy link
Contributor

@pmoogiThis should be linked to https://issues.redhat.com/browse/LOG-1043 - that task is specifically for designing the API.
https://issues.redhat.com/browse/LOG-2207 is about implementing it.

pmoogi-redhat and others added 6 commits February 11, 2022 10:25
Co-authored-by: Alan Conway <aconway@redhat.com>
Co-authored-by: Alan Conway <aconway@redhat.com>
Co-authored-by: Alan Conway <aconway@redhat.com>
Co-authored-by: Alan Conway <aconway@redhat.com>
Co-authored-by: Alan Conway <aconway@redhat.com>
Co-authored-by: Alan Conway <aconway@redhat.com>
@alanconway
Copy link
Contributor

I have some updates from recent discussion to be included as soon as I get a chance to write them up.
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 9, 2022
@alanconway
Copy link
Contributor

/unhold
/lgtm

@alanconway
Copy link
Contributor

I will update in a separate PR.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 24, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2022
@alanconway
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alanconway

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 24, 2022
@alanconway
Copy link
Contributor

/approved

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2022

@pmoogi-redhat: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 719525c into openshift:master Mar 24, 2022
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants