> For the complete documentation index, see [llms.txt](https://docs.cloudeka.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.id/platform/deka-harbor/configuration-worker.md). # Configuration Worker On workers you can configure workers by adding or removing workers on Deka Harbor. Workers that cannot be deleted according to the limit entered by Superadmin. ## Add Worker Here are the steps to add workers: * On the service page of the Cloudka portal select the Deka Harbor menu on the Platform.

\\ * Select the cluster to which the worker will be added by clicking More in the Action column and clicking Detail.

* On the Worker tab click the Create Worker button.

* Select the flavored worker and the number of nodes to add. Click the Create button to continue with the process.

* Wait until the process completes and the worker displays on the worker list.

## Delete Worker You can only remove added workers manually. Here are the steps to remove the worker: * On the Worker tab select an unused worker by clicking the Delete button.

* Click the Confirm button.

* Wait until the removal process is complete and a "Deka Harbor Worker \[worker name] has successfully deleted!" notice displays.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cloudeka.id/platform/deka-harbor/configuration-worker.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.