apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 72d70c1b-180f-48d9-b0c0-76dff7e55291
    resourceVersion: "48920"
    uid: 68f75f1c-3bba-461a-b4d2-b8be70ccc6ff
  spec:
    sourcePod: network-check-source-989f8b8dc-5mqkv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.123µ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:05Z"
    - latency: 1.128673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 729.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:05Z"
    - latency: 1.160453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:05Z"
    - latency: 679.854µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:05Z"
    - latency: 667.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:05Z"
    - latency: 910.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:05Z"
    - latency: 616.424µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:05Z"
    - latency: 1.073308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:05Z"
    - latency: 782.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 72d70c1b-180f-48d9-b0c0-76dff7e55291
    resourceVersion: "50318"
    uid: 23d4186e-b24f-4f9f-9f47-20c912e8c807
  spec:
    sourcePod: network-check-source-989f8b8dc-5mqkv
    targetEndpoint: ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:36:05Z"
      message: 'load-balancer-api-external: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.044424ms
      message: 'load-balancer-api-external: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:05Z"
    - latency: 8.016625ms
      message: 'load-balancer-api-external: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:05Z"
    - latency: 4.366918ms
      message: 'load-balancer-api-external: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:05Z"
    - latency: 9.094208ms
      message: 'load-balancer-api-external: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:05Z"
    - latency: 4.69858ms
      message: 'load-balancer-api-external: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 12.808949ms
      message: 'load-balancer-api-external: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 6.781799ms
      message: 'load-balancer-api-external: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 11.423405ms
      message: 'load-balancer-api-external: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 4.640479ms
      message: 'load-balancer-api-external: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:05Z"
    - latency: 7.925443ms
      message: 'load-balancer-api-external: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:03:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 72d70c1b-180f-48d9-b0c0-76dff7e55291
    resourceVersion: "50320"
    uid: bc67eccb-19be-4b9a-aeb7-3f0a63dc88bd
  spec:
    sourcePod: network-check-source-989f8b8dc-5mqkv
    targetEndpoint: ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:36:05Z"
      message: 'load-balancer-api-internal: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.658274ms
      message: 'load-balancer-api-internal: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:05Z"
    - latency: 2.611421ms
      message: 'load-balancer-api-internal: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:05Z"
    - latency: 4.394874ms
      message: 'load-balancer-api-internal: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:05Z"
    - latency: 91.2µs
      message: 'load-balancer-api-internal: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:05Z"
    - latency: 4.830087ms
      message: 'load-balancer-api-internal: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 4.555352ms
      message: 'load-balancer-api-internal: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 7.308193ms
      message: 'load-balancer-api-internal: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 3.219709ms
      message: 'load-balancer-api-internal: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 3.543836ms
      message: 'load-balancer-api-internal: tcp connection to ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:05Z"
    - latency: 2.530332ms
      message: 'load-balancer-api-internal: resolved host name ac62e67e410bc444e977b99541dde199-2f2af20a0dc725e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:03:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-131-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 72d70c1b-180f-48d9-b0c0-76dff7e55291
    resourceVersion: "48917"
    uid: 0d653715-46a5-47eb-9af1-020c4fc8bd8d
  spec:
    sourcePod: network-check-source-989f8b8dc-5mqkv
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:05Z"
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.346223ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 990.407µs
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 2.404966ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:05Z"
    - latency: 2.299492ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:05Z"
    - latency: 2.201364ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:05Z"
    - latency: 2.14967ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:05Z"
    - latency: 730.27µs
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:05Z"
    - latency: 2.10437ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:05Z"
    - latency: 1.959079ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:05Z"
    - latency: 2.065769ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-136-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 72d70c1b-180f-48d9-b0c0-76dff7e55291
    resourceVersion: "48918"
    uid: 9ef1664f-b86f-4e45-8408-99df06d40027
  spec:
    sourcePod: network-check-source-989f8b8dc-5mqkv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:05Z"
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.352599ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 2.075642ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 860.99µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:05Z"
    - latency: 885.241µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:05Z"
    - latency: 713.773µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:05Z"
    - latency: 1.691609ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:05Z"
    - latency: 1.989582ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:05Z"
    - latency: 1.867893ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:05Z"
    - latency: 2.082485ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:05Z"
    - latency: 681.388µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-140-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 72d70c1b-180f-48d9-b0c0-76dff7e55291
    resourceVersion: "48919"
    uid: 1894efdc-e5e3-4dbc-a46c-477e9efa6399
  spec:
    sourcePod: network-check-source-989f8b8dc-5mqkv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:05Z"
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 627.911µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 1.282377ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 740.86µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:05Z"
    - latency: 1.008057ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:05Z"
    - latency: 742.709µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:05Z"
    - latency: 483.222µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:05Z"
    - latency: 682.158µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:05Z"
    - latency: 502.549µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:05Z"
    - latency: 500.058µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:05Z"
    - latency: 754.949µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 72d70c1b-180f-48d9-b0c0-76dff7e55291
    resourceVersion: "50319"
    uid: 95df3f87-1ecd-4158-b92f-fc14564ca6f9
  spec:
    sourcePod: network-check-source-989f8b8dc-5mqkv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:36:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.3528ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:05Z"
    - latency: 676.24µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:05Z"
    - latency: 1.02703ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:05Z"
    - latency: 583.112µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:05Z"
    - latency: 1.049844ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 595.842µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:05Z"
    - latency: 2.499528ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 832.483µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:05Z"
    - latency: 2.320279ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:05Z"
    - latency: 554.563µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:03:05Z"
kind: List
metadata:
  resourceVersion: ""