apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T19:30:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-174-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-174.us-west-2.compute.internal
      uid: d75e73e5-1d63-4f75-827b-3471a7cf883b
    resourceVersion: "116912"
    uid: 5ac7a92f-26fb-49d2-bd6e-131d74064724
  spec:
    sourcePod: network-check-source-6f78d59f99-mz8m7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T19:37:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 1.262134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 940.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:38:17Z"
    - latency: 1.015217ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:37:17Z"
    - latency: 1.213545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:36:17Z"
    - latency: 1.224209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:35:17Z"
    - latency: 1.341372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:34:17Z"
    - latency: 2.282211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:33:17Z"
    - latency: 978.089µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:32:17Z"
    - latency: 1.048771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:31:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T19:30:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-174-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-174.us-west-2.compute.internal
      uid: d75e73e5-1d63-4f75-827b-3471a7cf883b
    resourceVersion: "117949"
    uid: 29b27987-4b09-4954-b189-8b268d0e68d1
  spec:
    sourcePod: network-check-source-6f78d59f99-mz8m7
    targetEndpoint: a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T19:36:17Z"
      message: 'load-balancer-api-external: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.669001ms
      message: 'load-balancer-api-external: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:42:17Z"
    - latency: 6.275164ms
      message: 'load-balancer-api-external: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:42:17Z"
    - latency: 49.563149ms
      message: 'load-balancer-api-external: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:41:17Z"
    - latency: 6.353559ms
      message: 'load-balancer-api-external: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:41:17Z"
    - latency: 55.574646ms
      message: 'load-balancer-api-external: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 7.879603ms
      message: 'load-balancer-api-external: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 52.298728ms
      message: 'load-balancer-api-external: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 6.955121ms
      message: 'load-balancer-api-external: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 55.490003ms
      message: 'load-balancer-api-external: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:38:17Z"
    - latency: 7.944042ms
      message: 'load-balancer-api-external: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:38:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T19:30:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-174-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-174.us-west-2.compute.internal
      uid: d75e73e5-1d63-4f75-827b-3471a7cf883b
    resourceVersion: "117948"
    uid: 85570972-eb01-4e88-88d3-3c400b4a6876
  spec:
    sourcePod: network-check-source-6f78d59f99-mz8m7
    targetEndpoint: a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T19:36:17Z"
      message: 'load-balancer-api-internal: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 49.088299ms
      message: 'load-balancer-api-internal: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:42:17Z"
    - latency: 6.322491ms
      message: 'load-balancer-api-internal: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:42:17Z"
    - latency: 49.481289ms
      message: 'load-balancer-api-internal: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:41:17Z"
    - latency: 6.405479ms
      message: 'load-balancer-api-internal: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:41:17Z"
    - latency: 50.856771ms
      message: 'load-balancer-api-internal: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 7.939399ms
      message: 'load-balancer-api-internal: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 55.471893ms
      message: 'load-balancer-api-internal: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 6.862927ms
      message: 'load-balancer-api-internal: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 55.505083ms
      message: 'load-balancer-api-internal: tcp connection to a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:38:17Z"
    - latency: 7.91417ms
      message: 'load-balancer-api-internal: resolved host name a15d747bf66324e00b1608078aae7d90-1121cf0d51ffc33d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:38:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T19:30:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-174-to-network-check-target-ip-10-0-131-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-174.us-west-2.compute.internal
      uid: d75e73e5-1d63-4f75-827b-3471a7cf883b
    resourceVersion: "116908"
    uid: 3fb2546f-941b-4435-94e5-c784959a3be8
  spec:
    sourcePod: network-check-source-6f78d59f99-mz8m7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T19:37:17Z"
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.017389ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 2.07633ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 2.402276ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:38:17Z"
    - latency: 2.227557ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:37:17Z"
    - latency: 2.466938ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:36:17Z"
    - latency: 2.755443ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:35:17Z"
    - latency: 3.397332ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:34:17Z"
    - latency: 18.885074ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:33:17Z"
    - latency: 2.607958ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:32:17Z"
    - latency: 2.854014ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:31:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T19:30:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-174-to-network-check-target-ip-10-0-132-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-174.us-west-2.compute.internal
      uid: d75e73e5-1d63-4f75-827b-3471a7cf883b
    resourceVersion: "116907"
    uid: 817d3e95-dd56-4a20-afe7-105169055b93
  spec:
    sourcePod: network-check-source-6f78d59f99-mz8m7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T19:37:17Z"
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.222451ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 940.637µs
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 1.094109ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:38:17Z"
    - latency: 796.658µs
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:37:17Z"
    - latency: 1.014541ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:36:17Z"
    - latency: 1.124467ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:35:17Z"
    - latency: 1.736492ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:34:17Z"
    - latency: 5.18532ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:33:17Z"
    - latency: 1.267161ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:32:17Z"
    - latency: 1.06932ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:31:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T19:30:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-174-to-network-check-target-ip-10-0-133-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-174.us-west-2.compute.internal
      uid: d75e73e5-1d63-4f75-827b-3471a7cf883b
    resourceVersion: "116910"
    uid: 645a5585-6ecf-4a58-bddd-31b1e542fe2a
  spec:
    sourcePod: network-check-source-6f78d59f99-mz8m7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T19:37:17Z"
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.454028ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 2.313853ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 2.280479ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:38:17Z"
    - latency: 2.215484ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:37:17Z"
    - latency: 2.65099ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:36:17Z"
    - latency: 2.349233ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:35:17Z"
    - latency: 2.496044ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:34:17Z"
    - latency: 19.066065ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:33:17Z"
    - latency: 2.487545ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:32:17Z"
    - latency: 2.40335ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:31:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T19:30:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-174-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-174.us-west-2.compute.internal
      uid: d75e73e5-1d63-4f75-827b-3471a7cf883b
    resourceVersion: "117950"
    uid: 624605cb-b7d0-4664-a16c-c704eebb451e
  spec:
    sourcePod: network-check-source-6f78d59f99-mz8m7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T19:36:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:42:17Z"
    - latency: 759.159µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:42:17Z"
    - latency: 920.349µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:41:17Z"
    - latency: 836.939µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:41:17Z"
    - latency: 1.107682ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 796.518µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:40:17Z"
    - latency: 959.098µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 774.347µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:39:17Z"
    - latency: 1.280914ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:38:17Z"
    - latency: 673.82µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:38:17Z"
kind: List
metadata:
  resourceVersion: ""