apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-201-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-201.ec2.internal
      uid: b81f007b-0b55-4052-9052-221b37763c02
    resourceVersion: "23606"
    uid: 199397fd-ab5d-47bc-a8fd-6e589ec9837a
  spec:
    sourcePod: network-check-source-7cbc45fddc-ffxmr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:02:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 989.332µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:15:00Z"
    - latency: 1.15139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:14:00Z"
    - latency: 946.199µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:13:00Z"
    - latency: 907.745µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:12:00Z"
    - latency: 1.203631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:11:00Z"
    - latency: 1.015066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:10:00Z"
    - latency: 1.302363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:09:00Z"
    - latency: 992.282µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:08:00Z"
    - latency: 979.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:07:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-201-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-201.ec2.internal
      uid: b81f007b-0b55-4052-9052-221b37763c02
    resourceVersion: "25123"
    uid: 1cd5d7f0-76f1-46a9-8df2-71398122f115
  spec:
    sourcePod: network-check-source-7cbc45fddc-ffxmr
    targetEndpoint: ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:01:00Z"
      message: 'load-balancer-api-external: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.925057ms
      message: 'load-balancer-api-external: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:19:00Z"
    - latency: 9.032179ms
      message: 'load-balancer-api-external: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:19:00Z"
    - latency: 5.123195ms
      message: 'load-balancer-api-external: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:18:00Z"
    - latency: 7.682921ms
      message: 'load-balancer-api-external: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:18:00Z"
    - latency: 4.629202ms
      message: 'load-balancer-api-external: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:17:00Z"
    - latency: 10.182528ms
      message: 'load-balancer-api-external: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:17:00Z"
    - latency: 4.946302ms
      message: 'load-balancer-api-external: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 8.431333ms
      message: 'load-balancer-api-external: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 5.422353ms
      message: 'load-balancer-api-external: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:15:00Z"
    - latency: 13.742851ms
      message: 'load-balancer-api-external: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:15:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-201-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-201.ec2.internal
      uid: b81f007b-0b55-4052-9052-221b37763c02
    resourceVersion: "25124"
    uid: 2f98d12d-ab2f-41b7-b86f-f32c884626f9
  spec:
    sourcePod: network-check-source-7cbc45fddc-ffxmr
    targetEndpoint: ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:01:00Z"
      message: 'load-balancer-api-internal: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.986509ms
      message: 'load-balancer-api-internal: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:19:00Z"
    - latency: 8.975716ms
      message: 'load-balancer-api-internal: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:19:00Z"
    - latency: 5.073607ms
      message: 'load-balancer-api-internal: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:18:00Z"
    - latency: 7.717838ms
      message: 'load-balancer-api-internal: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:18:00Z"
    - latency: 3.57106ms
      message: 'load-balancer-api-internal: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:17:00Z"
    - latency: 10.148389ms
      message: 'load-balancer-api-internal: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:17:00Z"
    - latency: 5.179385ms
      message: 'load-balancer-api-internal: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 8.462768ms
      message: 'load-balancer-api-internal: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 5.418686ms
      message: 'load-balancer-api-internal: tcp connection to ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:15:00Z"
    - latency: 13.81018ms
      message: 'load-balancer-api-internal: resolved host name ae67d2d82bb4848c48768996089ba51d-595c2d5203710ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:15:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-201-to-network-check-target-ip-10-0-131-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-201.ec2.internal
      uid: b81f007b-0b55-4052-9052-221b37763c02
    resourceVersion: "23605"
    uid: 822ccb60-3c01-4947-93fc-47697df8c9c6
  spec:
    sourcePod: network-check-source-7cbc45fddc-ffxmr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:02:00Z"
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.429356ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 2.555566ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:15:00Z"
    - latency: 2.39913ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:14:00Z"
    - latency: 2.369545ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:13:00Z"
    - latency: 2.694943ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:12:00Z"
    - latency: 2.239517ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:11:00Z"
    - latency: 2.366435ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:10:00Z"
    - latency: 2.512575ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:09:00Z"
    - latency: 2.477278ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:08:00Z"
    - latency: 2.721573ms
      message: 'network-check-target-ip-10-0-131-164: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:07:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-201-to-network-check-target-ip-10-0-132-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-201.ec2.internal
      uid: b81f007b-0b55-4052-9052-221b37763c02
    resourceVersion: "23603"
    uid: 9813406f-40ec-4e4a-b415-6bc204d44578
  spec:
    sourcePod: network-check-source-7cbc45fddc-ffxmr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:02:00Z"
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.422µs
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 937.98µs
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:15:00Z"
    - latency: 1.516583ms
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:14:00Z"
    - latency: 1.238287ms
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:13:00Z"
    - latency: 844.187µs
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:12:00Z"
    - latency: 1.455375ms
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:11:00Z"
    - latency: 960.981µs
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:10:00Z"
    - latency: 1.674102ms
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:09:00Z"
    - latency: 882.091µs
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:08:00Z"
    - latency: 1.042607ms
      message: 'network-check-target-ip-10-0-132-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:07:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-201-to-network-check-target-ip-10-0-138-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-201.ec2.internal
      uid: b81f007b-0b55-4052-9052-221b37763c02
    resourceVersion: "23604"
    uid: 73560621-8b9d-415f-84da-040a19086c2b
  spec:
    sourcePod: network-check-source-7cbc45fddc-ffxmr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:02:00Z"
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376077ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 2.170981ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:15:00Z"
    - latency: 2.631147ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:14:00Z"
    - latency: 2.46935ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:13:00Z"
    - latency: 2.356288ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:12:00Z"
    - latency: 2.257397ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:11:00Z"
    - latency: 2.299029ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:10:00Z"
    - latency: 2.607921ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:09:00Z"
    - latency: 2.423218ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:08:00Z"
    - latency: 2.392862ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:07:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-201-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-201.ec2.internal
      uid: b81f007b-0b55-4052-9052-221b37763c02
    resourceVersion: "25122"
    uid: 110fe7fb-c708-4bf3-998e-d2c8a248059d
  spec:
    sourcePod: network-check-source-7cbc45fddc-ffxmr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:01:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:19:00Z"
    - latency: 1.753865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:19:00Z"
    - latency: 876.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:18:00Z"
    - latency: 1.842006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:18:00Z"
    - latency: 962.435µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:17:00Z"
    - latency: 1.790193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:17:00Z"
    - latency: 944.552µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 1.926354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:16:00Z"
    - latency: 1.013408ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:15:00Z"
    - latency: 1.681637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:15:00Z"
kind: List
metadata:
  resourceVersion: ""