Diff on Endpoint confused by IP sorting

[warmfusion]

Describe the bug
When using an Endpoint object with a set of IP addresses explicitally declared, when comparing the state against the intention the diff appears to sort the IP addresses Alphanumerically whilst Kubernetes sorts by octet resulting in a mistaken diff output.

To Reproduce
Provide a configuration as shown;

apiVersion: v1
kind: Endpoints
metadata:
  annotations:
    description: A workaround to support a set of backend IPs for solr
    linkerd.io/inject: disabled
  name: solrcloud
  namespace: engineering-fcsis-vanilla-quantum
subsets:
- addresses:
  - ip: 172.20.10.97
  - ip: 172.20.10.98
  - ip: 172.20.10.99
  - ip: 172.20.10.100
  - ip: 172.20.10.101
  ports:
  - name: solr-http
    port: 8080

Expected behavior

State in kubernetes is applied and no diff errors are shown.

** Actual Behaviour **

The diff triggers an out-of-sync warning as the IP list gets changed by some part of the system.

Screenshots

Version

argocd: v1.0.1+5fe1447.dirty
  BuildDate: 2019-05-28T17:28:05Z
  GitCommit: 5fe1447b722716649143c63f9fc054886d5b111c
  GitTreeState: dirty
  GoVersion: go1.11.4
  Compiler: gc
  Platform: darwin/amd64
argocd-server: v1.0.1+5fe1447.dirty
  BuildDate: 2019-05-28T17:27:38Z
  GitCommit: 5fe1447b722716649143c63f9fc054886d5b111c
  GitTreeState: dirty
  GoVersion: go1.11.4
  Compiler: gc
  Platform: linux/amd64
  Ksonnet Version: 0.13.1

[alexec]

Interesting. Can you work around by making sure the Git repo has the ASCII ordered list, rather than the (and admittedly nicer) dictionary order.

[jessesuen]

This is the same problem that HPA has. The only real workaround is to order the list in the same way that Kubernetes orders this list.

It's unlikely that Argo CD can do anything about this because we have no way to understand if list order is significant or not for all types of objects.

[warmfusion]

The workaround works as a solution, albeit one that needs a little twiddling if changes are made.

Could there perhaps be a whitelist of known sortable elements for both HPA and endpoints for instance?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[abhishekjiitr]

+1, really annoying for endpoint resources with lots of addresses

[abhishekjiitr]

Interesting. Can you work around by making sure the Git repo has the ASCII ordered list, rather than the (and admittedly nicer) dictionary order.

This doesn't seem to work for ascii ordered list. Kubernetes seems to sort the list like this, which is not ascii ordered:

apiVersion: v1
kind: Endpoints
metadata:
  name: qa
  namespace: monitoring
subsets:
  - addresses:
      - ip: 10.2.4.5
    ports:
      - name: bindexporter
        port: 9119
        protocol: TCP
      - name: nodeexporter
        port: 9100
        protocol: TCP
      - name: postgresexporter
        port: 9187
        protocol: TCP
      - name: apacheexporter
        port: 9117
        protocol: TCP
      - name: jmxexporter
        port: 7090
        protocol: TCP

[darshanime]

Currently, the IPs in endpoints are sorted lexicographically
https://github.com/kubernetes/kubernetes/blob/2da917d3701904939683ac545c7869c1e89b7840/pkg/api/endpoints/util.go#L191-L200

In argo-cd, how about sorting the manifest values using this function before comparing them for diffing?

---

To solve this more generally, is it a good idea to introduce a "normalizing" step before diffing which takes care of such intricacies based on a global mapping of GVK-field <> sorting order.