Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I can deploy workers via zbchaos #235

Closed
Tracked by #139
ChrisKujawa opened this issue Nov 17, 2022 · 0 comments · Fixed by #247
Closed
Tracked by #139

I can deploy workers via zbchaos #235

ChrisKujawa opened this issue Nov 17, 2022 · 0 comments · Fixed by #247
Assignees

Comments

@ChrisKujawa
Copy link
Member

ChrisKujawa commented Nov 17, 2022

Deploy the benchmarks workers for the chaos experiments, similar as it is done in the kotlin-worker

This enables experiments like:

  • worker-restart
  • But also experiments where we await the result of an instance
@ChrisKujawa ChrisKujawa self-assigned this Nov 17, 2022
ChrisKujawa added a commit that referenced this issue Nov 22, 2022
Add new sub-command to deploy Zeebe workers into a Zeebe cluster, which
can be used for several chaos experiments. This allows completing
process instances etc.

closes #235

--------

**Example:**


Non-verbose: Deploy worker:

```sh
$ ./zbchaos deploy worker
Worker successfully deployed to the current namespace: zell-chaos
```

Verbose: Deploy worker

```sh
$ ./zbchaos deploy worker -v
Connecting to zell-chaos
Running experiment in self-managed environment.
Deploy worker deployment to the current namespace: zell-chaos
Worker successfully deployed to the current namespace: zell-chaos
```

```sh
$ k get deployments.apps 
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
worker                     3/3     3            3           107s
```

Error when deployment already exists:


```
$ ./zbchaos deploy worker -v
Connecting to zell-chaos
Running experiment in self-managed environment.
Deploy worker deployment to the current namespace: zell-chaos
panic: deployments.apps "worker" already exists

```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant