Use the Katacoda hands on learning to review the directory structure and config examples https://academy.lucidworks.com/fusion-architecture/526426
customize_fusion_values.sh script uses the helm chart, cloud provider and config yaml file (see customize_fusion_values.yaml.example) to spin up the cluster.
By default, --num-solr instances and ZK_REPLICAS are set to 3
This is the file being run that controls the components https://github.com/lucidworks/fusion-cloud-native/blob/master/customize_fusion_values.yaml.example
We can disable a component/service like below
sql-service:
enabled: false
Control the replica count using the below (set replicaCount to 0 if you don't want to spin up the service) https://github.com/lucidworks/fusion-cloud-native/blob/master/example-values/replicas.yaml
Specify the resources like cpu and memory requirement for each component https://github.com/lucidworks/fusion-cloud-native/blob/master/example-values/resources.yaml
affinity rules applicable for multi region cloud environment. https://github.com/lucidworks/fusion-cloud-native/blob/master/example-values/affinity.yaml
Install Fusion locally with the variable SOLR_REPLICAS=1 on setup_f5_k8s.sh
For example, you can enable Kubernetes server that comes with your Docker Desktop For Mac
(To install Fusion locally, you should have a node with at least 12GB of memory, 100GB of disk and 4 CPU cores. The recommended setup is 16GB (or more) of memory and 8+ CPU cores. Please follow the instructions here to adjust your Docker’s resource limits)
Then run the setup_f5_k8s.sh script to install Fusion 5.x into local k8s cluster.
./setup_f5_k8s.sh -c <cluster_name> -r -n
Make sure all the pods are healthy and running by watching the cluster rollout using: kubectl get pods --watch
Hit ctrl-c once all the pods are running.
Run the following commands to access Fusion locally on http://localhost:6764
kubectl port-forward svc/proxy 6764:6764