apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-129-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-129.ec2.internal
      uid: b172cb30-9188-415d-a022-99383ad58ecc
    resourceVersion: "59012"
    uid: 3ee4c033-c5db-42a7-8c5c-c848e647047b
  spec:
    sourcePod: network-check-source-6f8b768455-z556l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:50: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.432613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 1.307621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 1.134207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:09:32Z"
    - latency: 1.141233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:08:32Z"
    - latency: 887.744µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:07:32Z"
    - latency: 1.310768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:06:32Z"
    - latency: 1.223409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:05:32Z"
    - latency: 937.256µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:04:32Z"
    - latency: 977.823µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:03:32Z"
    - latency: 2.021827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-129-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-129.ec2.internal
      uid: b172cb30-9188-415d-a022-99383ad58ecc
    resourceVersion: "60636"
    uid: 2a0d089d-66f4-4ad9-a6b5-1a146eb5794c
  spec:
    sourcePod: network-check-source-6f8b768455-z556l
    targetEndpoint: a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:49:32Z"
      message: 'load-balancer-api-external: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.471138ms
      message: 'load-balancer-api-external: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:13:32Z"
    - latency: 12.724024ms
      message: 'load-balancer-api-external: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:13:32Z"
    - latency: 4.789408ms
      message: 'load-balancer-api-external: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:12:32Z"
    - latency: 7.550684ms
      message: 'load-balancer-api-external: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:12:32Z"
    - latency: 4.777068ms
      message: 'load-balancer-api-external: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 10.041407ms
      message: 'load-balancer-api-external: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 4.598606ms
      message: 'load-balancer-api-external: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 6.515657ms
      message: 'load-balancer-api-external: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 3.787859ms
      message: 'load-balancer-api-external: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:09:32Z"
    - latency: 7.533605ms
      message: 'load-balancer-api-external: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:09:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-129-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-129.ec2.internal
      uid: b172cb30-9188-415d-a022-99383ad58ecc
    resourceVersion: "60637"
    uid: d8d1da6d-8436-4eab-9b5a-ab1f40bdbf7f
  spec:
    sourcePod: network-check-source-6f8b768455-z556l
    targetEndpoint: a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:49:32Z"
      message: 'load-balancer-api-internal: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.27256ms
      message: 'load-balancer-api-internal: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:13:32Z"
    - latency: 12.637413ms
      message: 'load-balancer-api-internal: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:13:32Z"
    - latency: 4.761432ms
      message: 'load-balancer-api-internal: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:12:32Z"
    - latency: 7.470766ms
      message: 'load-balancer-api-internal: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:12:32Z"
    - latency: 4.223531ms
      message: 'load-balancer-api-internal: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 9.308828ms
      message: 'load-balancer-api-internal: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 4.671294ms
      message: 'load-balancer-api-internal: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 6.496695ms
      message: 'load-balancer-api-internal: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 3.780193ms
      message: 'load-balancer-api-internal: tcp connection to a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:09:32Z"
    - latency: 7.285263ms
      message: 'load-balancer-api-internal: resolved host name a2cadcbd59f134d9b93fc00d25a9f060-ff5baa553188b8bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:09:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-129-to-network-check-target-ip-10-0-138-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-129.ec2.internal
      uid: b172cb30-9188-415d-a022-99383ad58ecc
    resourceVersion: "59011"
    uid: f6af60e8-17f7-4045-936a-74762b1c6955
  spec:
    sourcePod: network-check-source-6f8b768455-z556l
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:50:32Z"
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.356983ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 2.14615ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 2.564625ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:09:32Z"
    - latency: 2.367577ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:08:32Z"
    - latency: 2.313469ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:07:32Z"
    - latency: 2.338086ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:06:32Z"
    - latency: 2.456494ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:05:32Z"
    - latency: 2.171744ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:04:32Z"
    - latency: 2.33228ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:03:32Z"
    - latency: 2.316515ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-129-to-network-check-target-ip-10-0-139-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-129.ec2.internal
      uid: b172cb30-9188-415d-a022-99383ad58ecc
    resourceVersion: "59010"
    uid: be07d6cc-a27a-4bfa-970f-81b6b389476e
  spec:
    sourcePod: network-check-source-6f8b768455-z556l
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:50:32Z"
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.306822ms
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 916.148µs
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 1.096498ms
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:09:32Z"
    - latency: 909.466µs
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:08:32Z"
    - latency: 1.079562ms
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:07:32Z"
    - latency: 1.148121ms
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:06:32Z"
    - latency: 1.081958ms
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:05:32Z"
    - latency: 887.487µs
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:04:32Z"
    - latency: 1.183431ms
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:03:32Z"
    - latency: 2.872404ms
      message: 'network-check-target-ip-10-0-139-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-129-to-network-check-target-ip-10-0-141-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-129.ec2.internal
      uid: b172cb30-9188-415d-a022-99383ad58ecc
    resourceVersion: "59009"
    uid: cbf1be98-f2f3-4fc4-afa2-5e124a92d151
  spec:
    sourcePod: network-check-source-6f8b768455-z556l
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:50:32Z"
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.95064ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 2.227001ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 2.177993ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:09:32Z"
    - latency: 2.162367ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:08:32Z"
    - latency: 1.85442ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:07:32Z"
    - latency: 1.966019ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:06:32Z"
    - latency: 1.937651ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:05:32Z"
    - latency: 1.646961ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:04:32Z"
    - latency: 1.91054ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:03:32Z"
    - latency: 2.502158ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-129-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-129.ec2.internal
      uid: b172cb30-9188-415d-a022-99383ad58ecc
    resourceVersion: "60635"
    uid: a00a78f6-8933-4877-8146-b05d198d49be
  spec:
    sourcePod: network-check-source-6f8b768455-z556l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:49:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016958ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:13:32Z"
    - latency: 1.724053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:13:32Z"
    - latency: 1.098714ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:12:32Z"
    - latency: 1.707651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:12:32Z"
    - latency: 1.182811ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 1.813707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:11:32Z"
    - latency: 943.685µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 1.75755ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:10:32Z"
    - latency: 900.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:09:32Z"
    - latency: 1.727298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:09:32Z"
kind: List
metadata:
  resourceVersion: ""