Rollback 1.5.2

[strongjz]

Signed-off-by: James Strong [email protected]

Reverting 1.5.2, there are breaking changes to path type that are causing issues.

#9464
#9466

[k8s-ci-robot]

@strongjz: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rikatz]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz, strongjz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rikatz,strongjz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Callek]

Either artifacthub is confused OR this never actually rolled back.

https://artifacthub.io/packages/helm/ingress-nginx/ingress-nginx/4.4.2?modal=template&compare-to=4.4.1

The CHANGELOG on artifacthub is also identical to the changelog for 4.4.0.

CCL @strongjz

[strongjz]

Either artifacthub is confused OR this never actually rolled back.

https://artifacthub.io/packages/helm/ingress-nginx/ingress-nginx/4.4.2?modal=template&compare-to=4.4.1

The CHANGELOG on artifacthub is also identical to the changelog for 4.4.0.

CCL @strongjz

I reverted commits and didn't update the change log. The issue now is that with artifacthub We'd have to release a new chart to update the changelog. So effectively 4.4.0 and 4.4.2 are the same. Apologize for the confusion, we wanted to rollout a fix and I was only thinking of rolling back the controller version.