apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-133.ec2.internal
      uid: 2ba11d15-5f49-40df-9069-4a4caca94e52
    resourceVersion: "53577"
    uid: 96592961-d124-47a8-a9a5-afa2a53a720d
  spec:
    sourcePod: network-check-source-989f8b8dc-pqb49
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:46:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.213µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 1.206739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 908.05µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 930.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:02Z"
    - latency: 1.432995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:02Z"
    - latency: 985.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:02Z"
    - latency: 1.082714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:02Z"
    - latency: 1.140514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:02Z"
    - latency: 1.267556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:02Z"
    - latency: 880.466µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-133.ec2.internal
      uid: 2ba11d15-5f49-40df-9069-4a4caca94e52
    resourceVersion: "54660"
    uid: 45ed12e2-76af-4cc8-88d6-f3113c2005f9
  spec:
    sourcePod: network-check-source-989f8b8dc-pqb49
    targetEndpoint: aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:45:02Z"
      message: 'load-balancer-api-external: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.707691ms
      message: 'load-balancer-api-external: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:15:02Z"
    - latency: 11.157238ms
      message: 'load-balancer-api-external: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:15:02Z"
    - latency: 5.681013ms
      message: 'load-balancer-api-external: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 8.796118ms
      message: 'load-balancer-api-external: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 3.687778ms
      message: 'load-balancer-api-external: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 8.231177ms
      message: 'load-balancer-api-external: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 5.825494ms
      message: 'load-balancer-api-external: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 9.258265ms
      message: 'load-balancer-api-external: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 5.650726ms
      message: 'load-balancer-api-external: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:02Z"
    - latency: 6.989014ms
      message: 'load-balancer-api-external: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:11:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-133.ec2.internal
      uid: 2ba11d15-5f49-40df-9069-4a4caca94e52
    resourceVersion: "54661"
    uid: 8999fd6d-3368-42e7-a3ec-a32daf76a494
  spec:
    sourcePod: network-check-source-989f8b8dc-pqb49
    targetEndpoint: aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:45:02Z"
      message: 'load-balancer-api-internal: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.547932ms
      message: 'load-balancer-api-internal: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:15:02Z"
    - latency: 11.10391ms
      message: 'load-balancer-api-internal: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:15:02Z"
    - latency: 5.630201ms
      message: 'load-balancer-api-internal: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 8.759147ms
      message: 'load-balancer-api-internal: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 4.434028ms
      message: 'load-balancer-api-internal: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 8.139727ms
      message: 'load-balancer-api-internal: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 5.85852ms
      message: 'load-balancer-api-internal: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 9.237679ms
      message: 'load-balancer-api-internal: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 5.618849ms
      message: 'load-balancer-api-internal: tcp connection to aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:02Z"
    - latency: 6.925048ms
      message: 'load-balancer-api-internal: resolved host name aef7aa2fdea2c467f9fc66858afa18d2-dc0ed5d6fc4c571c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:11:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-139-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-133.ec2.internal
      uid: 2ba11d15-5f49-40df-9069-4a4caca94e52
    resourceVersion: "53574"
    uid: 24283d08-019d-4cbf-8825-f2ec50b5fb49
  spec:
    sourcePod: network-check-source-989f8b8dc-pqb49
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:46:02Z"
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.351314ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 1.34131ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 1.024062ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 902.088µs
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:02Z"
    - latency: 1.385434ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:02Z"
    - latency: 952.479µs
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:02Z"
    - latency: 1.603638ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:02Z"
    - latency: 1.467597ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:02Z"
    - latency: 882.48µs
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:02Z"
    - latency: 877.048µs
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-139-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-133.ec2.internal
      uid: 2ba11d15-5f49-40df-9069-4a4caca94e52
    resourceVersion: "53575"
    uid: b21d4bd4-56fe-4779-914a-3337321e9eaa
  spec:
    sourcePod: network-check-source-989f8b8dc-pqb49
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:46:02Z"
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.430554ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 2.341246ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 2.333201ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 2.333028ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:02Z"
    - latency: 2.557398ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:02Z"
    - latency: 1.942429ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:02Z"
    - latency: 2.547157ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:02Z"
    - latency: 2.410474ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:02Z"
    - latency: 2.420186ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:02Z"
    - latency: 2.466517ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-140-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-133.ec2.internal
      uid: 2ba11d15-5f49-40df-9069-4a4caca94e52
    resourceVersion: "53576"
    uid: f8fa99aa-aa87-4584-88ab-c76306b15211
  spec:
    sourcePod: network-check-source-989f8b8dc-pqb49
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:46:02Z"
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.435987ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 2.40027ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 2.369757ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 2.23556ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:02Z"
    - latency: 2.486567ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:02Z"
    - latency: 2.155176ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:02Z"
    - latency: 1.995514ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:02Z"
    - latency: 3.013671ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:02Z"
    - latency: 2.235086ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:02Z"
    - latency: 2.137483ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-133.ec2.internal
      uid: 2ba11d15-5f49-40df-9069-4a4caca94e52
    resourceVersion: "54658"
    uid: 9e78e546-1099-4f4b-81d3-b39ef7b9b6d1
  spec:
    sourcePod: network-check-source-989f8b8dc-pqb49
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:45:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:15:02Z"
    - latency: 2.604245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:15:02Z"
    - latency: 830.978µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 1.797241ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:14:02Z"
    - latency: 913.306µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 1.849222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:13:02Z"
    - latency: 855.244µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 1.947769ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:12:02Z"
    - latency: 1.212148ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:02Z"
    - latency: 1.701213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:11:02Z"
kind: List
metadata:
  resourceVersion: ""