apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:02:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-91-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-91.ec2.internal
      uid: 0f47f0ed-796b-4782-bf71-6da128f31b1a
    resourceVersion: "31721"
    uid: 38fb4e00-32f2-4fa8-88b4-2c0f8c4cb04a
  spec:
    sourcePod: network-check-source-dbd9cf844-6kz8n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:09:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.053298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:16:46Z"
    - latency: 1.009366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:15:46Z"
    - latency: 1.497842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:14:46Z"
    - latency: 1.160015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:13:46Z"
    - latency: 976.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:12:46Z"
    - latency: 1.154565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:11:46Z"
    - latency: 1.299013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:10:46Z"
    - latency: 1.209102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:09:46Z"
    - latency: 1.109396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:08:46Z"
    - latency: 1.009898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:02:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-91-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-91.ec2.internal
      uid: 0f47f0ed-796b-4782-bf71-6da128f31b1a
    resourceVersion: "35457"
    uid: 4538f9bd-55c3-41be-a005-4a129961b502
  spec:
    sourcePod: network-check-source-dbd9cf844-6kz8n
    targetEndpoint: af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:08:46Z"
      message: 'load-balancer-api-external: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.240948ms
      message: 'load-balancer-api-external: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:20:46Z"
    - latency: 6.856243ms
      message: 'load-balancer-api-external: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:20:46Z"
    - latency: 5.058356ms
      message: 'load-balancer-api-external: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:19:46Z"
    - latency: 6.611031ms
      message: 'load-balancer-api-external: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:19:46Z"
    - latency: 5.193563ms
      message: 'load-balancer-api-external: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:18:46Z"
    - latency: 7.315168ms
      message: 'load-balancer-api-external: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:18:46Z"
    - latency: 3.77552ms
      message: 'load-balancer-api-external: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:17:46Z"
    - latency: 8.065805ms
      message: 'load-balancer-api-external: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:17:46Z"
    - latency: 3.671353ms
      message: 'load-balancer-api-external: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:16:46Z"
    - latency: 7.634607ms
      message: 'load-balancer-api-external: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:16:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:02:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-91-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-91.ec2.internal
      uid: 0f47f0ed-796b-4782-bf71-6da128f31b1a
    resourceVersion: "35458"
    uid: 7cf10fe2-fded-4761-9023-6fbc5f56baa1
  spec:
    sourcePod: network-check-source-dbd9cf844-6kz8n
    targetEndpoint: af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:08:46Z"
      message: 'load-balancer-api-internal: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.768958ms
      message: 'load-balancer-api-internal: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:20:46Z"
    - latency: 6.917469ms
      message: 'load-balancer-api-internal: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:20:46Z"
    - latency: 4.980432ms
      message: 'load-balancer-api-internal: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:19:46Z"
    - latency: 6.600656ms
      message: 'load-balancer-api-internal: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:19:46Z"
    - latency: 5.198294ms
      message: 'load-balancer-api-internal: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:18:46Z"
    - latency: 7.252174ms
      message: 'load-balancer-api-internal: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:18:46Z"
    - latency: 3.704412ms
      message: 'load-balancer-api-internal: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:17:46Z"
    - latency: 8.103479ms
      message: 'load-balancer-api-internal: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:17:46Z"
    - latency: 3.739156ms
      message: 'load-balancer-api-internal: tcp connection to af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:16:46Z"
    - latency: 7.701844ms
      message: 'load-balancer-api-internal: resolved host name af81ff03c7d2140bf80d0d98b90480e4-19e5d5851ffe75fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:16:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:02:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-91-to-network-check-target-ip-10-0-133-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-91.ec2.internal
      uid: 0f47f0ed-796b-4782-bf71-6da128f31b1a
    resourceVersion: "31720"
    uid: 5b435917-de9d-43db-b456-ddf3d0941b8a
  spec:
    sourcePod: network-check-source-dbd9cf844-6kz8n
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:09:46Z"
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.149506ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:16:46Z"
    - latency: 2.421783ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:15:46Z"
    - latency: 2.629505ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:14:46Z"
    - latency: 2.358532ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:13:46Z"
    - latency: 2.67067ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:12:46Z"
    - latency: 2.298164ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:11:46Z"
    - latency: 2.408382ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:10:46Z"
    - latency: 2.194404ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:09:46Z"
    - latency: 2.425799ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:08:46Z"
    - latency: 2.241184ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:02:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-91-to-network-check-target-ip-10-0-139-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-91.ec2.internal
      uid: 0f47f0ed-796b-4782-bf71-6da128f31b1a
    resourceVersion: "31719"
    uid: 2a53e4d6-5b71-40b7-a99a-32a999343ada
  spec:
    sourcePod: network-check-source-dbd9cf844-6kz8n
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:09:46Z"
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.243825ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:16:46Z"
    - latency: 2.38158ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:15:46Z"
    - latency: 2.313761ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:14:46Z"
    - latency: 2.329825ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:13:46Z"
    - latency: 2.264947ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:12:46Z"
    - latency: 2.264758ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:11:46Z"
    - latency: 2.341833ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:10:46Z"
    - latency: 2.180495ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:09:46Z"
    - latency: 2.318097ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:08:46Z"
    - latency: 2.219687ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:02:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-91-to-network-check-target-ip-10-0-141-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-91.ec2.internal
      uid: 0f47f0ed-796b-4782-bf71-6da128f31b1a
    resourceVersion: "31718"
    uid: 80137e84-7b0c-4416-b41e-d741ff4c0acb
  spec:
    sourcePod: network-check-source-dbd9cf844-6kz8n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:09:46Z"
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.039478ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:16:46Z"
    - latency: 951.697µs
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:15:46Z"
    - latency: 1.021087ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:14:46Z"
    - latency: 943.844µs
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:13:46Z"
    - latency: 1.05887ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:12:46Z"
    - latency: 1.024944ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:11:46Z"
    - latency: 1.113006ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:10:46Z"
    - latency: 1.462147ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:09:46Z"
    - latency: 1.79213ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:08:46Z"
    - latency: 1.523661ms
      message: 'network-check-target-ip-10-0-141-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T12:02:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-91-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-91.ec2.internal
      uid: 0f47f0ed-796b-4782-bf71-6da128f31b1a
    resourceVersion: "35456"
    uid: 01abbe8f-fa98-4dad-bbc9-0d44f4fff968
  spec:
    sourcePod: network-check-source-dbd9cf844-6kz8n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T12:08:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.32099ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:20:46Z"
    - latency: 1.760175ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:20:46Z"
    - latency: 894.311µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:19:46Z"
    - latency: 1.793365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:19:46Z"
    - latency: 860.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:18:46Z"
    - latency: 1.869949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:18:46Z"
    - latency: 849.023µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:17:46Z"
    - latency: 1.656959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:17:46Z"
    - latency: 1.337361ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T12:16:46Z"
    - latency: 1.921496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T12:16:46Z"
kind: List
metadata:
  resourceVersion: ""