Red Hat Bugzilla – Bug 1254880
Secure communication for Heapster metric collection
Last modified: 2016-09-29 22:16:47 EDT
- Proposed title of this feature request Secure Access to OpenShift cluster for collecting metrics. - What is the nature and description of the request? At the moment Heapster is using readonly port to collect metrics from OpenShift cluster however, traffic is not encrypted. - Why does the customer need this? Due to corporate security policies requirements all traffic needs to be encrypted. - How would the customer like to achieve this? Traffic from nodes to Heapster needs to go through secured channel. (i.e ssl) - For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. - Is there already an existing RFE upstream or in Red Hat Bugzilla? No - Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? OSE 3.1 - Is the sales team involved in this request and do they have any additional input? Yes - Would the customer be able to assist in testing this functionality if implemented? Yes
Upstream discussion related to this subject https://github.com/openshift/origin/issues/3020
In progress via https://trello.com/c/kej8gRJg
Card was accepted in Oct.
It's fixed, checked with latest metrics stack images as below: openshift3/metrics-deployer image 277d6f10f28e openshift3/metrics-hawkular-metrics image b44dc66d64f2 openshift3/metrics-cassandra image 8ea21f4b3377 openshift3/metrics-heapster image 800434e62203 Test results: The metrics endpoints are using secure http method, like below: https://hawkular-metrics.0107-1kp.qe.rhcloud.com/hawkular/metrics/counters/hawkular-metrics%2F270d1075-b509-11e5-b264-fa163ea9e676%2Fcpu%2Fusage/data?buckets=61&start=1452148364643
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-2016:0070