> For the complete documentation index, see [llms.txt](https://docs.akamas.io/quick-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-box/aiab-04-optimize-a-java-based-kubernetes-application-online-boutique/aiab-04-create-the-workflow.md).

# \[AIAB-04] Create the workflow

The next step is to create a workflow describing the steps executed in each experiment of your optimization study.

A workflow in an optimization study for Kubernetes is typically composed of the following tasks:

* Write the manifest file corresponding to a new configuration of the selected optimization parameters to the target system using the FileConfigurator operator.
* Apply the manifest with the new configurations via `kubectl`.
* Wait until the rollout of all services has completed.
* Run the performance test.

You can create the Akamas workflow with a single command by leveraging the script `create-workflow.sh` provided in the `scripts` folder. Also, this script requires a parameter:

* `CLUSTER_IP`: the public IP address of the cluster

The artifact in your cloned repo contains the *workflow\.yaml* file that creates the workflow by issuing the following command:

```bash
bash kubernetes-online-boutique/scripts/create-workflow.sh <CLUSTER_IP>
```

You can verify that this workflow has been created by accessing the corresponding Workflow menu in the Akamas UI:

All scripts and templates used in the steps of this workflow can be found in the `kubernetes-online-boutique/workflow-artifacts` folder.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-box/aiab-04-optimize-a-java-based-kubernetes-application-online-boutique/aiab-04-create-the-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.