Venktesh Shivam Patel

okay looks like issue has nothing to do with the orphaned lease from last installation `nginx-ingress-leader` which can now be deleted. Can you please check if this issue only occurs...

sorry meant to ask if you run into same issue if installing/upgrading just using helm on test cluster, I'm unable to repro it unfortunately using helm

Hey @sov-msaeed, unfortunately I can't comment on timeline for this enhancement but we will definitely be reviewing attached PR.

closing in favour of https://github.com/nginx/kubernetes-ingress/pull/7993

@hafe is this specific to ArgoCD? haven't came across this in normal helm or manifest deployments. Having lease in helm templates allows it to manage them.

yep we added it in nginx-ingress so helm can manage it and also remove it once the application is uninstalled

related https://github.com/nginxinc/kubernetes-ingress/discussions/4341

Hey @mightymouse2045 we looked at this issue and would like to know if you'll be interested in creating a PR with documentation?

@aknot242 can you please run `make update-crds` from project root and commit the updated files

@jjngx @hafe lets add it to the docs as well for clarity and since we can't report it through configmap event: > ` access_log` value will be set to `/dev/stdout...