apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T02:52:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-139.ec2.internal
      uid: f41144e9-0297-4772-91f6-2ab67c40b03b
    resourceVersion: "63872"
    uid: 85333c3a-bdac-4f2d-aff0-0d377bda1ecf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vxh2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T02:59:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 1.104757ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 1.317843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 1.151998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 1.066667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:30:45Z"
    - latency: 919.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:29:45Z"
    - latency: 1.014238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:28:45Z"
    - latency: 1.102346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:27:45Z"
    - latency: 1.048693ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:26:45Z"
    - latency: 1.056796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T02:52:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-139.ec2.internal
      uid: f41144e9-0297-4772-91f6-2ab67c40b03b
    resourceVersion: "63874"
    uid: 0ef5d82e-309e-4405-ae29-d49b17e7ca98
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vxh2
    targetEndpoint: ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T02:58:45Z"
      message: 'load-balancer-api-external: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.271604ms
      message: 'load-balancer-api-external: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 8.369867ms
      message: 'load-balancer-api-external: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 4.866515ms
      message: 'load-balancer-api-external: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 9.012281ms
      message: 'load-balancer-api-external: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 4.270603ms
      message: 'load-balancer-api-external: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 9.721524ms
      message: 'load-balancer-api-external: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 4.125421ms
      message: 'load-balancer-api-external: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 8.789324ms
      message: 'load-balancer-api-external: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 4.370256ms
      message: 'load-balancer-api-external: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:30:45Z"
    - latency: 8.128957ms
      message: 'load-balancer-api-external: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:30:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T02:52:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-139.ec2.internal
      uid: f41144e9-0297-4772-91f6-2ab67c40b03b
    resourceVersion: "63873"
    uid: 75d38d9f-bdd8-40f3-82eb-b891b389ea99
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vxh2
    targetEndpoint: ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T02:58:45Z"
      message: 'load-balancer-api-internal: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.705172ms
      message: 'load-balancer-api-internal: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 8.336249ms
      message: 'load-balancer-api-internal: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 4.953903ms
      message: 'load-balancer-api-internal: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 8.994021ms
      message: 'load-balancer-api-internal: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 3.599564ms
      message: 'load-balancer-api-internal: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 9.664201ms
      message: 'load-balancer-api-internal: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 3.537857ms
      message: 'load-balancer-api-internal: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 8.957405ms
      message: 'load-balancer-api-internal: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 4.765756ms
      message: 'load-balancer-api-internal: tcp connection to ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:30:45Z"
    - latency: 8.166333ms
      message: 'load-balancer-api-internal: resolved host name ab627c0a8bc0f4e1d96a2fbc676c87e3-23e80bdd1ed4fd2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:30:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T02:52:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-139-to-network-check-target-ip-10-0-134-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-139.ec2.internal
      uid: f41144e9-0297-4772-91f6-2ab67c40b03b
    resourceVersion: "63870"
    uid: e00ed90f-b1e9-4602-9230-37c643286303
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vxh2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T02:59:45Z"
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.161559ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 2.707511ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 2.652337ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 2.294862ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 2.802729ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:30:45Z"
    - latency: 2.440002ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:29:45Z"
    - latency: 2.43442ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:28:45Z"
    - latency: 2.41128ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:27:45Z"
    - latency: 2.095846ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:26:45Z"
    - latency: 2.646903ms
      message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T02:52:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-139-to-network-check-target-ip-10-0-140-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-139.ec2.internal
      uid: f41144e9-0297-4772-91f6-2ab67c40b03b
    resourceVersion: "63869"
    uid: fb26d46f-123b-4c4d-93ea-0a5578d13040
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vxh2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T02:59:45Z"
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.343087ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 2.383215ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 2.588115ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 2.249795ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 2.106952ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:30:45Z"
    - latency: 2.430867ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:29:45Z"
    - latency: 2.285336ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:28:45Z"
    - latency: 2.394327ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:27:45Z"
    - latency: 2.462197ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:26:45Z"
    - latency: 2.381323ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T02:52:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-139-to-network-check-target-ip-10-0-142-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-139.ec2.internal
      uid: f41144e9-0297-4772-91f6-2ab67c40b03b
    resourceVersion: "63868"
    uid: 5cfe11e8-cf97-4c0c-9495-a64de5401e48
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vxh2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T02:59:45Z"
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159377ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 992.484µs
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 1.761659ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 845.065µs
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 1.03966ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:30:45Z"
    - latency: 1.041079ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:29:45Z"
    - latency: 1.576653ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:28:45Z"
    - latency: 1.022461ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:27:45Z"
    - latency: 1.430011ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:26:45Z"
    - latency: 874.977µs
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:25:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T02:52:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-139.ec2.internal
      uid: f41144e9-0297-4772-91f6-2ab67c40b03b
    resourceVersion: "63871"
    uid: ffa7af79-e1b5-4f14-8eb9-b7577ddf1bd5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vxh2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T02:58:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221137ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 1.95529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:34:45Z"
    - latency: 1.102398ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 1.773041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:33:45Z"
    - latency: 848.983µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 1.737222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:32:45Z"
    - latency: 1.382588ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 1.690328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:31:45Z"
    - latency: 826.06µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T03:30:45Z"
    - latency: 1.864876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T03:30:45Z"
kind: List
metadata:
  resourceVersion: ""