You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tests/README.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# integration tests
2
2
3
-
This is a working example of a kubernetes application `dapp`, that is deployed on CI during circle's `kind_k8s` and `kind_compile` job.
3
+
This is a working example of a kubernetes application `dapp`, that is deployed on CI during circle's `kind_k8s` and `kind_compile` job. See [this part of the .circleci/config](https://github.com/clux/kube-rs/blob/9837d60246a0528f8d810243fe544014d1e51dca/.circleci/config.yml#L32-L84).
4
4
5
5
## Behavior
6
6
The app currently only does what the `job_api` example does, but from within the cluster, so it needs the rbac permissions to `create` a `job` in `batch`.
@@ -27,8 +27,6 @@ It's successful if the app exits successfully, without encountering errors.
27
27
## Locally
28
28
Start a cluster first. Say, via `make minikube-create && make minikube` or `make kind-create && make kind`.
29
29
30
-
NB: Mileage may vary. At time of writing `kind` was best for CI (but had troubles loading images), whereas `minikube` seems more battle tested for local development at the moment.
31
-
32
30
### Building Yourself
33
31
Run `make integration-test` to cross compile `dapp` with `muslrust` locally using the same docker image, and then deploy it to the current active cluster.
0 commit comments