Balazs Szeti

Yes, and I've talked to Raffaele about this. The "capacity" dashboards requires a special "nodegroup" label on nodes and shows the resource utilization when we have different group of compute...

@etsauer ok, at the moment the "capacity dashboards" are duplicated in the repo. They are under "capacity-dashboard" directory and also in the yaml files under "custom-dasboards/.openshift/dashboards/capacity". The purpose of "custom-dashboards"...

@etsauer I'm taking a look at this now. I see two use cases: - manually import the dashboards via Grafana UI. This requires a json files. For example /capacity-dashboard/capacity-planning.json -...

I'm trying to use jinja like this: _{% include "namespaces-in-cluster.json" %}_ or _{% include inventory_dir + '/../.openshift/dashboards/capacity-by-nodetype/namespaces-in-cluster.json' %}_ or even with absolute path _{% include "/Users/bszeti/git/openshift-toolkit/custom-dashboards/.openshift/dashboards/capacity-by-nodetype/namespaces-in-cluster.json" %}_ but I'm keep...

It seems that the {% include [file] %} only works if the file is under the role. In this case "galaxy/openshift-applier/roles/openshift-applier", which is obviously not god for us. (Also "../../../../namespaces-in-cluster.json"...

@etsauer Any suggestions?

Using global pull secrets is an easy solution of course, but that's not always doable. One workaround is to expect a pull secret in the namespace with a hardcoded name...

Hi @anik120 Thanks for the response. I understand the reasoning behind not copying secrets between namespaces, that doesn't sound good from the security point of view. I also read the...

Thanks a lot for the feedback. Yes, we've seen such issues, but didn't want to make the queries more complicated - and in our case the number of Completed Pods...