apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T19:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-238.ec2.internal
      uid: fc1ba743-c09d-4335-b7ad-3d6c6ee789d7
    resourceVersion: "72887"
    uid: 0544cb2c-9a32-45ec-8778-4f880f931fe5
  spec:
    sourcePod: network-check-source-7d88cb55d8-wzzdp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T19:36:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.532µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 2.120185ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 951.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 1.166046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 1.163103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:07:29Z"
    - latency: 1.120682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:06:29Z"
    - latency: 1.315192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:05:29Z"
    - latency: 944.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:04:29Z"
    - latency: 935.789µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:03:29Z"
    - latency: 1.151909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T19:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-238.ec2.internal
      uid: fc1ba743-c09d-4335-b7ad-3d6c6ee789d7
    resourceVersion: "72888"
    uid: 036f86cd-3636-45c0-b529-04d386725b29
  spec:
    sourcePod: network-check-source-7d88cb55d8-wzzdp
    targetEndpoint: a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T19:35:29Z"
      message: 'load-balancer-api-external: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.177634ms
      message: 'load-balancer-api-external: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 8.800036ms
      message: 'load-balancer-api-external: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 4.315604ms
      message: 'load-balancer-api-external: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 9.248113ms
      message: 'load-balancer-api-external: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 4.801813ms
      message: 'load-balancer-api-external: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 9.105891ms
      message: 'load-balancer-api-external: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 3.959997ms
      message: 'load-balancer-api-external: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 8.908121ms
      message: 'load-balancer-api-external: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 4.461261ms
      message: 'load-balancer-api-external: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:07:29Z"
    - latency: 9.835502ms
      message: 'load-balancer-api-external: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T19:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-238.ec2.internal
      uid: fc1ba743-c09d-4335-b7ad-3d6c6ee789d7
    resourceVersion: "72890"
    uid: 0bb4efd8-da9f-4279-856f-b547d2cdcd51
  spec:
    sourcePod: network-check-source-7d88cb55d8-wzzdp
    targetEndpoint: a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T19:35:29Z"
      message: 'load-balancer-api-internal: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.178238ms
      message: 'load-balancer-api-internal: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 8.955591ms
      message: 'load-balancer-api-internal: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 4.399885ms
      message: 'load-balancer-api-internal: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 9.306719ms
      message: 'load-balancer-api-internal: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 4.084583ms
      message: 'load-balancer-api-internal: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 9.022728ms
      message: 'load-balancer-api-internal: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 3.885397ms
      message: 'load-balancer-api-internal: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 9.064921ms
      message: 'load-balancer-api-internal: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 3.610272ms
      message: 'load-balancer-api-internal: tcp connection to a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:07:29Z"
    - latency: 9.800482ms
      message: 'load-balancer-api-internal: resolved host name a45cbb576b36c4b558ac02824b2241ed-dad27e9ccb36c0ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T19:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-238-to-network-check-target-ip-10-0-131-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-238.ec2.internal
      uid: fc1ba743-c09d-4335-b7ad-3d6c6ee789d7
    resourceVersion: "72882"
    uid: fd48ce04-f5e1-4fca-a512-53b3668dfe80
  spec:
    sourcePod: network-check-source-7d88cb55d8-wzzdp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T19:36:29Z"
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.248522ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 2.453061ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 2.413002ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 2.299863ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 2.446726ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:07:29Z"
    - latency: 2.271337ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:06:29Z"
    - latency: 2.278294ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:05:29Z"
    - latency: 2.412975ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:04:29Z"
    - latency: 2.412265ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:03:29Z"
    - latency: 2.422634ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T19:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-238-to-network-check-target-ip-10-0-133-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-238.ec2.internal
      uid: fc1ba743-c09d-4335-b7ad-3d6c6ee789d7
    resourceVersion: "72885"
    uid: 23641361-1e23-488a-bae5-73ee5d63d042
  spec:
    sourcePod: network-check-source-7d88cb55d8-wzzdp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T19:36:29Z"
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.067866ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 2.601446ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 2.202229ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 2.286931ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 2.387904ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:07:29Z"
    - latency: 2.399692ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:06:29Z"
    - latency: 2.31416ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:05:29Z"
    - latency: 2.335826ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:04:29Z"
    - latency: 2.07029ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:03:29Z"
    - latency: 2.893493ms
      message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T19:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-238-to-network-check-target-ip-10-0-141-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-238.ec2.internal
      uid: fc1ba743-c09d-4335-b7ad-3d6c6ee789d7
    resourceVersion: "72883"
    uid: 51cebfbc-a6bc-4212-9a59-1df063811cd3
  spec:
    sourcePod: network-check-source-7d88cb55d8-wzzdp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T19:36:29Z"
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.443353ms
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 1.61321ms
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 1.502088ms
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 1.169278ms
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 972.972µs
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:07:29Z"
    - latency: 1.419134ms
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:06:29Z"
    - latency: 889.376µs
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:05:29Z"
    - latency: 1.068684ms
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:04:29Z"
    - latency: 912.356µs
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:03:29Z"
    - latency: 1.669216ms
      message: 'network-check-target-ip-10-0-141-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T19:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-238.ec2.internal
      uid: fc1ba743-c09d-4335-b7ad-3d6c6ee789d7
    resourceVersion: "72884"
    uid: 10410aba-a86d-45cf-bb06-77baaba53e47
  spec:
    sourcePod: network-check-source-7d88cb55d8-wzzdp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T19:35:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.382414ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 1.841069ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:11:29Z"
    - latency: 979.454µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 3.073496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:10:29Z"
    - latency: 1.336672ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 1.740908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:09:29Z"
    - latency: 952.578µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 1.808855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:08:29Z"
    - latency: 902.419µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T20:07:29Z"
    - latency: 2.032988ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T20:07:29Z"
kind: List
metadata:
  resourceVersion: ""