Sort ingresses by creation timestamp

[aledbf]

What this PR does / why we need it: ResourceVersion is not immutable. It can change if the ingress is modified. Switching to CreationTimestamp to avoid edge cases.

[ElvinEfendi]

Given ingresses A and B where A is created before B and they both have same host but different paths pointing to different services and different set of annotations. In this case the annotations from ingress A will be overridden by the annotations in ingress B if they are server level.

With the changes in this PR, when an annotation in ingress A changes, it will have no effect. However without this PR, the new change would be effective since the resource version of A would be more recent.

That being said using creating time makes more sense. The case (where user overrides annotation defined in another ingress) I described above is a bad practice anyway.

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, ElvinEfendi

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 [ElvinEfendi,aledbf]

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