apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 40a897e7-b256-4a1f-b4ef-cb7c0c1bfa45
    resourceVersion: "53711"
    uid: 1671f299-618b-4060-aefe-dbb7a1d533ba
  spec:
    sourcePod: network-check-source-989f8b8dc-mf7qg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:33:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 1.058175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 1.101953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 986.775µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 1.152311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:56Z"
    - latency: 1.044104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:56Z"
    - latency: 1.109023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:56Z"
    - latency: 1.079127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:56Z"
    - latency: 1.173498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:56Z"
    - latency: 1.188896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 40a897e7-b256-4a1f-b4ef-cb7c0c1bfa45
    resourceVersion: "53712"
    uid: 7eb88de8-8cfe-4f08-9ee0-90f5199b8b74
  spec:
    sourcePod: network-check-source-989f8b8dc-mf7qg
    targetEndpoint: a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:32:56Z"
      message: 'load-balancer-api-external: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.113192ms
      message: 'load-balancer-api-external: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 7.436244ms
      message: 'load-balancer-api-external: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 4.731046ms
      message: 'load-balancer-api-external: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 8.313622ms
      message: 'load-balancer-api-external: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 4.578851ms
      message: 'load-balancer-api-external: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 7.214239ms
      message: 'load-balancer-api-external: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 4.322711ms
      message: 'load-balancer-api-external: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 6.750248ms
      message: 'load-balancer-api-external: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 5.060527ms
      message: 'load-balancer-api-external: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:56Z"
    - latency: 8.818733ms
      message: 'load-balancer-api-external: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 40a897e7-b256-4a1f-b4ef-cb7c0c1bfa45
    resourceVersion: "53713"
    uid: ff1a06bf-61d4-464e-a684-1da82d26e949
  spec:
    sourcePod: network-check-source-989f8b8dc-mf7qg
    targetEndpoint: a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:32:56Z"
      message: 'load-balancer-api-internal: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.021642ms
      message: 'load-balancer-api-internal: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 7.484872ms
      message: 'load-balancer-api-internal: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 5.133483ms
      message: 'load-balancer-api-internal: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 8.254551ms
      message: 'load-balancer-api-internal: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 6.691075ms
      message: 'load-balancer-api-internal: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 7.17984ms
      message: 'load-balancer-api-internal: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 3.816497ms
      message: 'load-balancer-api-internal: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 6.703206ms
      message: 'load-balancer-api-internal: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 5.404ms
      message: 'load-balancer-api-internal: tcp connection to a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:56Z"
    - latency: 8.783271ms
      message: 'load-balancer-api-internal: resolved host name a7094b167326a4c82a83b6b901f5856c-474eb07a5e9b8c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-ip-10-0-135-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 40a897e7-b256-4a1f-b4ef-cb7c0c1bfa45
    resourceVersion: "53708"
    uid: f323eb47-7dd8-4b95-8574-13e6a56ae1bd
  spec:
    sourcePod: network-check-source-989f8b8dc-mf7qg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:33:56Z"
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.713942ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 1.865954ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 2.004649ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 2.023674ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 1.739355ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:56Z"
    - latency: 1.929544ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:56Z"
    - latency: 1.647626ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:56Z"
    - latency: 1.487836ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:56Z"
    - latency: 1.719123ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:56Z"
    - latency: 1.992948ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-ip-10-0-140-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 40a897e7-b256-4a1f-b4ef-cb7c0c1bfa45
    resourceVersion: "53709"
    uid: 04fdc7fe-4e5e-4102-8231-a4e96d97c091
  spec:
    sourcePod: network-check-source-989f8b8dc-mf7qg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:33:56Z"
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.197476ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 1.982531ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 2.440934ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 2.127534ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 2.107639ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:56Z"
    - latency: 2.236396ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:56Z"
    - latency: 2.268604ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:56Z"
    - latency: 2.258565ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:56Z"
    - latency: 2.228776ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:56Z"
    - latency: 2.426734ms
      message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-ip-10-0-140-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 40a897e7-b256-4a1f-b4ef-cb7c0c1bfa45
    resourceVersion: "53707"
    uid: ac3d19cf-0301-4390-ac12-8b65da747429
  spec:
    sourcePod: network-check-source-989f8b8dc-mf7qg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:33:56Z"
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.547µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 836.605µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 941.915µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 1.134788ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 963.654µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:56Z"
    - latency: 1.493499ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:56Z"
    - latency: 1.098043ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:56Z"
    - latency: 876.18µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:56Z"
    - latency: 882.086µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:56Z"
    - latency: 1.009953ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:26:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 40a897e7-b256-4a1f-b4ef-cb7c0c1bfa45
    resourceVersion: "53710"
    uid: 36749720-9c4a-4514-a484-b7add4b38573
  spec:
    sourcePod: network-check-source-989f8b8dc-mf7qg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:32:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.663µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 1.717613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:56Z"
    - latency: 899.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 1.78014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:56Z"
    - latency: 965.566µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 1.890056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:56Z"
    - latency: 1.240121ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 1.731768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:56Z"
    - latency: 839.047µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:56Z"
    - latency: 1.905086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:56Z"
kind: List
metadata:
  resourceVersion: ""