Bug 1435781

Summary:	Router Metrics needs to use image shipped by Red Hat
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Networking	Assignee:	Clayton Coleman <ccoleman>
Networking sub component:	router	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	aos-bugs, pdwyer
Version:	3.3.0
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Deprecated Functionality
Doc Text:	The router metrics image field on "oadm router" has been deprecated and will be removed in a future release. A Prometheus compatible metrics endpoint has been added to the HAProxy router in tech preview and will be supported in future releases.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 21:53:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eric Jones 2017-03-24 18:14:47 UTC

Description of problem:
The current haproxy metrics requires usage of another image to be sideloaded into the pod. This is not ideal but fine except that the image being used is not shipped by Red Hat [0]. It is an image from docker.io

[0] https://docs.openshift.com/container-platform/3.3/install_config/router/default_haproxy_router.html#exposing-the-router-metrics

If we support it, we need to ship it ourselves.

Comment 1 Clayton Coleman 2017-04-12 13:15:08 UTC

In 3.6 we have a supported metrics endpoint as part of haproxy.  No externaml image required.

Comment 2 zhaozhanqi 2017-04-13 01:36:32 UTC

I checked this feature in 3.6. this metric info can be got on the router node by:

# curl 127.0.0.1:1935/metrics -u admin:FAh7ibk0Pw

Comment 3 Clayton Coleman 2017-04-19 14:38:49 UTC

We've decided to deprecate the router metrics image as well.  We should remove references from the docs.

Comment 8 errata-xmlrpc 2017-11-28 21:53:01 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