Repository: jina-ai/serve
Pull request: docs: common args inheritence from Flow API
<!---Decomposing the complex issue into subtasks can help you build it step-by-step. Thanks for your pull request! :rocket: --->
<!---We know that dev life is hectic, but **please provide a (brief) description** of what your PR does, and how it does it. **Otherwise, your PR cannot be reviewed!** --->
<!---This policy was agreed upon in a past company retro, and makes everyone's life a little easier. Thanks for your collaboration!--->

**Goals:**
<!---https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword--->

- resolves #5353 
- [ ] check and update documentation. See [guide](https://github.com/jina-ai/jina/blob/master/CONTRIBUTING.md#-contributing-documentation) and ask the team.


Problem statement:
Document the common args inheritence from Flow API to Executors and Gateway
Currently, flow API accepts all args of all entities.
These args will be propagated to other entities (gateway, executor) with some occasional exclusion.
We need to document this behavior and document what arguments are excluded

Hints from issue discussion:

Commit message: docs: add excluded arguments to flow

Patch to review:
diff --git a/docs/concepts/flow/basics.md b/docs/concepts/flow/basics.md
index 47ab296ffbba3..a3ae0f99ec9c2 100644
--- a/docs/concepts/flow/basics.md
+++ b/docs/concepts/flow/basics.md
@@ -301,6 +301,13 @@ You can control the access mode, storage class name and capacity of the attached
 `JINA_K8S_ACCESS_MODES`, `JINA_K8S_STORAGE_CLASS_NAME` and `JINA_K8S_STORAGE_CAPACITY`. Only the first volume will be considered to be mounted.
 ```
 
+```{tip}
+All arguments received by `Flow()` API will be propagated to other entities (gateway, executor) with the following exclusions:
+
+- `uses` and `uses_with` won't be passed to gateway
+- `port`, `port_monitoring`, `uses` and `uses_with` won't be passed to executor
+```
+
 ```{admonition} See also
 :class: seealso
 For more in-depth guides on Flow deployment, check our how-tos for {ref}`Docker compose <docker-compose>` and


Code review comments:
diff_hunk: @@ -301,6 +301,13 @@ You can control the access mode, storage class name and capacity of the attached
 `JINA_K8S_ACCESS_MODES`, `JINA_K8S_STORAGE_CLASS_NAME` and `JINA_K8S_STORAGE_CAPACITY`. Only the first volume will be considered to be mounted.
 ```
 
+```{tip}
path: docs/concepts/flow/basics.md
text: @user1:
important instead of tip