apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:14:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-33.ec2.internal
      uid: 085ae624-ef84-4bcb-a474-a6e004815e71
    resourceVersion: "30578"
    uid: 096bf40d-8e80-4944-a053-314a5cd2b960
  spec:
    sourcePod: network-check-source-56d84b9f44-xwljj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:21:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 920.765µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:28:48Z"
    - latency: 813.253µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:48Z"
    - latency: 822.133µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 1.128598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 1.154302ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 1.008229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 1.002362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:48Z"
    - latency: 1.160732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:48Z"
    - latency: 953.032µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:20:48Z"
    - latency: 845.322µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:19:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:14:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-33.ec2.internal
      uid: 085ae624-ef84-4bcb-a474-a6e004815e71
    resourceVersion: "29035"
    uid: 36705c44-8ae5-4df9-8ec2-e568a44c056c
  spec:
    sourcePod: network-check-source-56d84b9f44-xwljj
    targetEndpoint: ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:20:48Z"
      message: 'load-balancer-api-external: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.792513ms
      message: 'load-balancer-api-external: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 6.13003ms
      message: 'load-balancer-api-external: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 5.478231ms
      message: 'load-balancer-api-external: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 6.46429ms
      message: 'load-balancer-api-external: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 5.896131ms
      message: 'load-balancer-api-external: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 6.784645ms
      message: 'load-balancer-api-external: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 5.946582ms
      message: 'load-balancer-api-external: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 7.953833ms
      message: 'load-balancer-api-external: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 3.449737ms
      message: 'load-balancer-api-external: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:48Z"
    - latency: 6.759933ms
      message: 'load-balancer-api-external: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:14:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-33.ec2.internal
      uid: 085ae624-ef84-4bcb-a474-a6e004815e71
    resourceVersion: "29034"
    uid: 1bc8380e-3b6a-4e59-b789-4def2431ace7
  spec:
    sourcePod: network-check-source-56d84b9f44-xwljj
    targetEndpoint: ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:20:48Z"
      message: 'load-balancer-api-internal: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.847875ms
      message: 'load-balancer-api-internal: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 6.063472ms
      message: 'load-balancer-api-internal: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 5.345305ms
      message: 'load-balancer-api-internal: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 6.571884ms
      message: 'load-balancer-api-internal: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 6.523628ms
      message: 'load-balancer-api-internal: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 6.852933ms
      message: 'load-balancer-api-internal: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 5.960426ms
      message: 'load-balancer-api-internal: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 7.849974ms
      message: 'load-balancer-api-internal: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 4.246909ms
      message: 'load-balancer-api-internal: tcp connection to ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:48Z"
    - latency: 6.833505ms
      message: 'load-balancer-api-internal: resolved host name ae44667f1c6854e61a4d58522ab10b4a-23b093c980491257.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:14:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-33-to-network-check-target-ip-10-0-130-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-33.ec2.internal
      uid: 085ae624-ef84-4bcb-a474-a6e004815e71
    resourceVersion: "30577"
    uid: 8bbf1096-72ca-40cd-a91e-ac07cb3d781d
  spec:
    sourcePod: network-check-source-56d84b9f44-xwljj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:21:48Z"
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.850166ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:28:48Z"
    - latency: 1.448614ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:48Z"
    - latency: 1.691379ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 1.911635ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 1.665202ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 1.733081ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 1.611724ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:48Z"
    - latency: 1.970014ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:48Z"
    - latency: 1.995755ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:20:48Z"
    - latency: 2.071583ms
      message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:19:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:14:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-33-to-network-check-target-ip-10-0-131-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-33.ec2.internal
      uid: 085ae624-ef84-4bcb-a474-a6e004815e71
    resourceVersion: "30575"
    uid: f6f6670a-f9da-4a2b-9ea2-84b9fc8b6e36
  spec:
    sourcePod: network-check-source-56d84b9f44-xwljj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:21:48Z"
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.150401ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:28:48Z"
    - latency: 694.898µs
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:48Z"
    - latency: 831.964µs
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 810.665µs
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 859.547µs
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 867.568µs
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 919.693µs
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:48Z"
    - latency: 875.919µs
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:48Z"
    - latency: 1.025682ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:20:48Z"
    - latency: 1.610987ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:19:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:14:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-33-to-network-check-target-ip-10-0-136-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-33.ec2.internal
      uid: 085ae624-ef84-4bcb-a474-a6e004815e71
    resourceVersion: "30576"
    uid: 72b394c6-0b11-4744-889a-8ee9951c06fc
  spec:
    sourcePod: network-check-source-56d84b9f44-xwljj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:21:48Z"
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.262873ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:28:48Z"
    - latency: 2.172295ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:48Z"
    - latency: 2.120865ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 2.151433ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 2.305826ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 1.96731ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 2.190023ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:48Z"
    - latency: 2.364224ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:48Z"
    - latency: 2.11196ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:20:48Z"
    - latency: 2.117614ms
      message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:19:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:14:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-33.ec2.internal
      uid: 085ae624-ef84-4bcb-a474-a6e004815e71
    resourceVersion: "29033"
    uid: 3d3a9915-1b1f-40fa-b0a6-3b8e691414d6
  spec:
    sourcePod: network-check-source-56d84b9f44-xwljj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:20:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 1.679283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:26:48Z"
    - latency: 759.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 1.571516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:25:48Z"
    - latency: 936.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 1.698596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:24:48Z"
    - latency: 910.548µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 1.723672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:23:48Z"
    - latency: 971.515µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:48Z"
    - latency: 1.699304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:22:48Z"
kind: List
metadata:
  resourceVersion: ""