apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:21:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 9b5620c3-8454-42c4-9a8e-d662a7b52296
    resourceVersion: "69701"
    uid: bfd1af17-d87d-49d5-a9d7-691da1e5c058
  spec:
    sourcePod: network-check-source-7d88cb55d8-dtrcq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:28:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.306504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:10:20Z"
    - latency: 1.152353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 1.113751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 1.251388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 867.561µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 1.096275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:05:20Z"
    - latency: 850.065µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:04:20Z"
    - latency: 933.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:03:20Z"
    - latency: 1.267155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:02:20Z"
    - latency: 934.779µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:21:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 9b5620c3-8454-42c4-9a8e-d662a7b52296
    resourceVersion: "68302"
    uid: b273c898-b264-49a3-9fc6-f15a06b43f70
  spec:
    sourcePod: network-check-source-7d88cb55d8-dtrcq
    targetEndpoint: adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:27:20Z"
      message: 'load-balancer-api-external: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.542902ms
      message: 'load-balancer-api-external: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 7.362143ms
      message: 'load-balancer-api-external: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 6.22844ms
      message: 'load-balancer-api-external: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 8.875179ms
      message: 'load-balancer-api-external: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 4.262802ms
      message: 'load-balancer-api-external: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 9.532609ms
      message: 'load-balancer-api-external: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 3.154391ms
      message: 'load-balancer-api-external: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 8.303944ms
      message: 'load-balancer-api-external: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 5.730057ms
      message: 'load-balancer-api-external: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:05:20Z"
    - latency: 8.225942ms
      message: 'load-balancer-api-external: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:21:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 9b5620c3-8454-42c4-9a8e-d662a7b52296
    resourceVersion: "68301"
    uid: 506c9931-2c78-40cd-9b53-3f7295fd8109
  spec:
    sourcePod: network-check-source-7d88cb55d8-dtrcq
    targetEndpoint: adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:27:20Z"
      message: 'load-balancer-api-internal: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.541854ms
      message: 'load-balancer-api-internal: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 7.393372ms
      message: 'load-balancer-api-internal: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 5.740377ms
      message: 'load-balancer-api-internal: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 8.965586ms
      message: 'load-balancer-api-internal: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 4.215914ms
      message: 'load-balancer-api-internal: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 9.549046ms
      message: 'load-balancer-api-internal: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 3.935347ms
      message: 'load-balancer-api-internal: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 8.406307ms
      message: 'load-balancer-api-internal: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 8.765355ms
      message: 'load-balancer-api-internal: tcp connection to adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:05:20Z"
    - latency: 8.323325ms
      message: 'load-balancer-api-internal: resolved host name adb4a6049d25346a2be5a7652b3b99ad-045829fbb79924ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:21:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-128-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 9b5620c3-8454-42c4-9a8e-d662a7b52296
    resourceVersion: "69699"
    uid: 2f9037f9-582f-4586-abc9-7a8e91505483
  spec:
    sourcePod: network-check-source-7d88cb55d8-dtrcq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:28:20Z"
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.520284ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:10:20Z"
    - latency: 2.365648ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 2.314182ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 2.530396ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 2.701347ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 2.026321ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:05:20Z"
    - latency: 2.153744ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:04:20Z"
    - latency: 2.33435ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:03:20Z"
    - latency: 2.379286ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:02:20Z"
    - latency: 2.417282ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:21:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-129-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 9b5620c3-8454-42c4-9a8e-d662a7b52296
    resourceVersion: "69700"
    uid: cb73b160-a527-4efe-ae50-c8e7ac3793f7
  spec:
    sourcePod: network-check-source-7d88cb55d8-dtrcq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:28:20Z"
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.703581ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:10:20Z"
    - latency: 2.275057ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 2.347935ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 2.318939ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 2.127703ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 2.105971ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:05:20Z"
    - latency: 2.361225ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:04:20Z"
    - latency: 2.180428ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:03:20Z"
    - latency: 2.514664ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:02:20Z"
    - latency: 2.385026ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:21:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-136-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 9b5620c3-8454-42c4-9a8e-d662a7b52296
    resourceVersion: "69698"
    uid: 2ab8b7ac-d84b-409f-93f0-6ef265486a40
  spec:
    sourcePod: network-check-source-7d88cb55d8-dtrcq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:28:20Z"
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 973.91µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:10:20Z"
    - latency: 907.131µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 1.052929ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 992.959µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 1.167777ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 1.0563ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:05:20Z"
    - latency: 1.215262ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:04:20Z"
    - latency: 913.739µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:03:20Z"
    - latency: 1.029958ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:02:20Z"
    - latency: 923.645µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T19:21:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 9b5620c3-8454-42c4-9a8e-d662a7b52296
    resourceVersion: "68300"
    uid: b9381769-20df-4543-9abe-79d0db4c85d4
  spec:
    sourcePod: network-check-source-7d88cb55d8-dtrcq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T19:27:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.053064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 1.771075ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:09:20Z"
    - latency: 812.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 1.800695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:08:20Z"
    - latency: 1.287365ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 1.680684ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:07:20Z"
    - latency: 925.645µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 2.00014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:06:20Z"
    - latency: 798.763µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T20:05:20Z"
    - latency: 1.601881ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T20:05:20Z"
kind: List
metadata:
  resourceVersion: ""