apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:49:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-96-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-96.ec2.internal
      uid: 00c67227-2b91-44c0-b0c7-f437a5318078
    resourceVersion: "52918"
    uid: 692186c4-5dfc-44f9-905b-4aab6bee9bc0
  spec:
    sourcePod: network-check-source-6f8b768455-d85tk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:56:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 974.919µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 947.747µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 1.389038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:15:03Z"
    - latency: 1.360694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:14:03Z"
    - latency: 1.517175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:13:03Z"
    - latency: 1.22087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:12:03Z"
    - latency: 1.053836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:11:03Z"
    - latency: 1.51278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:10:03Z"
    - latency: 1.159501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:09:03Z"
    - latency: 1.206431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:08:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:49:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-96-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-96.ec2.internal
      uid: 00c67227-2b91-44c0-b0c7-f437a5318078
    resourceVersion: "54487"
    uid: b9f451ab-e961-45ce-abaf-3b8309b01d45
  spec:
    sourcePod: network-check-source-6f8b768455-d85tk
    targetEndpoint: abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:55:03Z"
      message: 'load-balancer-api-external: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.018587ms
      message: 'load-balancer-api-external: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:19:03Z"
    - latency: 6.385144ms
      message: 'load-balancer-api-external: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:19:03Z"
    - latency: 3.860049ms
      message: 'load-balancer-api-external: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:18:03Z"
    - latency: 6.712926ms
      message: 'load-balancer-api-external: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:18:03Z"
    - latency: 5.19098ms
      message: 'load-balancer-api-external: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 6.486288ms
      message: 'load-balancer-api-external: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 4.225922ms
      message: 'load-balancer-api-external: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 7.01395ms
      message: 'load-balancer-api-external: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 4.758759ms
      message: 'load-balancer-api-external: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:15:03Z"
    - latency: 6.928324ms
      message: 'load-balancer-api-external: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:15:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:49:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-96-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-96.ec2.internal
      uid: 00c67227-2b91-44c0-b0c7-f437a5318078
    resourceVersion: "54488"
    uid: 8c4601c0-e110-4b79-a54f-036ac1d53265
  spec:
    sourcePod: network-check-source-6f8b768455-d85tk
    targetEndpoint: abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:55:03Z"
      message: 'load-balancer-api-internal: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.267199ms
      message: 'load-balancer-api-internal: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:19:03Z"
    - latency: 6.433533ms
      message: 'load-balancer-api-internal: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:19:03Z"
    - latency: 3.847875ms
      message: 'load-balancer-api-internal: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:18:03Z"
    - latency: 6.746544ms
      message: 'load-balancer-api-internal: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:18:03Z"
    - latency: 5.183828ms
      message: 'load-balancer-api-internal: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 6.585573ms
      message: 'load-balancer-api-internal: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 4.220495ms
      message: 'load-balancer-api-internal: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 7.088003ms
      message: 'load-balancer-api-internal: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 6.075876ms
      message: 'load-balancer-api-internal: tcp connection to abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:15:03Z"
    - latency: 6.897255ms
      message: 'load-balancer-api-internal: resolved host name abc94ddfdfc35412b9a77d6bdb656be3-7bc1da958dede9d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:15:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:49:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-96-to-network-check-target-ip-10-0-138-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-96.ec2.internal
      uid: 00c67227-2b91-44c0-b0c7-f437a5318078
    resourceVersion: "52915"
    uid: 23c046c5-16f4-4005-9d06-7ae59e8b2f04
  spec:
    sourcePod: network-check-source-6f8b768455-d85tk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:56:03Z"
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018137ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 1.463254ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 1.256945ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:15:03Z"
    - latency: 1.786413ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:14:03Z"
    - latency: 1.462776ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:13:03Z"
    - latency: 943.16µs
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:12:03Z"
    - latency: 1.008376ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:11:03Z"
    - latency: 1.240759ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:10:03Z"
    - latency: 1.049903ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:09:03Z"
    - latency: 1.42215ms
      message: 'network-check-target-ip-10-0-138-96: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:08:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:49:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-96-to-network-check-target-ip-10-0-140-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-96.ec2.internal
      uid: 00c67227-2b91-44c0-b0c7-f437a5318078
    resourceVersion: "52916"
    uid: 41cfeab1-897d-4be4-ac7c-84777fef00d6
  spec:
    sourcePod: network-check-source-6f8b768455-d85tk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:56:03Z"
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.41563ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 2.136123ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 2.134473ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:15:03Z"
    - latency: 2.723968ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:14:03Z"
    - latency: 2.320303ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:13:03Z"
    - latency: 2.789506ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:12:03Z"
    - latency: 2.22729ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:11:03Z"
    - latency: 2.696842ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:10:03Z"
    - latency: 2.530846ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:09:03Z"
    - latency: 2.250533ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:08:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:49:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-96-to-network-check-target-ip-10-0-140-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-96.ec2.internal
      uid: 00c67227-2b91-44c0-b0c7-f437a5318078
    resourceVersion: "52917"
    uid: 7958c826-87ca-4951-abbc-15df19a6242c
  spec:
    sourcePod: network-check-source-6f8b768455-d85tk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:56:03Z"
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.452082ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 2.483093ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 2.604918ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:15:03Z"
    - latency: 2.772749ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:14:03Z"
    - latency: 2.58297ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:13:03Z"
    - latency: 2.54349ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:12:03Z"
    - latency: 2.31086ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:11:03Z"
    - latency: 2.694672ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:10:03Z"
    - latency: 2.539161ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:09:03Z"
    - latency: 2.595801ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:08:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:49:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-96-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-96.ec2.internal
      uid: 00c67227-2b91-44c0-b0c7-f437a5318078
    resourceVersion: "54486"
    uid: d774c6fb-ab62-4dcf-80a1-f053657d6873
  spec:
    sourcePod: network-check-source-6f8b768455-d85tk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:55:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.30172ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:19:03Z"
    - latency: 1.989333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:19:03Z"
    - latency: 908.131µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:18:03Z"
    - latency: 1.883953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:18:03Z"
    - latency: 846.472µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 1.926584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:17:03Z"
    - latency: 914.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 1.658586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:16:03Z"
    - latency: 1.318967ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:15:03Z"
    - latency: 2.146041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:15:03Z"
kind: List
metadata:
  resourceVersion: ""