MAS DevOps Ansible Collection Ansible CLI
Home Ansible Automation Platform OCP Install Cloud Pak For Data Install Core Add AIBroker Add IoT Add Manage Add Monitor Add Optimizer Add Predict Add Visual Inspection Update Upgrade Uninstall Core Backup & Restore ocp_cluster_monitoring ocp_config ocp_deprovision ocp_efs ocp_github_oauth ocp_login ocp_node_config ocp_provision ocp_roks_upgrade_registry_storage ocp_upgrade ocp_verify appconnect aws_bucket_access_point aws_documentdb_user aws_policy aws_route53 aws_user_creation aws_vpc cert_manager cis common-services configure_manage_eventstreams cos cos_bucket cp4d_admin_pwd_update cp4d cp4d_service db2 dro eck grafana ibm_catalogs kafka nvidia_gpu mongodb ocs sls turbonomic uds mirror_case_prepare mirror_extras_prepare mirror_images mirror_ocp ocp_idms ocp_simulate_disconnected_network registry suite_app_config suite_app_install suite_app_uninstall suite_app_upgrade suite_app_rollback suite_app_backup_restore suite_certs suite_config suite_db2_setup_for_manage suite_dns suite_install suite_manage_attachments_config suite_manage_birt_report_config suite_manage_bim_config suite_manage_customer_files_config suite_manage_imagestitching_config suite_manage_import_certs_config suite_manage_load_dbc_scripts suite_manage_logging_config suite_manage_pvc_config suite_uninstall suite_upgrade suite_rollback suite_verify suite_backup_restore ansible_version_check entitlement_key_rotation gencfg_jdbc gencfg_watsonstudio gencfg_workspace gencfg_mongo

eck¤

This role provides support to install Elastic Cloud on Kubernetes (ECK).

Elasticsearch is configured with a default user named elastic, you can obtain the password for this user by running the following command:

oc -n eck get secret mas-es-elastic-user -o go-template='{{.data.elastic | base64decode}}'; echo

Role Variables¤

eck_action¤

Action to be performed by the role. The only valid value currently is install.

eck_enable_elasticsearch¤

Whether to include Elasticsearch when performing the desired action.

eck_enable_kibana¤

Whether to include Kibana when performing the desired action.

eck_enable_logstash¤

Whether to include Logstash when performing the desired action.

eck_enable_filebeat¤

Whether to include Filebeat when performing the desired action.

Role Variables - Remote Elasticsearch¤

When eck_remote_es_hosts, eck_remote_es_username, and eck_remote_es_password are all set, and eck_enable_logstash is true, the Logstash server will be configured to send log messages to the remote Elasticsearch instance defined.

eck_remote_es_hosts¤

A list of one or more hosts for the remote Elasticsearch instance. When using an environment varible, the value should be in the format of a comma-seperated list.

eck_remote_es_username¤

The username that will be used to authenticate with the remote Elasticsearch instance.

eck_remote_es_password¤

The password that will be used to authenticate with the remote Elasticsearch instance.

Role Variables - Domains and Certificates¤

Elasticsearch and Kibana can be configured with a custom domain and a certificate signed by LetsEncrypt.

es_domain¤

The domain that Elasticsearch will be accessed from, must be routable to the target OCP cluster.

kibana_domain¤

The domain that Kibana will be accessed from, must be routable to the target OCP cluster.

letsencrypt_email¤

Provide the email address which will be used to register the certificates with LetsEncrypt. When this is provided and one or both domains are set, an Issuer will be configured for LetsEncrypt production using a HTTP solver that will installed automatically by Cert-Manager in the ECK namespace.

Example Playbook¤

- hosts: localhost
  any_errors_fatal: true
  vars:
    eck_action: install
    eck_enable_elasticsearch: true
    eck_enable_kibana: true
    eck_enable_logstash: true
  roles:
    - ibm.mas_devops.eck

License¤

EPL-2.0