Follow the steps below to provision the minikube cluster and install Tackle 2.0.
Follow the steps below to provision minikube for single users deploying Tackle on a workstation. These steps will configure minikube and enable:
Procedure
<profile name>
with your choice of minikube profile name.[user@user ~]$ minikube start --memory=10g -p <profile name>
[user@user ~]$ minikube addons enable ingress -p <profile name>
[user@user ~]$ curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.21.2/install.sh | bash -s v0.21.2
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.
Name | Default Size | Access Mode | Description |
---|---|---|---|
hub database | 5Gi | RWO | Hub DB |
hub bucket | 100Gi | RWX | Hub file storage |
keycloak postgresql | 1Gi | RWO | Keycloak backend DB |
pathfinder postgresql | 1Gi | RWO | Pathfinder backend DB |
maven | 100Gi | RWX | maven m2 repository |
Follow the steps below to install the Tackle Operator in the my-tackle-operator namespace (default) on any Kubernetes distribution, including minikube.
Procedure
[user@user ~]$ kubectl create -f https://operatorhub.io/install/tackle-operator.yaml
[user@user ~]$ kubectl get pods -n my-tackle-operator
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
[user@user ~]$ cat << EOF | kubectl apply -f -
kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
name: tackle
namespace: my-tackle-operator
spec:
EOF
[user@user ~]$ kubectl get pods -n my-tackle-operator
Note: This can take one to five minutes depending on the cluster resources.
Follow the steps below to log in to the Tackle web console.
Procedure
[user@user ~]$ minikube dashboard -p <profile name>
my-tackle-operator
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 tohttps://$IP_ADDR
admin
/Passw0rd!