Skip to content

Latest commit

 

History

History
42 lines (24 loc) · 2.31 KB

install_with_helm.md

File metadata and controls

42 lines (24 loc) · 2.31 KB

Install to Kubernetes

The following guide details how to install the Ansible Lifecycle Driver into a Kubernetes environment with helm.

Prerequisites

To complete the install you will need a Kubernetes cluster.

You will also need a controller machine (can be one of the Kubernetes cluster nodes) to perform the installation from. This machine must have the Helm CLI tool installed and initialised with access to your cluster. Please note that Helm v3 is required.

Installation

Download

Download the Helm chart from the releases page to your machine.

wget https://github.com/IBM/ansible-lifecycle-driver/releases/download/<version>/ansiblelifecycledriver-<version>.tgz

Install

Install the chart using the helm CLI:

helm install ansible-lifecycle-driver ansiblelifecycledriver-<version>.tgz [--set app.config.override.lifecycle.request_queue.topic.num_partitions=100,app.config.override.lifecycle.request_queue.topic.replication_factor=1]

kafka host value must be set as follows, in values.yaml file of the helm package, depending on the CP4NA versions:

  • For pre CP4NA v2.3, the kafka host must be iaf-system-kafka-bootstrap

  • For CP4NA v2.3/v2.3+, the kafka host must be cp4na-o-events-kafka-bootstrap

By default, the driver will attempt to connect to Kafka with the address cp4na-o-events-kafka-bootstrap:9092.

The Ansible Lifecycle Driver uses an Ignition Request Queue to process transitions. Note the overrides for the Kafka request queue topic number of partitions and replication factory. The number of partitions determines an upper limit on how many transitions can be run in parallel, the replication factor improves fault tolerance and should be set to less than or equal to the number of Kafka brokers in your cluster.

The driver runs with SSL enabled by default. The installation will generate a self-signed certificate and key by default, adding them to the Kubernetes secret "ald-tls". To use a custom certificate and key in your own secret, override the properties under "apps.config.security.ssl.secret".

Confirm

You can confirm the driver is working by accessing: http://<kubernetes-node-ip>:31680/management/health