apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:04:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-212-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-212.ec2.internal
      uid: e35346d2-34c6-45de-b1d7-e4b1243e6939
    resourceVersion: "54388"
    uid: 37ce434f-5c62-40e4-b673-074f253d3505
  spec:
    sourcePod: network-check-source-685456655f-s5rlp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:11:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.111673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 1.02714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 1.070688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:18Z"
    - latency: 1.056543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:18Z"
    - latency: 1.168311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:18Z"
    - latency: 1.207083ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:18Z"
    - latency: 1.065524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:18Z"
    - latency: 1.613635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:18Z"
    - latency: 1.150407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:18Z"
    - latency: 1.034782ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:04:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-212-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-212.ec2.internal
      uid: e35346d2-34c6-45de-b1d7-e4b1243e6939
    resourceVersion: "55924"
    uid: a5de0084-bfc6-4553-8e8e-9a0748e940ae
  spec:
    sourcePod: network-check-source-685456655f-s5rlp
    targetEndpoint: a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:10:18Z"
      message: 'load-balancer-api-external: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.408731ms
      message: 'load-balancer-api-external: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:18Z"
    - latency: 14.338846ms
      message: 'load-balancer-api-external: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:18Z"
    - latency: 5.093562ms
      message: 'load-balancer-api-external: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:18Z"
    - latency: 7.146285ms
      message: 'load-balancer-api-external: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:18Z"
    - latency: 4.052311ms
      message: 'load-balancer-api-external: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 7.995705ms
      message: 'load-balancer-api-external: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 4.248264ms
      message: 'load-balancer-api-external: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 9.884711ms
      message: 'load-balancer-api-external: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 4.942524ms
      message: 'load-balancer-api-external: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:18Z"
    - latency: 6.664493ms
      message: 'load-balancer-api-external: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:30:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:04:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-212-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-212.ec2.internal
      uid: e35346d2-34c6-45de-b1d7-e4b1243e6939
    resourceVersion: "55923"
    uid: a90abc3c-c302-4202-878a-443f70e39de9
  spec:
    sourcePod: network-check-source-685456655f-s5rlp
    targetEndpoint: a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:10:18Z"
      message: 'load-balancer-api-internal: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.474482ms
      message: 'load-balancer-api-internal: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:18Z"
    - latency: 14.290163ms
      message: 'load-balancer-api-internal: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:18Z"
    - latency: 5.239855ms
      message: 'load-balancer-api-internal: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:18Z"
    - latency: 7.105158ms
      message: 'load-balancer-api-internal: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:18Z"
    - latency: 4.504912ms
      message: 'load-balancer-api-internal: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 7.91376ms
      message: 'load-balancer-api-internal: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 3.962662ms
      message: 'load-balancer-api-internal: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 9.819869ms
      message: 'load-balancer-api-internal: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 4.949089ms
      message: 'load-balancer-api-internal: tcp connection to a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:18Z"
    - latency: 6.58237ms
      message: 'load-balancer-api-internal: resolved host name a125b6b86e64b4f0fabe67240e517827-22966073bf9299cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:30:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:04:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-212-to-network-check-target-ip-10-0-128-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-212.ec2.internal
      uid: e35346d2-34c6-45de-b1d7-e4b1243e6939
    resourceVersion: "54385"
    uid: 9442b655-b57f-4b2f-a254-6cfb786efd2b
  spec:
    sourcePod: network-check-source-685456655f-s5rlp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:11:18Z"
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.12µs
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 1.357987ms
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 1.23489ms
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:18Z"
    - latency: 976.752µs
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:18Z"
    - latency: 949.609µs
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:18Z"
    - latency: 1.441599ms
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:18Z"
    - latency: 836.181µs
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:18Z"
    - latency: 903.888µs
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:18Z"
    - latency: 908.351µs
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:18Z"
    - latency: 1.172571ms
      message: 'network-check-target-ip-10-0-128-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:04:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-212-to-network-check-target-ip-10-0-132-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-212.ec2.internal
      uid: e35346d2-34c6-45de-b1d7-e4b1243e6939
    resourceVersion: "54387"
    uid: d8095711-618e-439d-850a-8ffd441fc50e
  spec:
    sourcePod: network-check-source-685456655f-s5rlp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:11:18Z"
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.437256ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 2.228858ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 2.681729ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:18Z"
    - latency: 2.86754ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:18Z"
    - latency: 2.133142ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:18Z"
    - latency: 3.173038ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:18Z"
    - latency: 2.612723ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:18Z"
    - latency: 2.385632ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:18Z"
    - latency: 2.52132ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:18Z"
    - latency: 2.453437ms
      message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:04:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-212-to-network-check-target-ip-10-0-134-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-212.ec2.internal
      uid: e35346d2-34c6-45de-b1d7-e4b1243e6939
    resourceVersion: "54386"
    uid: 17d727ec-59f6-4448-aa18-294d49e9a6c2
  spec:
    sourcePod: network-check-source-685456655f-s5rlp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:11:18Z"
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.294876ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 2.332589ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 2.097164ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:18Z"
    - latency: 2.709485ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:18Z"
    - latency: 2.074325ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:18Z"
    - latency: 3.054272ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:18Z"
    - latency: 2.015186ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:18Z"
    - latency: 2.143652ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:18Z"
    - latency: 1.892395ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:18Z"
    - latency: 2.240114ms
      message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:04:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-212-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-212.ec2.internal
      uid: e35346d2-34c6-45de-b1d7-e4b1243e6939
    resourceVersion: "55922"
    uid: b90379b4-de36-44fa-bada-2123f9ccfb88
  spec:
    sourcePod: network-check-source-685456655f-s5rlp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:10:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.16µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:18Z"
    - latency: 1.591207ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:18Z"
    - latency: 955.505µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:18Z"
    - latency: 1.894003ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:18Z"
    - latency: 1.12061ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 1.917898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:18Z"
    - latency: 817.9µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 2.048089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:18Z"
    - latency: 1.032148ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:18Z"
    - latency: 1.643507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:30:18Z"
kind: List
metadata:
  resourceVersion: ""