apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 76a80486-9ac1-4604-aabf-c838cb344ad7
    resourceVersion: "76750"
    uid: a4d49552-13d2-4992-b37c-c7155df8dfb3
  spec:
    sourcePod: network-check-source-989f8b8dc-gv9xz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 941.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 892.408µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 1.174449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 1.094527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:38Z"
    - latency: 848.859µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:38Z"
    - latency: 964.4µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:38Z"
    - latency: 1.302264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:38Z"
    - latency: 1.048634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:38Z"
    - latency: 1.044001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:38Z"
    - latency: 1.037438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 76a80486-9ac1-4604-aabf-c838cb344ad7
    resourceVersion: "77555"
    uid: c795f102-966f-4a69-85e6-d29af435e20f
  spec:
    sourcePod: network-check-source-989f8b8dc-gv9xz
    targetEndpoint: aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:38Z"
      message: 'load-balancer-api-external: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.868265ms
      message: 'load-balancer-api-external: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:38Z"
    - latency: 6.772738ms
      message: 'load-balancer-api-external: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:55:38Z"
    - latency: 5.296374ms
      message: 'load-balancer-api-external: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 6.987175ms
      message: 'load-balancer-api-external: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 5.293064ms
      message: 'load-balancer-api-external: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 7.698645ms
      message: 'load-balancer-api-external: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 6.373564ms
      message: 'load-balancer-api-external: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 6.19509ms
      message: 'load-balancer-api-external: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 6.146285ms
      message: 'load-balancer-api-external: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:38Z"
    - latency: 6.963613ms
      message: 'load-balancer-api-external: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:51:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 76a80486-9ac1-4604-aabf-c838cb344ad7
    resourceVersion: "77556"
    uid: 9fde6de4-36ab-4220-8485-0945b5658d42
  spec:
    sourcePod: network-check-source-989f8b8dc-gv9xz
    targetEndpoint: aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:38Z"
      message: 'load-balancer-api-internal: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.483572ms
      message: 'load-balancer-api-internal: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:38Z"
    - latency: 6.827144ms
      message: 'load-balancer-api-internal: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:55:38Z"
    - latency: 7.03983ms
      message: 'load-balancer-api-internal: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 7.057123ms
      message: 'load-balancer-api-internal: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 5.255859ms
      message: 'load-balancer-api-internal: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 7.725516ms
      message: 'load-balancer-api-internal: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 6.352357ms
      message: 'load-balancer-api-internal: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 6.250549ms
      message: 'load-balancer-api-internal: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 7.341682ms
      message: 'load-balancer-api-internal: tcp connection to aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:38Z"
    - latency: 7.002401ms
      message: 'load-balancer-api-internal: resolved host name aa419ce991be54aee901e5aa7e5ab1f5-21a7125f3e1aac29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:51:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-ip-10-0-128-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 76a80486-9ac1-4604-aabf-c838cb344ad7
    resourceVersion: "76747"
    uid: fb521e5e-59f8-4742-b264-531d445dcafb
  spec:
    sourcePod: network-check-source-989f8b8dc-gv9xz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:38Z"
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.945142ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 2.217944ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 2.290872ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 2.603773ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:38Z"
    - latency: 2.288616ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:38Z"
    - latency: 2.231117ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:38Z"
    - latency: 2.038737ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:38Z"
    - latency: 2.168355ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:38Z"
    - latency: 2.166372ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:38Z"
    - latency: 2.173464ms
      message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-ip-10-0-130-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 76a80486-9ac1-4604-aabf-c838cb344ad7
    resourceVersion: "76749"
    uid: 72d58bc1-2ce7-4217-a39a-357ad0d45298
  spec:
    sourcePod: network-check-source-989f8b8dc-gv9xz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:38Z"
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.888144ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 2.147866ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 2.007829ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 2.469397ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:38Z"
    - latency: 2.459883ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:38Z"
    - latency: 2.268982ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:38Z"
    - latency: 2.276054ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:38Z"
    - latency: 1.831272ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:38Z"
    - latency: 2.462458ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:38Z"
    - latency: 2.404589ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-ip-10-0-142-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 76a80486-9ac1-4604-aabf-c838cb344ad7
    resourceVersion: "76748"
    uid: 14e2c983-152c-46f6-a5c8-454cd1e10f70
  spec:
    sourcePod: network-check-source-989f8b8dc-gv9xz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:38Z"
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 900.215µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 1.271492ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 885.832µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 1.267851ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:38Z"
    - latency: 829.932µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:38Z"
    - latency: 940.655µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:38Z"
    - latency: 968.807µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:38Z"
    - latency: 903.753µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:38Z"
    - latency: 856.217µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:38Z"
    - latency: 964.813µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 76a80486-9ac1-4604-aabf-c838cb344ad7
    resourceVersion: "77554"
    uid: e8987726-e587-46f7-8c2f-fa30fa6461c0
  spec:
    sourcePod: network-check-source-989f8b8dc-gv9xz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 770.77µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:38Z"
    - latency: 1.77174ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:55:38Z"
    - latency: 1.23546ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 1.849719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:54:38Z"
    - latency: 950.38µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 1.737442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:53:38Z"
    - latency: 804.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 1.588568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:52:38Z"
    - latency: 1.39503ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:38Z"
    - latency: 1.735982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:51:38Z"
kind: List
metadata:
  resourceVersion: ""