Installing Tackle

Follow the steps below to provision the minikube cluster and install Tackle 2.0.

Provisioning Minikube

Follow the steps below to provision minikube for single users deploying Tackle on a workstation. These steps will configure minikube and enable:

• Ingress so the Tackle tool can publish outside of the Kubernetes cluster.
• Operator lifecycle manager (OLM) addon. (OpenShift has OLM installed out of the box but Kubernetes does not.)

Procedure

1. Provision the minikube cluster with these recommended parameters. Replace <profile name> with your choice of minikube profile name.

[user@user ~]$ minikube start --memory=10g -p <profile name>

2. Enable the ingress addon.

[user@user ~]$ minikube addons enable ingress -p <profile name>

3. Install Operator Lifecycle Manager (OLM), a tool to help manage the Operators running on your cluster.

[user@user ~]$ curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.21.2/install.sh | bash -s v0.21.2

Installing Tackle Operator

Operators are a structural layer that manages resources deployed on Kubernetes (database, front end, back end) to automatically create a Tackle instance instead of doing it manually.

Requirements Tackle requires a total of 5 persistent volumes (PVs) used by different components to successfully deploy, 3 RWO volumes and 2 RWX volumes will be requested via PVCs.

Follow the steps below to install the Tackle Operator in the my-tackle-operator namespace (default) on any Kubernetes distribution, including minikube.

Procedure

1. Install the Tackle Operator.

[user@user ~]$ kubectl create -f https://operatorhub.io/install/tackle-operator.yaml

2. Verify Tackle was installed.

[user@user ~]$ kubectl get pods -n my-tackle-operator

3. Repeat this step until konveyor-tackle-XXX and tackle-operator-XXX show 1/1 Running.

Create the Tackle instance

Follow the steps below to initiate the Tackle instance and set a custom resource (CR) with the tackle_hub.yaml file. CRs can be customized to meet the project needs.

Procedure

1. Create the instance pointing to the CR file.

[user@user ~]$ cat << EOF | kubectl apply -f -
kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
  name: tackle
  namespace: my-tackle-operator
spec:
EOF

2. Verify the instance

[user@user ~]$ kubectl get pods -n my-tackle-operator

3. Repeat this step until all components are Completed or Running.

Note: This can take one to five minutes depending on the cluster resources.

Logging in to Tackle Web Console

Follow the steps below to log into the Tackle web console.

Procedure

1. Access the minikube dashboard. This will enable the dashboard add-on, and open the proxy in the default web browser.

[user@user ~]$ minikube dashboard -p <profile name>

2. Ensure the top dropdown namespace selector is set to the my-tackle-operator
3. Click Service then Ingresses
4. Click the endpoint IP for the tackle ingress ingress to launch the Tackle web console in a new browser window.

Note: This may default to http://$IP_ADDR and fail to load, if so switch to https://$IP_ADDR

6. The default auth enabled credentials are: admin/Passw0rd!

Source