apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:42:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-43.ec2.internal
      uid: 09e7bdc8-51d9-4b31-95b8-ddc3b4e9dea0
    resourceVersion: "55264"
    uid: 71cb5da8-d4f3-4b09-a4e3-1c807be1c0bc
  spec:
    sourcePod: network-check-source-685456655f-59g52
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:49:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.292104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 1.211047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 1.083615ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:08:09Z"
    - latency: 1.000049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:07:09Z"
    - latency: 1.210959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:06:09Z"
    - latency: 1.825549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:05:09Z"
    - latency: 1.443664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:04:09Z"
    - latency: 1.444496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:03:09Z"
    - latency: 1.710018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:02:09Z"
    - latency: 1.239931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:42:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-43.ec2.internal
      uid: 09e7bdc8-51d9-4b31-95b8-ddc3b4e9dea0
    resourceVersion: "56734"
    uid: 43b32857-d73e-45ee-a3be-bf70ac8f466f
  spec:
    sourcePod: network-check-source-685456655f-59g52
    targetEndpoint: a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:48:09Z"
      message: 'load-balancer-api-external: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.545486ms
      message: 'load-balancer-api-external: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:12:09Z"
    - latency: 9.698513ms
      message: 'load-balancer-api-external: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:12:09Z"
    - latency: 5.923532ms
      message: 'load-balancer-api-external: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:11:09Z"
    - latency: 7.906622ms
      message: 'load-balancer-api-external: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:11:09Z"
    - latency: 4.888882ms
      message: 'load-balancer-api-external: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 11.8945ms
      message: 'load-balancer-api-external: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 5.040408ms
      message: 'load-balancer-api-external: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 8.813145ms
      message: 'load-balancer-api-external: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 5.355952ms
      message: 'load-balancer-api-external: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:08:09Z"
    - latency: 7.180244ms
      message: 'load-balancer-api-external: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:08:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:42:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-43.ec2.internal
      uid: 09e7bdc8-51d9-4b31-95b8-ddc3b4e9dea0
    resourceVersion: "56735"
    uid: 129eaf86-2c75-4584-a3a6-3965fd83b6a7
  spec:
    sourcePod: network-check-source-685456655f-59g52
    targetEndpoint: a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:48:09Z"
      message: 'load-balancer-api-internal: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.695987ms
      message: 'load-balancer-api-internal: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:12:09Z"
    - latency: 9.597488ms
      message: 'load-balancer-api-internal: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:12:09Z"
    - latency: 6.010831ms
      message: 'load-balancer-api-internal: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:11:09Z"
    - latency: 7.809522ms
      message: 'load-balancer-api-internal: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:11:09Z"
    - latency: 5.278052ms
      message: 'load-balancer-api-internal: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 11.865333ms
      message: 'load-balancer-api-internal: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 5.068149ms
      message: 'load-balancer-api-internal: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 8.838997ms
      message: 'load-balancer-api-internal: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 5.278967ms
      message: 'load-balancer-api-internal: tcp connection to a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:08:09Z"
    - latency: 7.21451ms
      message: 'load-balancer-api-internal: resolved host name a41b9e7aa50dd42ce8a9ab3f4ff2113e-0d6fa2aa303a5abd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:08:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:42:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-43-to-network-check-target-ip-10-0-132-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-43.ec2.internal
      uid: 09e7bdc8-51d9-4b31-95b8-ddc3b4e9dea0
    resourceVersion: "55261"
    uid: c3f0ca47-f6b6-4d0d-b265-f1c6fb57fc9f
  spec:
    sourcePod: network-check-source-685456655f-59g52
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:49:09Z"
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.024µs
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 1.051039ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 1.637826ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:08:09Z"
    - latency: 1.120721ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:07:09Z"
    - latency: 1.017619ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:06:09Z"
    - latency: 998.728µs
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:05:09Z"
    - latency: 1.942554ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:04:09Z"
    - latency: 1.156067ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:03:09Z"
    - latency: 895.81µs
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:02:09Z"
    - latency: 985.919µs
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:42:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-43-to-network-check-target-ip-10-0-134-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-43.ec2.internal
      uid: 09e7bdc8-51d9-4b31-95b8-ddc3b4e9dea0
    resourceVersion: "55263"
    uid: a049a6e6-e19c-465f-b0ec-ba5649c8e4f2
  spec:
    sourcePod: network-check-source-685456655f-59g52
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:49:09Z"
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.20731ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 2.216166ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 2.399139ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:08:09Z"
    - latency: 2.338257ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:07:09Z"
    - latency: 2.808742ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:06:09Z"
    - latency: 2.289279ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:05:09Z"
    - latency: 2.544785ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:04:09Z"
    - latency: 2.772512ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:03:09Z"
    - latency: 2.519839ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:02:09Z"
    - latency: 2.495743ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:42:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-43-to-network-check-target-ip-10-0-140-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-43.ec2.internal
      uid: 09e7bdc8-51d9-4b31-95b8-ddc3b4e9dea0
    resourceVersion: "55262"
    uid: 12ecafd8-a748-471a-9446-b9b367d2761c
  spec:
    sourcePod: network-check-source-685456655f-59g52
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:49:09Z"
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.1415ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 1.888278ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 2.309267ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:08:09Z"
    - latency: 2.178292ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:07:09Z"
    - latency: 2.354686ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:06:09Z"
    - latency: 2.385439ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:05:09Z"
    - latency: 2.187813ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:04:09Z"
    - latency: 2.292197ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:03:09Z"
    - latency: 1.984496ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:02:09Z"
    - latency: 2.235326ms
      message: 'network-check-target-ip-10-0-140-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:42:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-43.ec2.internal
      uid: 09e7bdc8-51d9-4b31-95b8-ddc3b4e9dea0
    resourceVersion: "56733"
    uid: 4b171961-5d75-44b6-b167-7833c4141cd5
  spec:
    sourcePod: network-check-source-685456655f-59g52
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:48:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.776µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:12:09Z"
    - latency: 2.108629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:12:09Z"
    - latency: 857.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:11:09Z"
    - latency: 1.812737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:11:09Z"
    - latency: 982.176µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 2.223071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:10:09Z"
    - latency: 1.043737ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 1.850356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:09:09Z"
    - latency: 952.882µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T19:08:09Z"
    - latency: 1.684467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T19:08:09Z"
kind: List
metadata:
  resourceVersion: ""