apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-0.us-west-1.compute.internal
      uid: 39ac1b9c-37ba-42d3-b01c-fc09c6366fe9
    resourceVersion: "30209"
    uid: b41b9fa7-a43a-4316-b57d-8c0c3468516a
  spec:
    sourcePod: network-check-source-6f78d59f99-bhng4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:59:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.655µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:06:21Z"
    - latency: 1.044695ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:05:21Z"
    - latency: 1.055938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:04:21Z"
    - latency: 5.290709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:03:21Z"
    - latency: 2.349338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:02:21Z"
    - latency: 1.718449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:01:21Z"
    - latency: 997.353µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:00:21Z"
    - latency: 1.088515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:59:21Z"
    - latency: 799.004µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:58:21Z"
    - latency: 1.062368ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-0.us-west-1.compute.internal
      uid: 39ac1b9c-37ba-42d3-b01c-fc09c6366fe9
    resourceVersion: "38363"
    uid: 435eef3a-bd1c-42db-93ae-2513b4c87f76
  spec:
    sourcePod: network-check-source-6f78d59f99-bhng4
    targetEndpoint: ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:58:21Z"
      message: 'load-balancer-api-external: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.677317ms
      message: 'load-balancer-api-external: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:10:21Z"
    - latency: 6.759167ms
      message: 'load-balancer-api-external: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:10:21Z"
    - latency: 55.190142ms
      message: 'load-balancer-api-external: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:09:21Z"
    - latency: 7.401465ms
      message: 'load-balancer-api-external: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:09:21Z"
    - latency: 56.416709ms
      message: 'load-balancer-api-external: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:08:21Z"
    - latency: 7.917099ms
      message: 'load-balancer-api-external: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:08:21Z"
    - latency: 58.714608ms
      message: 'load-balancer-api-external: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:07:21Z"
    - latency: 6.369853ms
      message: 'load-balancer-api-external: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:07:21Z"
    - latency: 56.142359ms
      message: 'load-balancer-api-external: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:06:21Z"
    - latency: 6.459428ms
      message: 'load-balancer-api-external: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:06:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-0.us-west-1.compute.internal
      uid: 39ac1b9c-37ba-42d3-b01c-fc09c6366fe9
    resourceVersion: "38364"
    uid: 73971e2f-17c9-475b-8021-5a46470ad147
  spec:
    sourcePod: network-check-source-6f78d59f99-bhng4
    targetEndpoint: ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:58:21Z"
      message: 'load-balancer-api-internal: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 57.870796ms
      message: 'load-balancer-api-internal: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:10:21Z"
    - latency: 6.59559ms
      message: 'load-balancer-api-internal: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:10:21Z"
    - latency: 55.219468ms
      message: 'load-balancer-api-internal: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:09:21Z"
    - latency: 7.302304ms
      message: 'load-balancer-api-internal: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:09:21Z"
    - latency: 57.294556ms
      message: 'load-balancer-api-internal: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:08:21Z"
    - latency: 7.981898ms
      message: 'load-balancer-api-internal: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:08:21Z"
    - latency: 58.676731ms
      message: 'load-balancer-api-internal: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:07:21Z"
    - latency: 6.396046ms
      message: 'load-balancer-api-internal: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:07:21Z"
    - latency: 56.164747ms
      message: 'load-balancer-api-internal: tcp connection to ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:06:21Z"
    - latency: 6.404503ms
      message: 'load-balancer-api-internal: resolved host name ad99878772f894bf595fb87a43495684-6faf233d34787b2e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:06:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-0-to-network-check-target-ip-10-0-133-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-0.us-west-1.compute.internal
      uid: 39ac1b9c-37ba-42d3-b01c-fc09c6366fe9
    resourceVersion: "30200"
    uid: 1d12ba5d-9e87-4543-92df-6e7f68f0f348
  spec:
    sourcePod: network-check-source-6f78d59f99-bhng4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:59:21Z"
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 791.192µs
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:06:21Z"
    - latency: 1.37437ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:05:21Z"
    - latency: 843.726µs
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:04:21Z"
    - latency: 5.683997ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:03:21Z"
    - latency: 1.170738ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:02:21Z"
    - latency: 1.438036ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:01:21Z"
    - latency: 960.839µs
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:00:21Z"
    - latency: 885.542µs
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:59:21Z"
    - latency: 1.239611ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:58:21Z"
    - latency: 951.212µs
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-0-to-network-check-target-ip-10-0-134-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-0.us-west-1.compute.internal
      uid: 39ac1b9c-37ba-42d3-b01c-fc09c6366fe9
    resourceVersion: "30204"
    uid: c097e3bf-96b8-471c-afd8-64f72206562d
  spec:
    sourcePod: network-check-source-6f78d59f99-bhng4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:59:21Z"
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.213312ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:06:21Z"
    - latency: 2.160732ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:05:21Z"
    - latency: 2.312332ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:04:21Z"
    - latency: 5.955568ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:03:21Z"
    - latency: 3.727367ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:02:21Z"
    - latency: 2.699956ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:01:21Z"
    - latency: 2.572921ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:00:21Z"
    - latency: 2.307495ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:59:21Z"
    - latency: 2.327857ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:58:21Z"
    - latency: 2.912708ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-0-to-network-check-target-ip-10-0-143-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-0.us-west-1.compute.internal
      uid: 39ac1b9c-37ba-42d3-b01c-fc09c6366fe9
    resourceVersion: "30201"
    uid: 62ee555d-66e1-460d-a81b-efd844d99b27
  spec:
    sourcePod: network-check-source-6f78d59f99-bhng4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:59:21Z"
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.035151ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:06:21Z"
    - latency: 2.55856ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:05:21Z"
    - latency: 2.088852ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:04:21Z"
    - latency: 4.03194ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:03:21Z"
    - latency: 3.02821ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:02:21Z"
    - latency: 2.423213ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:01:21Z"
    - latency: 2.055722ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:00:21Z"
    - latency: 2.284836ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:59:21Z"
    - latency: 2.069634ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:58:21Z"
    - latency: 2.085327ms
      message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-0.us-west-1.compute.internal
      uid: 39ac1b9c-37ba-42d3-b01c-fc09c6366fe9
    resourceVersion: "38359"
    uid: c87a2072-4918-4751-9312-0b9d1890ebe8
  spec:
    sourcePod: network-check-source-6f78d59f99-bhng4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:58:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.327µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:10:21Z"
    - latency: 1.88382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:10:21Z"
    - latency: 1.212673ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:09:21Z"
    - latency: 2.137966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:09:21Z"
    - latency: 1.444955ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:08:21Z"
    - latency: 1.828468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:08:21Z"
    - latency: 826.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:07:21Z"
    - latency: 1.691148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:07:21Z"
    - latency: 1.356666ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T06:06:21Z"
    - latency: 1.725961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T06:06:21Z"
kind: List
metadata:
  resourceVersion: ""