[AIRFLOW-XXXX] Add architecture section to k8sexec docs#7406
[AIRFLOW-XXXX] Add architecture section to k8sexec docs#7406kaxil merged 1 commit intoapache:masterfrom
Conversation
5488b99 to
b3aa8fc
Compare
b3aa8fc to
0a8aa7e
Compare
0a8aa7e to
d15a22f
Compare
d15a22f to
6e4c2ab
Compare
|
Can you add some labels to the diagram, please? The diagram uses the Airflow logo to describe many different components. It is not clear what the role of each logo is. Lines appear in the diagram, but they are not described. I think that it is also worth numbering the next steps in the diagram, which allows for easier tracking of the message. If possible, it is worth using generally accepted conventions, e.g. sequence diagram. This makes the drawings simpler to understand and easier to draw. You could use online editor e.g. https://www.planttext.com/ I have one more comment. Can you maintain uniform naming between text and diagram also, please? You use the term "the backend DB" in the text, but it does not appear in the image, but instead is "PostgresSQL". I also prepared preview of your documentation: |
aec969b to
1c98154
Compare
Adds an architecture section the KubernetesExecutor documentation
1c98154 to
5190269
Compare
Adds an architecture section the KubernetesExecutor documentation
Issue link:
Document only change, no JIRA issueMake sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX].In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.