Allows the creation of an ingress for the webhook receiver, this will let us rollout flux v2 in a smoother way since we have many k8s clusters and we have automations that take care of applying the charts. Today the chart does not allow the creation of an ingress for the webhook receiver and we are using it to reduce the time flux takes to deploy and mantain considerable reconciliation intervals without querying either source providers or aws to notice there is a new image on the repository.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
Signed-off-by: Yannick Stevenin steveninyannick@gmail.com
What this PR does / why we need it:
Allows the creation of an ingress for the webhook receiver, this will let us rollout flux v2 in a smoother way since we have many k8s clusters and we have automations that take care of applying the charts. Today the chart does not allow the creation of an ingress for the webhook receiver and we are using it to reduce the time flux takes to deploy and mantain considerable reconciliation intervals without querying either source providers or aws to notice there is a new image on the repository.
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged)Special notes for your reviewer:
Checklist
make reviewable