Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Allow to customize cluster and zookeeper timeout settings #247

Allow to customize cluster and zookeeper timeout settings

Allow to customize cluster and zookeeper timeout settings #247

Workflow file for this run

name: Test
on:
push:
branches:
- master
pull_request:
branches:
- master
jobs:
example:
name: Minikube installation - Basic test
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Setup Minikube
uses: manusa/[email protected]
with:
minikube version: 'v1.28.0'
kubernetes version: 'v1.25.4'
github token: ${{ secrets.GITHUB_TOKEN }}
#- run: minikube addons list
#- name: Interact with the cluster
# run: kubectl get nodes
- name: Checkout code
uses: actions/checkout@v3
- name: Install dependencies
run: |
helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo add dysnix https://dysnix.github.io/charts/
helm repo update
helm dep up
- name: Install Nifi
run: helm install nifi .
- name: Check deployment status
run: |
kubectl rollout status --watch statefulset/nifi --timeout=5m
- name: Wait for NiFi web server to start
run: |
for n in [ 0 1 2 3 4 5 6 7 8 9 ]
do
if kubectl logs pod/nifi-0 -c app-log | grep 'JettyServer NiFi has started'
then
exit 0
fi
sleep 30
done
echo NiFi did not start for 300 seconds!
exit 1
- name: Check that web application responds with expected content
run: |
kubectl exec pod/nifi-0 -c server -- curl -sk https://localhost:8443 | \
grep 'You may have mistyped'