apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:23:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: 0a1df55f-7889-4d50-b047-f8bee6289d74
    resourceVersion: "93409"
    uid: 0cbbb172-dd2e-4738-add3-a00f699cf158
  spec:
    sourcePod: network-check-source-685456655f-ckvsw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:30:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.193865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:33:36Z"
    - latency: 915.431µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:36Z"
    - latency: 946.619µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:36Z"
    - latency: 1.268007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:36Z"
    - latency: 1.967341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 1.290092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 1.446487ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 1.158611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 999.352µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:25:36Z"
    - latency: 1.129896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:24:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:23:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: 0a1df55f-7889-4d50-b047-f8bee6289d74
    resourceVersion: "89415"
    uid: 2e44d176-b1d4-4e3d-ba32-7e395e4bcffb
  spec:
    sourcePod: network-check-source-685456655f-ckvsw
    targetEndpoint: ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:36Z"
      message: 'load-balancer-api-external: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.742536ms
      message: 'load-balancer-api-external: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 9.170781ms
      message: 'load-balancer-api-external: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 5.45173ms
      message: 'load-balancer-api-external: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 6.878188ms
      message: 'load-balancer-api-external: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 6.667488ms
      message: 'load-balancer-api-external: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 17.207269ms
      message: 'load-balancer-api-external: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 5.59877ms
      message: 'load-balancer-api-external: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 8.687775ms
      message: 'load-balancer-api-external: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 4.977598ms
      message: 'load-balancer-api-external: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:25:36Z"
    - latency: 7.616508ms
      message: 'load-balancer-api-external: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:25:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:23:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: 0a1df55f-7889-4d50-b047-f8bee6289d74
    resourceVersion: "89414"
    uid: eab2416e-dd95-4a87-9e37-0010d4656c9a
  spec:
    sourcePod: network-check-source-685456655f-ckvsw
    targetEndpoint: ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:36Z"
      message: 'load-balancer-api-internal: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.623522ms
      message: 'load-balancer-api-internal: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 8.898847ms
      message: 'load-balancer-api-internal: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 5.520328ms
      message: 'load-balancer-api-internal: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 6.860299ms
      message: 'load-balancer-api-internal: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 7.676834ms
      message: 'load-balancer-api-internal: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 16.422147ms
      message: 'load-balancer-api-internal: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 5.499733ms
      message: 'load-balancer-api-internal: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 8.655506ms
      message: 'load-balancer-api-internal: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 4.840139ms
      message: 'load-balancer-api-internal: tcp connection to ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:25:36Z"
    - latency: 7.591392ms
      message: 'load-balancer-api-internal: resolved host name ac54a81ce5e154c3eaba27582b75d4bf-4891c65bf78eef47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:25:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:23:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-ip-10-0-140-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: 0a1df55f-7889-4d50-b047-f8bee6289d74
    resourceVersion: "93407"
    uid: 293bc019-df65-4f5c-bbf6-c4964d3194a2
  spec:
    sourcePod: network-check-source-685456655f-ckvsw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:30:36Z"
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304151ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:33:36Z"
    - latency: 2.200362ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:36Z"
    - latency: 2.222334ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:36Z"
    - latency: 2.369505ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:36Z"
    - latency: 3.074379ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 2.04365ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 3.347449ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 2.230034ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 2.323517ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:25:36Z"
    - latency: 2.532803ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:24:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:23:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-ip-10-0-143-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: 0a1df55f-7889-4d50-b047-f8bee6289d74
    resourceVersion: "93406"
    uid: 8c22789b-5232-4d36-96c9-7c191542a848
  spec:
    sourcePod: network-check-source-685456655f-ckvsw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:30:36Z"
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.193877ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:33:36Z"
    - latency: 1.367002ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:36Z"
    - latency: 1.488916ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:36Z"
    - latency: 1.046826ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:36Z"
    - latency: 2.304232ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 1.040343ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 1.963684ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 1.390146ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 1.041453ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:25:36Z"
    - latency: 994.028µs
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:24:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:23:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-ip-10-0-143-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: 0a1df55f-7889-4d50-b047-f8bee6289d74
    resourceVersion: "93408"
    uid: ddbb2116-a1dc-469b-8c80-d13777aac878
  spec:
    sourcePod: network-check-source-685456655f-ckvsw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:30:36Z"
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.264259ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:33:36Z"
    - latency: 2.180287ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:36Z"
    - latency: 2.443309ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:36Z"
    - latency: 1.999851ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:36Z"
    - latency: 2.760754ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 2.111398ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 2.457575ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 2.513467ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 2.118543ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:25:36Z"
    - latency: 2.458229ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:24:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:23:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: 0a1df55f-7889-4d50-b047-f8bee6289d74
    resourceVersion: "89413"
    uid: bfda8cae-7a4e-48d5-b827-3d773dc01069
  spec:
    sourcePod: network-check-source-685456655f-ckvsw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.01368ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 3.163155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:29:36Z"
    - latency: 1.209044ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 1.99504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:28:36Z"
    - latency: 2.080077ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 2.126274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:27:36Z"
    - latency: 1.004179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 2.056506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:26:36Z"
    - latency: 957.833µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:25:36Z"
    - latency: 1.980134ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:25:36Z"
kind: List
metadata:
  resourceVersion: ""