apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T23:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.ec2.internal
      uid: 883a5db0-8579-4312-af2f-581a82752b25
    resourceVersion: "69352"
    uid: dc6ba13e-f94d-4a19-a458-1e5eedc0c463
  spec:
    sourcePod: network-check-source-6f8b768455-5qpm8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T23:16:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 1.205401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 1.159544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 1.192098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:41:37Z"
    - latency: 1.315707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:40:37Z"
    - latency: 1.464855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:39:37Z"
    - latency: 902.023µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:38:37Z"
    - latency: 945.703µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:37:37Z"
    - latency: 1.218001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:36:37Z"
    - latency: 1.349647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:35:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T23:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.ec2.internal
      uid: 883a5db0-8579-4312-af2f-581a82752b25
    resourceVersion: "70380"
    uid: 9c366e9c-96a5-4a86-9fb3-147297e0793f
  spec:
    sourcePod: network-check-source-6f8b768455-5qpm8
    targetEndpoint: a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T23:15:37Z"
      message: 'load-balancer-api-external: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.255179ms
      message: 'load-balancer-api-external: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:45:37Z"
    - latency: 7.421386ms
      message: 'load-balancer-api-external: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:45:37Z"
    - latency: 5.079276ms
      message: 'load-balancer-api-external: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 11.363954ms
      message: 'load-balancer-api-external: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 4.136883ms
      message: 'load-balancer-api-external: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 7.202354ms
      message: 'load-balancer-api-external: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 3.732589ms
      message: 'load-balancer-api-external: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 6.194847ms
      message: 'load-balancer-api-external: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 4.515782ms
      message: 'load-balancer-api-external: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:41:37Z"
    - latency: 6.792273ms
      message: 'load-balancer-api-external: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:41:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T23:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.ec2.internal
      uid: 883a5db0-8579-4312-af2f-581a82752b25
    resourceVersion: "70381"
    uid: 23d61ff2-12e5-4415-9011-fa4c6dadbbe5
  spec:
    sourcePod: network-check-source-6f8b768455-5qpm8
    targetEndpoint: a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T23:15:37Z"
      message: 'load-balancer-api-internal: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.49759ms
      message: 'load-balancer-api-internal: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:45:37Z"
    - latency: 7.381777ms
      message: 'load-balancer-api-internal: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:45:37Z"
    - latency: 5.657058ms
      message: 'load-balancer-api-internal: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 11.421995ms
      message: 'load-balancer-api-internal: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 4.135011ms
      message: 'load-balancer-api-internal: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 7.17026ms
      message: 'load-balancer-api-internal: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 4.73325ms
      message: 'load-balancer-api-internal: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 6.215253ms
      message: 'load-balancer-api-internal: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 4.321532ms
      message: 'load-balancer-api-internal: tcp connection to a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:41:37Z"
    - latency: 6.68233ms
      message: 'load-balancer-api-internal: resolved host name a3cf4bd5c2d09420689e837e2d6f6726-a0c8bc48f7fbc36c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:41:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T23:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-128-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.ec2.internal
      uid: 883a5db0-8579-4312-af2f-581a82752b25
    resourceVersion: "69349"
    uid: fb2c11a1-f829-4cbc-bd32-0777dcc7b6ce
  spec:
    sourcePod: network-check-source-6f8b768455-5qpm8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T23:16:37Z"
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 847.066µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 871.764µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 797.535µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 851.261µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:41:37Z"
    - latency: 787.82µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:40:37Z"
    - latency: 894.531µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:39:37Z"
    - latency: 993.21µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:38:37Z"
    - latency: 837.464µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:37:37Z"
    - latency: 1.029489ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:36:37Z"
    - latency: 885.789µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:35:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T23:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-134-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.ec2.internal
      uid: 883a5db0-8579-4312-af2f-581a82752b25
    resourceVersion: "69350"
    uid: 2121f017-6158-4aec-8426-4f13f9407356
  spec:
    sourcePod: network-check-source-6f8b768455-5qpm8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T23:16:37Z"
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.851343ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 2.180463ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 1.854746ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 2.192965ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:41:37Z"
    - latency: 1.724954ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:40:37Z"
    - latency: 1.803787ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:39:37Z"
    - latency: 1.691039ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:38:37Z"
    - latency: 1.763297ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:37:37Z"
    - latency: 2.262091ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:36:37Z"
    - latency: 2.306925ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:35:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T23:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-138-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.ec2.internal
      uid: 883a5db0-8579-4312-af2f-581a82752b25
    resourceVersion: "69351"
    uid: 2c9db4f7-ea0d-4a19-ade2-450e53c30bc7
  spec:
    sourcePod: network-check-source-6f8b768455-5qpm8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T23:16:37Z"
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221308ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 2.342945ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 2.362436ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 2.357869ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:41:37Z"
    - latency: 2.012333ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:40:37Z"
    - latency: 2.783655ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:39:37Z"
    - latency: 2.130491ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:38:37Z"
    - latency: 1.834833ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:37:37Z"
    - latency: 2.565592ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:36:37Z"
    - latency: 2.400509ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:35:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T23:09:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.ec2.internal
      uid: 883a5db0-8579-4312-af2f-581a82752b25
    resourceVersion: "70379"
    uid: 7d37549e-a522-4c5f-8ba9-29565147b6f6
  spec:
    sourcePod: network-check-source-6f8b768455-5qpm8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T23:15:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 851.144µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:45:37Z"
    - latency: 1.778777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:45:37Z"
    - latency: 1.272988ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 1.672351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:44:37Z"
    - latency: 1.313985ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 1.728947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:43:37Z"
    - latency: 894.646µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 1.641668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:42:37Z"
    - latency: 1.291577ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T23:41:37Z"
    - latency: 1.893717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T23:41:37Z"
kind: List
metadata:
  resourceVersion: ""