Skip to content

Commit

Permalink
try again
Browse files Browse the repository at this point in the history
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
  • Loading branch information
vsoch committed Dec 20, 2022
1 parent 5d6125a commit d5055f4
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 6 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ jobs:
kubectl apply -f examples/tests/${applyfile}
sleep 10
make list
pkill ${pid}
kill ${pid} || echo "Already dead"
# - name: Test service URLs
# run: |
Expand Down
13 changes: 8 additions & 5 deletions docs/development/developer-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -225,7 +225,12 @@ make deploy
kubectl create namespace flux-operator

# Apply a named job (e.g., minicluster-<job>.yaml in examples/tests)
$ make name=hello-world applytest
make name=hello-world applytest

# run the operator (in actions we run in subprocess and then kill with pid)
make run &
pid=$!
echo "PID for running cluster is ${pid}"

# Get pods for all namespaces (you'd see system operator and flux-operator)
kubectl get pod --all-namespaces
Expand All @@ -235,10 +240,8 @@ kubectl logs -n flux-operator flux-sample-0-f7thx
```

The tests above are headless, meaning they submit commands directly, and that way
we don't need to do it in the UI and can programatically determine if they were successful.

kubectl apply -f examples/tests/minicluster-hello-world.yaml
minicluster.flux-framework.org/flux-sample created
we don't need to do it in the UI and can programmatically determine if they were successful.
Note that we are looking at [kuttl](https://kuttl.dev/docs/kuttl-test-harness.html#writing-your-first-test).

## Documentation

Expand Down

0 comments on commit d5055f4

Please sign in to comment.