Switch to JSON formatted access logs

[dinofizz]

I'd like to emit access logs in JSON format so as to be able to improve their visibility in our OpenSearch index. In addition to this I made a number of changes:

• I did a general update of direct dependencies (apologies for the vendor folder changes)
• I removed references and flags related to legacy Kubernetes versions in our manifest/CRD generation
• I've switched to using the latest version of controller-gen
• I'm using docker buildx build with a platform flag specifying the architecture to be linux amd64
• I've extended some of the RBAC roles to align with changes in our internal "deployment" repo

Example pod logs showing admin logs and cluster access logs (admin logs left as default - but we can move these to JSON to if we want):

JSON access log (prettified):

{
  "response_code": 0,
  "upstream_cluster": "example-www_TCP_443",
  "bytes_received": 1294,
  "bytes_sent": 5999,
  "downstream_local_address": "10.129.191.27:443",
  "duration": 445,
  "upstream_host": "93.184.215.14:443",
  "downstream_remote_address": "10.129.187.50:48990",
  "response_flags": "-",
  "start_time": "2025-01-08T14:12:19.041Z",
  "upstream_local_address": "10.129.191.27:37028"
}

[awnumar]

Do you think we should pin this to a specific hash?

[dinofizz]

I've pinned this with this commit b8a2e9c

[domgoodwin]

Do these roughly match our service mesh ones?

[dinofizz]

No, not exactly.

This is what we have for the service mesh

		"start_time":                     "%START_TIME%",
		"total_duration_ms":              "%DURATION%",
		"bytes_received":                 "%BYTES_RECEIVED%",
		"bytes_sent":                     "%BYTES_SENT%",
		"response_flags":                 "%RESPONSE_FLAGS%",
		"destination_host":               "%UPSTREAM_HOST%",
		"destination_service":            "%UPSTREAM_CLUSTER%",
		"source_address":                 "%DOWNSTREAM_REMOTE_ADDRESS%",
		"connection_id":                  "%CONNECTION_ID%",
		"connection_termination_details": "%CONNECTION_TERMINATION_DETAILS%",
		"requested_sni":                  "%REQUESTED_SERVER_NAME%",
		"hostname":                       "%HOSTNAME%",

vs what's in this PR:

          authority: '%REQ(:AUTHORITY)%'
          bytes_received: '%BYTES_RECEIVED%'
          bytes_sent: '%BYTES_SENT%'
          connection_termination_details: '%CONNECTION_TERMINATION_DETAILS%'
          downstream_local_address: '%DOWNSTREAM_LOCAL_ADDRESS%'
          downstream_remote_address: '%DOWNSTREAM_REMOTE_ADDRESS%'
          duration: '%DURATION%'
          method: '%REQ(:METHOD)%'
          path: '%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%'
          protocol: '%PROTOCOL%'
          requested_server_name: '%REQUESTED_SERVER_NAME%'
          response_code: '%RESPONSE_CODE%'
          response_code_details: '%RESPONSE_CODE_DETAILS%'
          response_flags: '%RESPONSE_FLAGS%'
          start_time: '%START_TIME%'
          upstream_cluster: '%UPSTREAM_CLUSTER%'
          upstream_host: '%UPSTREAM_HOST%'
          upstream_local_address: '%UPSTREAM_LOCAL_ADDRESS%'
          upstream_service_time: '%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%'
          upstream_transport_failure_reason: '%UPSTREAM_TRANSPORT_FAILURE_REASON%'
          user_agent: '%REQ(USER-AGENT)%'