script to add dashboards and other Kibana UI objects #518
Conversation
|
| info Adding Kibana dashboards and other UI objects for user $1 index $kibindex | ||
|
|
||
| INDEX_PATTERN=${INDEX_PATTERN:-project.*} | ||
| INDEX_PATTERN_FILE=${INDEX_PATTERN_FILE:-/usr/share/elasticsearch/index_patterns/com.redhat.viaq-openshift.index-pattern.json} |
There was a problem hiding this comment.
We should consider refactoring '/usr/share/elasticsearch/' into a var like ES_HOME. If I ever get the reconciliation PR complete I think this will simply the impact and additional modifications we need to make.
There was a problem hiding this comment.
ok - but there are likely other places which will need to change
test/kibana_dashboards.sh
Outdated
| else | ||
| os::cmd::info Creating cluster-admin user $LOG_ADMIN_USER | ||
| current_project="$( oc project -q )" | ||
| os::cmd::debug "$( oc login --username=$LOG_ADMIN_USER --password=$LOG_ADMIN_PW )" |
There was a problem hiding this comment.
I don't believe this is necessary since when adding roles to a user, a user doesn't need to exist. I'm pretty certain the association is by name and userpolicy is applied to users with that name. There is no 'user' store per se.
|
[test] |
@jcantrill It doesn't appear to require the acls, just the |
https://bugzilla.redhat.com/show_bug.cgi?id=1467963 The script es_load_kibana_ui_objects is used to load dashboards and other Kibana UI objects for the given user. Usage: oc exec $espod -- es_load_kibana_ui_objects user-name That is, it exists inside the Elasticsearch and ES-OPS pod, and must be run inside those pods. Additionally, it requires some indices and other objects set up by the OpenShift Elasticsearch plugin, so the user must login to Kibana (or Elasticsearch) before using this script. This will also add an index pattern for `project.*` and load the necessary index pattern file. This relies on some additions to the viaq schema which is provided by ViaQ/elasticsearch-templates#50
|
Evaluated for origin aggregated logging test up to b0044ec |
|
Origin Aggregated Logging Test Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_aggregated_logging/179/) (Base Commit: b613f65) (PR Branch Commit: b0044ec) |
|
[merge][severity: blocker] |
|
flake [merge][severity:blocker] |
|
Evaluated for origin aggregated logging merge up to b0044ec |
|
Origin Aggregated Logging Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin_aggregated_logging/68/) (Base Commit: b613f65) (PR Branch Commit: b0044ec) (Extended Tests: blocker) |
The script es_load_kibana_ui_objects is used to load dashboards and
other Kibana UI objects for the given user. Usage:
oc exec $espod -- es_load_kibana_ui_objects user-name
That is, it exists inside the Elasticsearch and ES-OPS pod, and must
be run inside those pods. Additionally, it requires some indices and
other objects set up by the OpenShift Elasticsearch plugin, so the user
must login to Kibana (or Elasticsearch) before using this script.
This will also add an index pattern for
project.*and load thenecessary index pattern file.
This relies on some additions to the viaq schema which is provided
by ViaQ/elasticsearch-templates#50
@jcantrill @portante PTAL
[test]