Cluster-monitoring-operator repository is missing 2 generated asset files: - assets/thanos-querier/kube-rbac-proxy-secret.yaml - assets/thanos-ruler/kube-rbac-proxy-secret.yaml Those files are referenced in pkg/manifests/manifests.go but not created in assets/ directory. Those files need to exist or their references need to be removed from pkg/manifests/manifests.go.
The file assets/thanos-querier/kube-rbac-proxy-secret.yaml is still available and being used AFAICT. The file assets/thanos-ruler/kube-rbac-proxy-secret.yaml was removed as part of a previous cleanup (https://github.com/openshift/cluster-monitoring-operator/pull/700). Created PR #744 (https://github.com/openshift/cluster-monitoring-operator/pull/744)
Test with payload 4.5.0-0.nightly-2020-04-06-212952: Checked git repository: - assets/thanos-querier/kube-rbac-proxy-secret.yaml exists - assets/thanos-ruler/kube-rbac-proxy-secret.yaml deleted execute the following command and get the corresponding data: oc get Secret thanos-querier-kube-rbac-proxy -oyaml
Check git repository: https://github.com/openshift/cluster-monitoring-operator
enabled techPreviewUserWorkload, see # oc -n openshift-monitoring get cm cluster-monitoring-config -oyaml 4:34 then there are resources under openshift-user-workload-monitoring 4:34 # oc -n openshift-user-workload-monitoring get secret | grep thanos-ruler no kube-rbac-proxy secret # oc -n openshift-monitoring get secret | grep thanos-querier thanos-querier-dockercfg-r8szt kubernetes.io/dockercfg 1 7h53m thanos-querier-grpc-tls-f9g2c7s4l0rd9 Opaque 3 7h53m thanos-querier-kube-rbac-proxy Opaque 1 7h53m thanos-querier-oauth-cookie Opaque 1 7h54m thanos-querier-oauth-htpasswd Opaque 1 7h53m thanos-querier-tls kubernetes.io/tls 2 8h thanos-querier-token-fvtzr kubernetes.io/service-account-token 4 7h53m thanos-querier-token-vqjfj kubernetes.io/service-account-token 4 7h53m There is secret thanos-querier-kube-rbac-proxy
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-2020:2409