Description of problem: etcd pods are deployed under openshift-etcd project now, not in kube-system ******************************************** # oc -n openshift-etcd get pod NAME READY STATUS RESTARTS AGE etcd-member-ip-10-0-135-140.us-east-2.compute.internal 2/2 Running 0 8h etcd-member-ip-10-0-151-177.us-east-2.compute.internal 2/2 Running 0 8h etcd-member-ip-10-0-169-0.us-east-2.compute.internal 2/2 Running 0 8h ******************************************** # oc -n kube-system get pod No resources found. ******************************************** but "kube_pod_status_ready:etcd:sum" rule still use "kube-system" project ******************************************** record: kube_pod_status_ready:etcd:sum expr: sum by(condition) (kube_pod_status_ready{condition="true",namespace="kube-system",pod=~"etcd.*"}) ******************************************** Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-05-23-213243 How reproducible: Always Steps to Reproduce: 1. Check "kube_pod_status_ready:etcd:sum" rule 2. 3. Actual results: namespace is stil "kube-system" for "kube_pod_status_ready:etcd:sum" rule Expected results: namespace should be openshift-etcd for "kube_pod_status_ready:etcd:sum" rule Additional info:
change back to MODIFIED, no 4.1.z OCP build to verify now
namespace is openshift-etcd for "kube_pod_status_ready:etcd:sum" rule payload: 4.1.0-0.nightly-2019-06-04-235906
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/RHBA-2019:1382