apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: dc1e0db3-b63c-4954-b019-83183d699cd2
    resourceVersion: "55962"
    uid: 6335b16e-27e2-4df2-bf2d-3da90ac90b6c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q6mzg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:13:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.598µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 1.095918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 988.657µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 1.037066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:38:57Z"
    - latency: 1.358292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:37:57Z"
    - latency: 1.321361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:36:57Z"
    - latency: 1.668666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:35:57Z"
    - latency: 1.150703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:34:57Z"
    - latency: 926.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:33:57Z"
    - latency: 923.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: dc1e0db3-b63c-4954-b019-83183d699cd2
    resourceVersion: "57280"
    uid: e47beffe-04d7-4204-a42c-249409502970
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q6mzg
    targetEndpoint: a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:12:57Z"
      message: 'load-balancer-api-external: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.741867ms
      message: 'load-balancer-api-external: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:42:57Z"
    - latency: 9.075489ms
      message: 'load-balancer-api-external: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:42:57Z"
    - latency: 5.872142ms
      message: 'load-balancer-api-external: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 8.534707ms
      message: 'load-balancer-api-external: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 4.839404ms
      message: 'load-balancer-api-external: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 8.444995ms
      message: 'load-balancer-api-external: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 4.075163ms
      message: 'load-balancer-api-external: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 8.168407ms
      message: 'load-balancer-api-external: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 3.344639ms
      message: 'load-balancer-api-external: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:38:57Z"
    - latency: 8.605323ms
      message: 'load-balancer-api-external: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:38:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: dc1e0db3-b63c-4954-b019-83183d699cd2
    resourceVersion: "57281"
    uid: 97279117-eda2-4b4f-8dd8-a248aefc2591
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q6mzg
    targetEndpoint: a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:12:57Z"
      message: 'load-balancer-api-internal: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.751111ms
      message: 'load-balancer-api-internal: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:42:57Z"
    - latency: 9.038777ms
      message: 'load-balancer-api-internal: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:42:57Z"
    - latency: 5.819965ms
      message: 'load-balancer-api-internal: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 8.438668ms
      message: 'load-balancer-api-internal: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 4.231181ms
      message: 'load-balancer-api-internal: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 8.425754ms
      message: 'load-balancer-api-internal: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 4.093024ms
      message: 'load-balancer-api-internal: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 8.104066ms
      message: 'load-balancer-api-internal: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 4.036467ms
      message: 'load-balancer-api-internal: tcp connection to a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:38:57Z"
    - latency: 8.581251ms
      message: 'load-balancer-api-internal: resolved host name a4495bf23c78e41c39b7a850f3eac79f-3100a356aed21a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:38:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-ip-10-0-131-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: dc1e0db3-b63c-4954-b019-83183d699cd2
    resourceVersion: "55960"
    uid: 0861dbfd-2b30-44c0-825d-35f396c9186c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q6mzg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:13:57Z"
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938171ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 2.20138ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 2.357948ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 2.241157ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:38:57Z"
    - latency: 2.471562ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:37:57Z"
    - latency: 2.316691ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:36:57Z"
    - latency: 2.681425ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:35:57Z"
    - latency: 2.009617ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:34:57Z"
    - latency: 2.059189ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:33:57Z"
    - latency: 2.319726ms
      message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-ip-10-0-132-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: dc1e0db3-b63c-4954-b019-83183d699cd2
    resourceVersion: "55961"
    uid: 63cc2a9f-acf0-4010-a7e1-f56a89efd7bc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q6mzg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:13:57Z"
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.38305ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 3.15565ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 2.917817ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 2.443289ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:38:57Z"
    - latency: 3.237771ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:37:57Z"
    - latency: 2.195811ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:36:57Z"
    - latency: 2.387319ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:35:57Z"
    - latency: 2.258449ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:34:57Z"
    - latency: 2.296245ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:33:57Z"
    - latency: 1.830288ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-ip-10-0-137-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: dc1e0db3-b63c-4954-b019-83183d699cd2
    resourceVersion: "55959"
    uid: 0750efdf-c34e-405d-99df-af9b3ba7d5c6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q6mzg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:13:57Z"
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.685µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 998.234µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 1.254613ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 995.247µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:38:57Z"
    - latency: 1.296124ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:37:57Z"
    - latency: 1.60475ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:36:57Z"
    - latency: 971.876µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:35:57Z"
    - latency: 920.677µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:34:57Z"
    - latency: 834.764µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:33:57Z"
    - latency: 1.013064ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:06:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: dc1e0db3-b63c-4954-b019-83183d699cd2
    resourceVersion: "57278"
    uid: f753fce3-0f95-45a3-834f-57d1cea3693c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q6mzg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:12:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001989ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:42:57Z"
    - latency: 2.182155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:42:57Z"
    - latency: 1.216109ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 1.79325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:41:57Z"
    - latency: 1.576524ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 1.726309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:40:57Z"
    - latency: 1.109557ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 1.633964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:39:57Z"
    - latency: 1.160527ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T21:38:57Z"
    - latency: 2.109102ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T21:38:57Z"
kind: List
metadata:
  resourceVersion: ""