apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: 9ded2214-47ed-46ea-b8ab-70d261f5f8eb
    resourceVersion: "80495"
    uid: b6942ec5-a4c1-41bf-815d-8d4613fce1e1
  spec:
    sourcePod: network-check-source-6f8b768455-zvt9g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.247734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 1.200238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:45:00Z"
    - latency: 1.051222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:44:00Z"
    - latency: 1.339319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:43:00Z"
    - latency: 1.262719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:42:00Z"
    - latency: 1.381956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:41:00Z"
    - latency: 1.082603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:40:00Z"
    - latency: 1.486319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:39:00Z"
    - latency: 1.258573ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:00Z"
    - latency: 1.325466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: 9ded2214-47ed-46ea-b8ab-70d261f5f8eb
    resourceVersion: "83679"
    uid: 253bc017-e473-4741-867d-d124258fa1bb
  spec:
    sourcePod: network-check-source-6f8b768455-zvt9g
    targetEndpoint: a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:49:00Z"
      message: 'load-balancer-api-external: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.946153ms
      message: 'load-balancer-api-external: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:49:00Z"
    - latency: 7.322247ms
      message: 'load-balancer-api-external: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:49:00Z"
    - latency: 5.668304ms
      message: 'load-balancer-api-external: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:48:00Z"
    - latency: 9.118718ms
      message: 'load-balancer-api-external: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:48:00Z"
    - latency: 5.437455ms
      message: 'load-balancer-api-external: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:47:00Z"
    - latency: 6.24111ms
      message: 'load-balancer-api-external: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:47:00Z"
    - latency: 4.374196ms
      message: 'load-balancer-api-external: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 9.885022ms
      message: 'load-balancer-api-external: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 5.581616ms
      message: 'load-balancer-api-external: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:45:00Z"
    - latency: 6.295575ms
      message: 'load-balancer-api-external: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:45:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: 9ded2214-47ed-46ea-b8ab-70d261f5f8eb
    resourceVersion: "83680"
    uid: 433008e1-f89a-4ff1-b495-ea9410f9f8ec
  spec:
    sourcePod: network-check-source-6f8b768455-zvt9g
    targetEndpoint: a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:49:00Z"
      message: 'load-balancer-api-internal: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.866459ms
      message: 'load-balancer-api-internal: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:49:00Z"
    - latency: 7.361223ms
      message: 'load-balancer-api-internal: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:49:00Z"
    - latency: 5.693029ms
      message: 'load-balancer-api-internal: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:48:00Z"
    - latency: 9.176093ms
      message: 'load-balancer-api-internal: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:48:00Z"
    - latency: 6.103896ms
      message: 'load-balancer-api-internal: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:47:00Z"
    - latency: 6.285016ms
      message: 'load-balancer-api-internal: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:47:00Z"
    - latency: 4.364598ms
      message: 'load-balancer-api-internal: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 9.926885ms
      message: 'load-balancer-api-internal: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 8.38927ms
      message: 'load-balancer-api-internal: tcp connection to a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:45:00Z"
    - latency: 6.330723ms
      message: 'load-balancer-api-internal: resolved host name a91933527056244ba964875ed59a1d49-70351e234d543d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:45:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-130-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: 9ded2214-47ed-46ea-b8ab-70d261f5f8eb
    resourceVersion: "80492"
    uid: be28d233-6fa3-418f-b1d0-c2f5e2e1d7e1
  spec:
    sourcePod: network-check-source-6f8b768455-zvt9g
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:00Z"
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02749ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 1.062884ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:45:00Z"
    - latency: 1.011301ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:44:00Z"
    - latency: 1.31264ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:43:00Z"
    - latency: 1.534716ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:42:00Z"
    - latency: 1.411906ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:41:00Z"
    - latency: 1.080279ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:40:00Z"
    - latency: 1.725261ms
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:39:00Z"
    - latency: 950.75µs
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:00Z"
    - latency: 983.031µs
      message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-142-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: 9ded2214-47ed-46ea-b8ab-70d261f5f8eb
    resourceVersion: "80493"
    uid: 78457129-0c21-469a-9284-ddd8b651984b
  spec:
    sourcePod: network-check-source-6f8b768455-zvt9g
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:00Z"
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.287115ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 2.076025ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:45:00Z"
    - latency: 2.160446ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:44:00Z"
    - latency: 2.969053ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:43:00Z"
    - latency: 2.302572ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:42:00Z"
    - latency: 2.455189ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:41:00Z"
    - latency: 2.403647ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:40:00Z"
    - latency: 2.434748ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:39:00Z"
    - latency: 2.379769ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:00Z"
    - latency: 2.146208ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-143-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: 9ded2214-47ed-46ea-b8ab-70d261f5f8eb
    resourceVersion: "80494"
    uid: deb340fe-b901-4cb4-b26d-8f2ceb2dfc92
  spec:
    sourcePod: network-check-source-6f8b768455-zvt9g
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:00Z"
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.511687ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 2.624715ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:45:00Z"
    - latency: 2.176094ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:44:00Z"
    - latency: 2.447403ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:43:00Z"
    - latency: 2.248562ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:42:00Z"
    - latency: 2.925008ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:41:00Z"
    - latency: 2.209088ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:40:00Z"
    - latency: 2.226728ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:39:00Z"
    - latency: 2.439416ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:00Z"
    - latency: 2.393252ms
      message: 'network-check-target-ip-10-0-143-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: 9ded2214-47ed-46ea-b8ab-70d261f5f8eb
    resourceVersion: "83678"
    uid: c3065c62-0e3e-44cf-b841-4806056da38a
  spec:
    sourcePod: network-check-source-6f8b768455-zvt9g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:49:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.184695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:49:00Z"
    - latency: 2.399597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:49:00Z"
    - latency: 1.210549ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:48:00Z"
    - latency: 2.648089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:48:00Z"
    - latency: 1.131329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:47:00Z"
    - latency: 2.039597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:47:00Z"
    - latency: 1.033812ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 2.088526ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:46:00Z"
    - latency: 877.587µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:45:00Z"
    - latency: 1.921976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:45:00Z"
kind: List
metadata:
  resourceVersion: ""