apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:36:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-98-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-98.ec2.internal
      uid: 0303ed7b-a934-4988-98c9-0d5566b6a2ed
    resourceVersion: "61953"
    uid: 60760b8d-51c1-45f9-bda3-a7caf465dd50
  spec:
    sourcePod: network-check-source-869dcfcdcd-bskbc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:43:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.064037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 1.06604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 1.000674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 956.8µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 1.140068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:14:06Z"
    - latency: 1.024968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:13:06Z"
    - latency: 1.061132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:12:06Z"
    - latency: 1.108504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:11:06Z"
    - latency: 1.511639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:10:06Z"
    - latency: 1.023325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:09:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:36:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-98-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-98.ec2.internal
      uid: 0303ed7b-a934-4988-98c9-0d5566b6a2ed
    resourceVersion: "61955"
    uid: 7a152197-ca83-45ff-a47d-2b34f8ef4149
  spec:
    sourcePod: network-check-source-869dcfcdcd-bskbc
    targetEndpoint: aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:42:06Z"
      message: 'load-balancer-api-external: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.666764ms
      message: 'load-balancer-api-external: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 7.695081ms
      message: 'load-balancer-api-external: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 4.467264ms
      message: 'load-balancer-api-external: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 8.111162ms
      message: 'load-balancer-api-external: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 4.350542ms
      message: 'load-balancer-api-external: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 9.249178ms
      message: 'load-balancer-api-external: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 6.117667ms
      message: 'load-balancer-api-external: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 6.647404ms
      message: 'load-balancer-api-external: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 3.485167ms
      message: 'load-balancer-api-external: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:14:06Z"
    - latency: 8.489109ms
      message: 'load-balancer-api-external: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:36:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-98-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-98.ec2.internal
      uid: 0303ed7b-a934-4988-98c9-0d5566b6a2ed
    resourceVersion: "61954"
    uid: 462ee129-0620-4e0f-8d01-f2d867c74eb6
  spec:
    sourcePod: network-check-source-869dcfcdcd-bskbc
    targetEndpoint: aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:42:06Z"
      message: 'load-balancer-api-internal: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.182236ms
      message: 'load-balancer-api-internal: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 7.655374ms
      message: 'load-balancer-api-internal: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 5.10207ms
      message: 'load-balancer-api-internal: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 8.142018ms
      message: 'load-balancer-api-internal: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 4.421421ms
      message: 'load-balancer-api-internal: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 9.223137ms
      message: 'load-balancer-api-internal: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 6.082578ms
      message: 'load-balancer-api-internal: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 6.578631ms
      message: 'load-balancer-api-internal: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 5.83598ms
      message: 'load-balancer-api-internal: tcp connection to aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:14:06Z"
    - latency: 8.566857ms
      message: 'load-balancer-api-internal: resolved host name aaaf2c34929e14f038d429880e377eb7-016897258eb91c10.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:36:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-98-to-network-check-target-ip-10-0-133-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-98.ec2.internal
      uid: 0303ed7b-a934-4988-98c9-0d5566b6a2ed
    resourceVersion: "61950"
    uid: 6d78deb7-88dc-4d00-be17-5d67756b1950
  spec:
    sourcePod: network-check-source-869dcfcdcd-bskbc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:43:06Z"
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.736491ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 2.270843ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 2.124624ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 2.031958ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 2.384965ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:14:06Z"
    - latency: 2.651027ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:13:06Z"
    - latency: 2.362335ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:12:06Z"
    - latency: 2.706058ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:11:06Z"
    - latency: 2.394396ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:10:06Z"
    - latency: 2.428927ms
      message: 'network-check-target-ip-10-0-133-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:09:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:36:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-98-to-network-check-target-ip-10-0-140-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-98.ec2.internal
      uid: 0303ed7b-a934-4988-98c9-0d5566b6a2ed
    resourceVersion: "61952"
    uid: f7d7e83f-6ecb-4894-ac51-fe5fa617b447
  spec:
    sourcePod: network-check-source-869dcfcdcd-bskbc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:43:06Z"
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.334ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 2.512856ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 2.386696ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 2.263304ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 2.359835ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:14:06Z"
    - latency: 2.448548ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:13:06Z"
    - latency: 2.566152ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:12:06Z"
    - latency: 2.139483ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:11:06Z"
    - latency: 2.359403ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:10:06Z"
    - latency: 2.206911ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:09:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:36:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-98-to-network-check-target-ip-10-0-140-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-98.ec2.internal
      uid: 0303ed7b-a934-4988-98c9-0d5566b6a2ed
    resourceVersion: "61949"
    uid: 9571f034-9f82-4d57-9030-a927cda91a54
  spec:
    sourcePod: network-check-source-869dcfcdcd-bskbc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:43:06Z"
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148468ms
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 818.156µs
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 1.152766ms
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 962.382µs
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 808.71µs
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:14:06Z"
    - latency: 888.156µs
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:13:06Z"
    - latency: 1.10492ms
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:12:06Z"
    - latency: 885.372µs
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:11:06Z"
    - latency: 896.281µs
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:10:06Z"
    - latency: 709.494µs
      message: 'network-check-target-ip-10-0-140-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:09:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:36:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-98-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-98.ec2.internal
      uid: 0303ed7b-a934-4988-98c9-0d5566b6a2ed
    resourceVersion: "61951"
    uid: 7aef10ef-9985-428e-99fa-cdb9bb6871db
  spec:
    sourcePod: network-check-source-869dcfcdcd-bskbc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:42:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.115388ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 1.872796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:18:06Z"
    - latency: 912.428µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 1.789163ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:17:06Z"
    - latency: 1.079742ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 2.070986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:16:06Z"
    - latency: 923.572µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 1.712658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:15:06Z"
    - latency: 826.86µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:14:06Z"
    - latency: 1.720607ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:14:06Z"
kind: List
metadata:
  resourceVersion: ""