Bug 1509341 - Stop prometheus metrics growth issues
Summary: Stop prometheus metrics growth issues
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.7.0
Assignee: Dan Mace
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-03 15:08 UTC by Eric Paris
Modified: 2017-11-28 22:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-28 22:21:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

Description Eric Paris 2017-11-03 15:08:29 UTC
Clayton says this will stop premetheus metric growth.

https://github.com/kubernetes/kubernetes/pull/54921

I believe he wants/needs this for 3.7 GA

Comment 2 Derek Carr 2017-11-03 17:53:03 UTC
https://github.com/openshift/origin/pull/17173

Comment 4 Junqi Zhao 2017-11-08 09:18:33 UTC
Tested,  Prometheus AlertManager volumes does not grow infinitely now

env:
# openshift version
openshift v3.7.0-0.197.0
kubernetes v1.7.6+a08f5eeb62
etcd 3.2.8

images:
prometheus/images/v3.7.0-0.197.0.0
prometheus-alert-buffer/images/v3.7.0-0.197.0.0
oauth-proxy/images/v3.7.0-0.197.0.0
prometheus-alertmanager/images/v3.7.0-0.197.0.0

Comment 7 errata-xmlrpc 2017-11-28 22:21:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:3188


Note You need to log in before you can comment on or make changes to this bug.