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

disable events? #124836

Closed
tooptoop4 opened this issue May 13, 2024 · 7 comments
Closed

disable events? #124836

tooptoop4 opened this issue May 13, 2024 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/support Categorizes issue or PR as a support question. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/cli Categorizes an issue or PR as relevant to SIG CLI.

Comments

@tooptoop4
Copy link

What would you like to be added?

looking at kubectl events I see things like "message": "Started container bla" with "userAgent": "kubelet" and "involvedObject" "kind": "Pod"

is there any config option to prevent these events being sent?

Why is this needed?

etcd can fill up

@tooptoop4 tooptoop4 added the kind/feature Categorizes issue or PR as related to a new feature. label May 13, 2024
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 13, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@pacoxu
Copy link
Member

pacoxu commented May 13, 2024

kube-apiserver default event ttl is 1h. So etcd will not be filled up by events unless the recent 1 hour events is with a too large amount.

`--event-ttl` duration     Default: 1h0m0s
 Amount of time to retain events.

Another solution is to use separated etcd for events. https://openai.com/index/scaling-kubernetes-to-2500-nodes/ openai blog also include the etcd-servers-overrides flag usage. With this solution, events are saved separately.

--etcd-servers-overrides strings

  | Per-resource etcd servers overrides, comma separated. The individual override format: group/resource#servers, where servers are URLs, semicolon separated. Note that this applies only to resources compiled into this server binary.

@tooptoop4
Copy link
Author

@pacoxu can i put ttl as 0? really not interested in the events

@pacoxu
Copy link
Member

pacoxu commented May 13, 2024

You may set it to a quite small duration IIUC.

Zero means no TTL, not expire immediately.

// calculateTTL is a helper for retrieving the updated TTL for an object or
// returning an error if the TTL cannot be calculated. The defaultTTL is
// changed to 1 if less than zero. Zero means no TTL, not expire immediately.
func (e *Store) calculateTTL(obj runtime.Object, defaultTTL int64, update bool) (ttl uint64, err error) {

@neolit123
Copy link
Member

/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 16, 2024
@neolit123
Copy link
Member

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label May 16, 2024
@k8s-ci-robot
Copy link
Contributor

@neolit123: Closing this issue.

In response to this:

/kind support
/close

https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/support Categorizes issue or PR as a support question. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
Projects
Status: Closed
Development

No branches or pull requests

4 participants