Skip to content

Conversation

@Seokyun-Ha
Copy link
Contributor

@Seokyun-Ha Seokyun-Ha commented Feb 19, 2024

I want to control flower probe configuration on helm values file.
Because, I think that the flower probe period is too often (5s), and I want to customize it 🙏

Please, take a look at, and let me know if there's something I missed 😄

reference kubernetes doc: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@boring-cyborg boring-cyborg bot added the area:helm-chart Airflow Helm Chart label Feb 19, 2024
@Seokyun-Ha Seokyun-Ha changed the title Flower probe config Flower K8s Probe config Feb 19, 2024
Copy link
Member

@hussein-awala hussein-awala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea! Could you add a test to ensure that everything works as expected?
https://github.com/apache/airflow/blob/main/helm_tests/other/test_flower.py

@Seokyun-Ha
Copy link
Contributor Author

hello, @hussein-awala ! I added probe values cofigurable test as you pointed 🙏

Thanks for reviewing!!

@potiuk potiuk merged commit 004dcb7 into apache:main Feb 20, 2024
@ephraimbuddy ephraimbuddy added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:helm-chart Airflow Helm Chart changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants