apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: f364df65-5f3c-42bd-8040-d7681bb608df
    resourceVersion: "56946"
    uid: cec60f07-17ad-4e03-910d-54b58ea04b8a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-27nmz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:49:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 1.439603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 1.131672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 1.095472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:14:59Z"
    - latency: 848.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:13:59Z"
    - latency: 1.33531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:12:59Z"
    - latency: 1.185522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:11:59Z"
    - latency: 1.042109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:10:59Z"
    - latency: 1.675236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:09:59Z"
    - latency: 1.071385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:08:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: f364df65-5f3c-42bd-8040-d7681bb608df
    resourceVersion: "58013"
    uid: 82dbfe32-2c74-4135-b80d-50c8485be4ed
  spec:
    sourcePod: network-check-source-7bc5b6bf85-27nmz
    targetEndpoint: a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:48:59Z"
      message: 'load-balancer-api-external: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.269592ms
      message: 'load-balancer-api-external: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:18:59Z"
    - latency: 8.631514ms
      message: 'load-balancer-api-external: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:18:59Z"
    - latency: 5.020624ms
      message: 'load-balancer-api-external: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 9.433125ms
      message: 'load-balancer-api-external: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 4.021545ms
      message: 'load-balancer-api-external: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 12.729059ms
      message: 'load-balancer-api-external: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 4.207486ms
      message: 'load-balancer-api-external: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 8.533107ms
      message: 'load-balancer-api-external: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 5.241375ms
      message: 'load-balancer-api-external: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:14:59Z"
    - latency: 8.321612ms
      message: 'load-balancer-api-external: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: f364df65-5f3c-42bd-8040-d7681bb608df
    resourceVersion: "58014"
    uid: d651227b-45c6-411b-9122-c914e1fff78f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-27nmz
    targetEndpoint: a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:48:59Z"
      message: 'load-balancer-api-internal: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.306703ms
      message: 'load-balancer-api-internal: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:18:59Z"
    - latency: 8.568148ms
      message: 'load-balancer-api-internal: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:18:59Z"
    - latency: 5.017728ms
      message: 'load-balancer-api-internal: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 9.337011ms
      message: 'load-balancer-api-internal: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 4.920069ms
      message: 'load-balancer-api-internal: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 12.664966ms
      message: 'load-balancer-api-internal: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 4.5946ms
      message: 'load-balancer-api-internal: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 8.557198ms
      message: 'load-balancer-api-internal: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 6.090852ms
      message: 'load-balancer-api-internal: tcp connection to a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:14:59Z"
    - latency: 8.279272ms
      message: 'load-balancer-api-internal: resolved host name a14505cdf048b402491c236f79417a54-43629ff85df97a3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-ip-10-0-136-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: f364df65-5f3c-42bd-8040-d7681bb608df
    resourceVersion: "56945"
    uid: ce374c80-b352-409f-9609-9af5d9dd7e0f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-27nmz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:49:59Z"
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.391762ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 2.090838ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 2.762254ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 1.989424ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:14:59Z"
    - latency: 2.080261ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:13:59Z"
    - latency: 1.85002ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:12:59Z"
    - latency: 1.985777ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:11:59Z"
    - latency: 1.886183ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:10:59Z"
    - latency: 2.52877ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:09:59Z"
    - latency: 1.982572ms
      message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:08:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-ip-10-0-138-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: f364df65-5f3c-42bd-8040-d7681bb608df
    resourceVersion: "56944"
    uid: d31ba2ac-ef89-4506-a00f-31d32cb22f8f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-27nmz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:49:59Z"
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.395626ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 2.230786ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 2.684201ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 1.971381ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:14:59Z"
    - latency: 2.097821ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:13:59Z"
    - latency: 2.121306ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:12:59Z"
    - latency: 2.084976ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:11:59Z"
    - latency: 2.138523ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:10:59Z"
    - latency: 2.890291ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:09:59Z"
    - latency: 2.020654ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:08:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-ip-10-0-140-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: f364df65-5f3c-42bd-8040-d7681bb608df
    resourceVersion: "56943"
    uid: 23362c8d-640c-4f46-8022-1b2b7bf6574e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-27nmz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:49:59Z"
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.214568ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 1.107201ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 1.068096ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 963.867µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:14:59Z"
    - latency: 1.559594ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:13:59Z"
    - latency: 1.286144ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:12:59Z"
    - latency: 875.348µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:11:59Z"
    - latency: 944.801µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:10:59Z"
    - latency: 1.173787ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:09:59Z"
    - latency: 1.12691ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:08:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: f364df65-5f3c-42bd-8040-d7681bb608df
    resourceVersion: "58011"
    uid: 923c70b9-6570-4390-a7a6-a43ae266932e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-27nmz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:48:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.07788ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:18:59Z"
    - latency: 1.928604ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:18:59Z"
    - latency: 901.173µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 2.453256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:17:59Z"
    - latency: 866.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 1.869993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:16:59Z"
    - latency: 941.732µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 2.767556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:15:59Z"
    - latency: 891.563µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:14:59Z"
    - latency: 2.244493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:14:59Z"
kind: List
metadata:
  resourceVersion: ""