apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:45:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-18-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-18.ec2.internal
      uid: e764f7c9-1161-412d-a37d-6080d053ca95
    resourceVersion: "62345"
    uid: 7697d572-6226-4c20-a34c-b60e0468ccb1
  spec:
    sourcePod: network-check-source-6f8b768455-ltc72
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:52:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13765ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 1.179859ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 991.835µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:11:10Z"
    - latency: 1.061141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:10:10Z"
    - latency: 1.14324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:09:10Z"
    - latency: 1.13732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:08:10Z"
    - latency: 2.49493ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:07:10Z"
    - latency: 1.116661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:06:10Z"
    - latency: 1.164809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:05:10Z"
    - latency: 961.771µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:04:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:45:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-18-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-18.ec2.internal
      uid: e764f7c9-1161-412d-a37d-6080d053ca95
    resourceVersion: "64115"
    uid: 6b0ccbb2-4016-4c6e-9b77-b79e98946d57
  spec:
    sourcePod: network-check-source-6f8b768455-ltc72
    targetEndpoint: a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:51:10Z"
      message: 'load-balancer-api-external: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.431331ms
      message: 'load-balancer-api-external: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:15:10Z"
    - latency: 9.547917ms
      message: 'load-balancer-api-external: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:15:10Z"
    - latency: 5.388244ms
      message: 'load-balancer-api-external: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:14:10Z"
    - latency: 9.896554ms
      message: 'load-balancer-api-external: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:14:10Z"
    - latency: 5.080863ms
      message: 'load-balancer-api-external: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 9.111645ms
      message: 'load-balancer-api-external: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 5.129261ms
      message: 'load-balancer-api-external: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 8.280859ms
      message: 'load-balancer-api-external: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 5.707033ms
      message: 'load-balancer-api-external: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:11:10Z"
    - latency: 8.751035ms
      message: 'load-balancer-api-external: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:11:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:45:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-18-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-18.ec2.internal
      uid: e764f7c9-1161-412d-a37d-6080d053ca95
    resourceVersion: "64114"
    uid: 1b902508-4bf1-46f0-9b0e-d9728c78a422
  spec:
    sourcePod: network-check-source-6f8b768455-ltc72
    targetEndpoint: a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:51:10Z"
      message: 'load-balancer-api-internal: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.995955ms
      message: 'load-balancer-api-internal: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:15:10Z"
    - latency: 9.514101ms
      message: 'load-balancer-api-internal: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:15:10Z"
    - latency: 5.409156ms
      message: 'load-balancer-api-internal: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:14:10Z"
    - latency: 9.978824ms
      message: 'load-balancer-api-internal: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:14:10Z"
    - latency: 5.075715ms
      message: 'load-balancer-api-internal: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 9.078238ms
      message: 'load-balancer-api-internal: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 5.136071ms
      message: 'load-balancer-api-internal: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 8.229512ms
      message: 'load-balancer-api-internal: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 5.763953ms
      message: 'load-balancer-api-internal: tcp connection to a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:11:10Z"
    - latency: 8.792568ms
      message: 'load-balancer-api-internal: resolved host name a50085952d3164f7a80487634b1cdff9-21ebd9ee9f144f38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:11:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:45:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-18-to-network-check-target-ip-10-0-142-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-18.ec2.internal
      uid: e764f7c9-1161-412d-a37d-6080d053ca95
    resourceVersion: "62342"
    uid: 777b764c-e4a9-4c1b-b712-e8110bdbb7d4
  spec:
    sourcePod: network-check-source-6f8b768455-ltc72
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:52:10Z"
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.647µs
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 957.656µs
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 1.037886ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:11:10Z"
    - latency: 900.723µs
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:10:10Z"
    - latency: 1.004165ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:09:10Z"
    - latency: 1.032813ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:08:10Z"
    - latency: 1.153107ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:07:10Z"
    - latency: 1.807627ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:06:10Z"
    - latency: 1.405591ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:05:10Z"
    - latency: 1.896175ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:04:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:45:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-18-to-network-check-target-ip-10-0-143-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-18.ec2.internal
      uid: e764f7c9-1161-412d-a37d-6080d053ca95
    resourceVersion: "62344"
    uid: 2ecd995f-108e-4233-a952-26191de2dae5
  spec:
    sourcePod: network-check-source-6f8b768455-ltc72
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:52:10Z"
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.258712ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 2.556113ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 2.472446ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:11:10Z"
    - latency: 2.577974ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:10:10Z"
    - latency: 2.203338ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:09:10Z"
    - latency: 2.640273ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:08:10Z"
    - latency: 3.527356ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:07:10Z"
    - latency: 3.111123ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:06:10Z"
    - latency: 2.739301ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:05:10Z"
    - latency: 2.159392ms
      message: 'network-check-target-ip-10-0-143-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:04:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:45:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-18-to-network-check-target-ip-10-0-143-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-18.ec2.internal
      uid: e764f7c9-1161-412d-a37d-6080d053ca95
    resourceVersion: "62343"
    uid: 1017a851-c015-4328-be52-9a961bb057c2
  spec:
    sourcePod: network-check-source-6f8b768455-ltc72
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:52:10Z"
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.620133ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 2.54188ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 2.083319ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:11:10Z"
    - latency: 3.301702ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:10:10Z"
    - latency: 2.598282ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:09:10Z"
    - latency: 2.501647ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:08:10Z"
    - latency: 4.245639ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:07:10Z"
    - latency: 2.79289ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:06:10Z"
    - latency: 2.787423ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:05:10Z"
    - latency: 2.263697ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:04:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:45:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-18-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-18.ec2.internal
      uid: e764f7c9-1161-412d-a37d-6080d053ca95
    resourceVersion: "64113"
    uid: 2da4bcd2-3144-4518-893f-f7d05238665e
  spec:
    sourcePod: network-check-source-6f8b768455-ltc72
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:51:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.141244ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:15:10Z"
    - latency: 1.70561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:15:10Z"
    - latency: 802.305µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:14:10Z"
    - latency: 2.701227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:14:10Z"
    - latency: 977.878µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 2.004304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:13:10Z"
    - latency: 1.2927ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 1.82586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:12:10Z"
    - latency: 870.474µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:11:10Z"
    - latency: 1.745044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:11:10Z"
kind: List
metadata:
  resourceVersion: ""