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.

Sign up for GitHub

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

Jump to bottom

Replication controller logs errors for full quotas #22364

Closed
chbatey opened this issue Mar 2, 2016 · 3 comments
Closed

Replication controller logs errors for full quotas #22364

chbatey opened this issue Mar 2, 2016 · 3 comments
Labels
area/controller-manager priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@chbatey
Copy link
Contributor

chbatey commented Mar 2, 2016

The daemons log a lot of Errors for what seems like normal operational events. We're currently building out our monitoring for our clusters and we'd rather treat Errors as something that needs a platform member to look at asap. Here's an example:

E0302 15:23:58.002320 1586 replication_controller.go:357] unable to create pods: Pod "voucher-manager-service-iron-" is forbidden: unable to admit pod without exceeding quota for resource cpu:

This for us is business as usual as each team can use their allocated resources as they place. I'd rather this kind of message be logged at Info level 0.

Happy to start raising PRs for these if they'll get accepted.
@bprashanth
Copy link
Contributor

I suspect it's just logging the error returned by the apiserver on failed create. It doesn't know to differentiate this from other legitimate errors. I suspect it's getting back a 403, which could mean user doesn't have access, admission controller failed etc. IMO these actually make more sense as events.

@bgrant0607
Copy link
Member

See also #21912

@bgrant0607 bgrant0607 added area/controller-manager priority/backlog Higher priority than priority/awaiting-more-evidence. labels Mar 3, 2016
@bgrant0607
Copy link
Member

Events are preferred. Closing in favor of #21912.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/controller-manager priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chbatey @bgrant0607 @bprashanth