[[TOC]]
The purpose of this automation is to install BigBang onto a Kind cluster running on your local machine
- Create an env file from the example
cp example.env .env
- Set environment variables in the .env file to fetch dependencies for bigbang and the git repo where your git ops configuration will live.
- Get your username and CLI Secret from Registry1 for REGISTRY1_USERNAME and REGISTRY1_PASSWORD
- Create an access token from your gitlab account with api permissions and set your GIT_ACCESS_TOKEN to that.
- Get your username and CLI Secret from Registry1 for REGISTRY1_USERNAME and REGISTRY1_PASSWORD
- Set the GIT_BRANCH_NAME to a new branch you want your cluster to be managed from. This will be a branch on this repo
- Run
deploy.sh
, grab some coffee, it'll take around 10-15 minutes to complete - Kiali will be the last service to come up, visit http://kiali.bigbang.dev
cd bb-template/dev/
...
twistlock:
enabled: false # Set to true
values:
console:
persistence:
size: 5Gi
...
Push the new configuration and watch your cluster update all GitOps like
git commit -am "enable twistlock"
git push
watch kubectl hr,po -A
- To teardown run
teardown.sh
If elasticsearch doesn't come up please do the following to give the image the minimum space it needs
sysctl -w vm.max_map_count=262144
echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf
Similarly, fluentbit may enter crashLoopBackoff for an error [TIMESTAMP] [error] [plugins/in_tail/tail_fs_inotify.c:305 errno=24] Too many open files
, the below are possible fixes for that
sysctl -w fs.inotify.max_user_instances=1500
echo "fs.inotify.max_user_instances=1500" | sudo tee -a /etc/sysctl.conf
Also check for a low value set, and change as below
cat /proc/sys/fs/inotify/max_user_watches
# If the value of the cmd above is low, then adjust like this
sysctl -w fs.inotify.max_user_watches=525000
echo "fs.inotify.max_user_watches=525000" | sudo tee -a /etc/sysctl.conf