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:
[user@user ~]$ Minikube start -- driver=kvm3 -p <project name> --memory=10g
[user@user ~]$ Minikube addons enable ingress -p docs
[user@user ~]$ Minikube addons enable olm -p docs
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.
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.
[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.
$ cat << EOF | kubectl apply -f -
kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
name: tackle
namespace: <your-tackle-namespace>
spec:
EOF
Note: For more information about altering the operator defaults, see the Tackle CR Settings section.
[user@user ~]$ Kubectl create -f tackle_hub.yaml -n my-tackle-operator
[user@user ~]$ kubectl get pods -n my-tackle-operator
Note: This can take one to five minutes depending on the cluster resources.
The default auth enabled credentials are: admin/password