apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:36:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-52.ec2.internal
      uid: d5e697a2-3089-4cc6-b148-0d9ddbf4ee4c
    resourceVersion: "63380"
    uid: 771b724a-01a9-4ca5-840a-a3f98a88018c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2ktbg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:43: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.028362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 1.111001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 1.306499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 960.454µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 880.858µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:14:59Z"
    - latency: 1.075976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:13:59Z"
    - latency: 1.001162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:12:59Z"
    - latency: 841.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:11:59Z"
    - latency: 1.18795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:10:59Z"
    - latency: 930.643µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:36:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-52.ec2.internal
      uid: d5e697a2-3089-4cc6-b148-0d9ddbf4ee4c
    resourceVersion: "63382"
    uid: 162cbeec-13cd-4f8b-95be-34ed1050fc9b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2ktbg
    targetEndpoint: a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:42:59Z"
      message: 'load-balancer-api-external: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.367718ms
      message: 'load-balancer-api-external: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 12.078803ms
      message: 'load-balancer-api-external: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 5.19259ms
      message: 'load-balancer-api-external: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 8.039012ms
      message: 'load-balancer-api-external: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 5.415077ms
      message: 'load-balancer-api-external: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 9.914184ms
      message: 'load-balancer-api-external: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 4.956611ms
      message: 'load-balancer-api-external: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 8.01097ms
      message: 'load-balancer-api-external: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 6.097282ms
      message: 'load-balancer-api-external: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:14:59Z"
    - latency: 9.51422ms
      message: 'load-balancer-api-external: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:36:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-52.ec2.internal
      uid: d5e697a2-3089-4cc6-b148-0d9ddbf4ee4c
    resourceVersion: "63381"
    uid: 089a5586-0bee-495b-843a-3720b965703a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2ktbg
    targetEndpoint: a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:42:59Z"
      message: 'load-balancer-api-internal: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.927956ms
      message: 'load-balancer-api-internal: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 12.219976ms
      message: 'load-balancer-api-internal: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 3.963702ms
      message: 'load-balancer-api-internal: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 7.999716ms
      message: 'load-balancer-api-internal: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 4.06035ms
      message: 'load-balancer-api-internal: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 9.969658ms
      message: 'load-balancer-api-internal: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 5.044005ms
      message: 'load-balancer-api-internal: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 7.97992ms
      message: 'load-balancer-api-internal: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 3.913382ms
      message: 'load-balancer-api-internal: tcp connection to a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:14:59Z"
    - latency: 9.445926ms
      message: 'load-balancer-api-internal: resolved host name a240ead4e781942d6ab4f69a78da2d6c-fd8f7d54a632629b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:36:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-52-to-network-check-target-ip-10-0-132-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-52.ec2.internal
      uid: d5e697a2-3089-4cc6-b148-0d9ddbf4ee4c
    resourceVersion: "63377"
    uid: cd65fd38-ee83-4e95-8d84-4767ca2c9296
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2ktbg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:43:59Z"
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.389145ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 1.983119ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 1.872717ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 1.998164ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 2.028467ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:14:59Z"
    - latency: 1.985939ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:13:59Z"
    - latency: 1.954077ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:12:59Z"
    - latency: 2.311285ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:11:59Z"
    - latency: 1.692875ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:10:59Z"
    - latency: 1.912482ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:36:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-52-to-network-check-target-ip-10-0-139-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-52.ec2.internal
      uid: d5e697a2-3089-4cc6-b148-0d9ddbf4ee4c
    resourceVersion: "63376"
    uid: fdf024d5-ee98-424b-9f05-3c21e05ad2cf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2ktbg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:43:59Z"
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.338729ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 1.388983ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 720.162µs
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 879.112µs
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 896.682µs
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:14:59Z"
    - latency: 879.529µs
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:13:59Z"
    - latency: 927.735µs
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:12:59Z"
    - latency: 1.484247ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:11:59Z"
    - latency: 1.303191ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:10:59Z"
    - latency: 745.558µs
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:36:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-52-to-network-check-target-ip-10-0-142-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-52.ec2.internal
      uid: d5e697a2-3089-4cc6-b148-0d9ddbf4ee4c
    resourceVersion: "63378"
    uid: 8833395a-86c3-4d59-920c-3c066bcffc39
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2ktbg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:43:59Z"
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.434125ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 2.387806ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 2.152923ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 1.765868ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 1.999916ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:14:59Z"
    - latency: 2.039658ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:13:59Z"
    - latency: 1.896247ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:12:59Z"
    - latency: 2.255405ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:11:59Z"
    - latency: 1.863116ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:10:59Z"
    - latency: 1.897317ms
      message: 'network-check-target-ip-10-0-142-88: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:36:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-52.ec2.internal
      uid: d5e697a2-3089-4cc6-b148-0d9ddbf4ee4c
    resourceVersion: "63379"
    uid: be0a3361-7c80-4588-8a6a-3ab3a97624ef
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2ktbg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:42:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035101ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 1.715829ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:18:59Z"
    - latency: 810.338µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 1.761249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:17:59Z"
    - latency: 766.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 1.466858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:16:59Z"
    - latency: 726.402µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 1.542734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:15:59Z"
    - latency: 1.64639ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T04:14:59Z"
    - latency: 1.656181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T04:14:59Z"
kind: List
metadata:
  resourceVersion: ""