apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:29:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-54-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-54.ec2.internal
      uid: fd321734-f369-4834-b7ab-779b640024a1
    resourceVersion: "67907"
    uid: 4f8c337a-a2aa-4f06-a965-2b66828fbb51
  spec:
    sourcePod: network-check-source-6f8b768455-6w6m6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:36:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.204115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 1.188064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 1.100921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 1.019052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:32Z"
    - latency: 952.843µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:32Z"
    - latency: 1.020333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:32Z"
    - latency: 995.501µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:32Z"
    - latency: 1.102613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:32Z"
    - latency: 1.550308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:32Z"
    - latency: 1.06056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:29:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-54-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-54.ec2.internal
      uid: fd321734-f369-4834-b7ab-779b640024a1
    resourceVersion: "69019"
    uid: 5399b69e-acd9-4a35-aa76-dd60ca4e142e
  spec:
    sourcePod: network-check-source-6f8b768455-6w6m6
    targetEndpoint: ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:35:32Z"
      message: 'load-balancer-api-external: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.909315ms
      message: 'load-balancer-api-external: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:32Z"
    - latency: 8.403847ms
      message: 'load-balancer-api-external: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:05:32Z"
    - latency: 4.603192ms
      message: 'load-balancer-api-external: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 8.605357ms
      message: 'load-balancer-api-external: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 4.465622ms
      message: 'load-balancer-api-external: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 8.870741ms
      message: 'load-balancer-api-external: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 5.429258ms
      message: 'load-balancer-api-external: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 8.414196ms
      message: 'load-balancer-api-external: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 7.083531ms
      message: 'load-balancer-api-external: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:32Z"
    - latency: 9.212473ms
      message: 'load-balancer-api-external: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:01:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:29:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-54-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-54.ec2.internal
      uid: fd321734-f369-4834-b7ab-779b640024a1
    resourceVersion: "69020"
    uid: cb461fed-f9e6-4d5f-82c9-a86e7fde6297
  spec:
    sourcePod: network-check-source-6f8b768455-6w6m6
    targetEndpoint: ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:35:32Z"
      message: 'load-balancer-api-internal: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.885185ms
      message: 'load-balancer-api-internal: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:32Z"
    - latency: 8.519192ms
      message: 'load-balancer-api-internal: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:05:32Z"
    - latency: 4.616141ms
      message: 'load-balancer-api-internal: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 8.649089ms
      message: 'load-balancer-api-internal: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 4.6795ms
      message: 'load-balancer-api-internal: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 8.938624ms
      message: 'load-balancer-api-internal: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 4.591765ms
      message: 'load-balancer-api-internal: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 8.501642ms
      message: 'load-balancer-api-internal: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 4.223202ms
      message: 'load-balancer-api-internal: tcp connection to ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:32Z"
    - latency: 9.299168ms
      message: 'load-balancer-api-internal: resolved host name ab3c4962cddbd44eeb23a82963e53834-a2487034536fb3ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:01:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:29:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-54-to-network-check-target-ip-10-0-131-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-54.ec2.internal
      uid: fd321734-f369-4834-b7ab-779b640024a1
    resourceVersion: "67905"
    uid: a58aa6b1-1841-4944-9109-69b90616d852
  spec:
    sourcePod: network-check-source-6f8b768455-6w6m6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:36:32Z"
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304485ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 2.501725ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 2.304192ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 2.376031ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:32Z"
    - latency: 2.379206ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:32Z"
    - latency: 2.382666ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:32Z"
    - latency: 2.499783ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:32Z"
    - latency: 2.579429ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:32Z"
    - latency: 2.476567ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:32Z"
    - latency: 2.234547ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:29:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-54-to-network-check-target-ip-10-0-139-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-54.ec2.internal
      uid: fd321734-f369-4834-b7ab-779b640024a1
    resourceVersion: "67906"
    uid: 75c6102a-61be-4c8d-acbd-699dafb1db6b
  spec:
    sourcePod: network-check-source-6f8b768455-6w6m6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:36:32Z"
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.608032ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 2.64884ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 2.311488ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 2.440179ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:32Z"
    - latency: 2.614756ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:32Z"
    - latency: 2.212799ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:32Z"
    - latency: 2.521558ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:32Z"
    - latency: 2.960067ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:32Z"
    - latency: 2.392865ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:32Z"
    - latency: 2.461164ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:29:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-54-to-network-check-target-ip-10-0-142-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-54.ec2.internal
      uid: fd321734-f369-4834-b7ab-779b640024a1
    resourceVersion: "67904"
    uid: 3065dfd3-277c-4065-93ae-f08e43779864
  spec:
    sourcePod: network-check-source-6f8b768455-6w6m6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:36:32Z"
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.663µs
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 1.033399ms
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 1.085699ms
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 939.822µs
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:32Z"
    - latency: 882.687µs
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:32Z"
    - latency: 995.695µs
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:32Z"
    - latency: 1.114662ms
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:32Z"
    - latency: 1.234167ms
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:32Z"
    - latency: 1.86226ms
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:32Z"
    - latency: 884.602µs
      message: 'network-check-target-ip-10-0-142-54: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:29:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-54-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-54.ec2.internal
      uid: fd321734-f369-4834-b7ab-779b640024a1
    resourceVersion: "69018"
    uid: 47d6dc4e-42e5-4a75-8c5f-b9c435552f82
  spec:
    sourcePod: network-check-source-6f8b768455-6w6m6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:35:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.607µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:32Z"
    - latency: 1.747566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:05:32Z"
    - latency: 1.105533ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 1.974985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:04:32Z"
    - latency: 774.139µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 1.683006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:03:32Z"
    - latency: 1.232261ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 1.900276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:02:32Z"
    - latency: 1.088594ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:32Z"
    - latency: 1.791889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:01:32Z"
kind: List
metadata:
  resourceVersion: ""