apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T13:25:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: f0eb6cd0-c47b-40a2-adbc-eb637bf1d602
    resourceVersion: "16399"
    uid: 6475affb-5fae-4c7a-8f8b-b0339d97abb8
  spec:
    sourcePod: network-check-source-7f44b6dd87-48vtl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T13:32:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 998.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:39:01Z"
    - latency: 1.056192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:38:01Z"
    - latency: 915.545µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 1.525289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 1.200723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 1.127165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 1.100456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:33:01Z"
    - latency: 1.276537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:32:01Z"
    - latency: 994.302µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:31:01Z"
    - latency: 1.023529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:30:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T13:25:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: f0eb6cd0-c47b-40a2-adbc-eb637bf1d602
    resourceVersion: "15630"
    uid: 5183d5f5-7fe3-4e26-8cc0-ac1643952a2a
  spec:
    sourcePod: network-check-source-7f44b6dd87-48vtl
    targetEndpoint: a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T13:31:01Z"
      message: 'load-balancer-api-external: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.021557ms
      message: 'load-balancer-api-external: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 6.440349ms
      message: 'load-balancer-api-external: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 4.679918ms
      message: 'load-balancer-api-external: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 6.956915ms
      message: 'load-balancer-api-external: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 6.29008ms
      message: 'load-balancer-api-external: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 6.656773ms
      message: 'load-balancer-api-external: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 5.329025ms
      message: 'load-balancer-api-external: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 6.507211ms
      message: 'load-balancer-api-external: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 6.222219ms
      message: 'load-balancer-api-external: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:33:01Z"
    - latency: 7.932284ms
      message: 'load-balancer-api-external: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:33:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T13:25:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: f0eb6cd0-c47b-40a2-adbc-eb637bf1d602
    resourceVersion: "15629"
    uid: 4992e80c-2a35-41ea-8bef-2a808758528a
  spec:
    sourcePod: network-check-source-7f44b6dd87-48vtl
    targetEndpoint: a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T13:31:01Z"
      message: 'load-balancer-api-internal: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.966175ms
      message: 'load-balancer-api-internal: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 6.362119ms
      message: 'load-balancer-api-internal: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 4.69984ms
      message: 'load-balancer-api-internal: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 7.044482ms
      message: 'load-balancer-api-internal: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 7.226073ms
      message: 'load-balancer-api-internal: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 6.631823ms
      message: 'load-balancer-api-internal: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 5.29907ms
      message: 'load-balancer-api-internal: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 6.537586ms
      message: 'load-balancer-api-internal: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 6.075806ms
      message: 'load-balancer-api-internal: tcp connection to a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:33:01Z"
    - latency: 7.989794ms
      message: 'load-balancer-api-internal: resolved host name a25e496e1f7d1499c80154c355625fc9-4b8679e620494864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:33:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T13:25:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-ip-10-0-132-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: f0eb6cd0-c47b-40a2-adbc-eb637bf1d602
    resourceVersion: "16397"
    uid: bf373048-3def-4d77-8361-ec2a41532eab
  spec:
    sourcePod: network-check-source-7f44b6dd87-48vtl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T13:32:01Z"
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.415209ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:39:01Z"
    - latency: 2.031286ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:38:01Z"
    - latency: 2.144745ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 2.258334ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 2.291469ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 2.142547ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 2.213463ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:33:01Z"
    - latency: 1.949709ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:32:01Z"
    - latency: 2.322971ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:31:01Z"
    - latency: 2.448386ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:30:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T13:25:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-ip-10-0-133-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: f0eb6cd0-c47b-40a2-adbc-eb637bf1d602
    resourceVersion: "16395"
    uid: af5e30bd-220b-45fa-88fc-c96001c60a4c
  spec:
    sourcePod: network-check-source-7f44b6dd87-48vtl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T13:32:01Z"
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.794µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:39:01Z"
    - latency: 786.437µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:38:01Z"
    - latency: 1.24034ms
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 901.615µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 926.472µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 823.394µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 872.252µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:33:01Z"
    - latency: 871.468µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:32:01Z"
    - latency: 885.838µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:31:01Z"
    - latency: 904.64µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:30:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T13:25:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-ip-10-0-139-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: f0eb6cd0-c47b-40a2-adbc-eb637bf1d602
    resourceVersion: "16398"
    uid: e46d94bd-dd66-422c-b1a2-b6bbce66da5d
  spec:
    sourcePod: network-check-source-7f44b6dd87-48vtl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T13:32:01Z"
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.975295ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:39:01Z"
    - latency: 2.249955ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:38:01Z"
    - latency: 2.328099ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 2.43253ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 2.276412ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 3.024782ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 3.16301ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:33:01Z"
    - latency: 2.389301ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:32:01Z"
    - latency: 2.150245ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:31:01Z"
    - latency: 2.288303ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:30:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T13:25:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: f0eb6cd0-c47b-40a2-adbc-eb637bf1d602
    resourceVersion: "15628"
    uid: 6096d872-6bfb-4cfc-8f7b-1c3aeccf011e
  spec:
    sourcePod: network-check-source-7f44b6dd87-48vtl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T13:31:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.385µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 1.749268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:37:01Z"
    - latency: 842.828µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 1.716054ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:36:01Z"
    - latency: 1.130893ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 1.886851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:35:01Z"
    - latency: 700.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 1.661128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:34:01Z"
    - latency: 1.11762ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T13:33:01Z"
    - latency: 1.767809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T13:33:01Z"
kind: List
metadata:
  resourceVersion: ""