apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.ec2.internal
      uid: 5d9d7478-70fd-43a8-a2b4-7a19f89583cd
    resourceVersion: "36549"
    uid: bd74f377-6c73-4efc-9749-f8466254a84f
  spec:
    sourcePod: network-check-source-869dcfcdcd-zn7cd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.791µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 1.120816ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:06Z"
    - latency: 1.087738ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:06Z"
    - latency: 1.396492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:06Z"
    - latency: 1.367587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:06Z"
    - latency: 1.234065ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:06Z"
    - latency: 946.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:06Z"
    - latency: 980.756µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:06Z"
    - latency: 997.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:06Z"
    - latency: 1.149253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.ec2.internal
      uid: 5d9d7478-70fd-43a8-a2b4-7a19f89583cd
    resourceVersion: "38968"
    uid: b670acc0-71a4-49b6-b46d-1249de3eda9e
  spec:
    sourcePod: network-check-source-869dcfcdcd-zn7cd
    targetEndpoint: afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:00:06Z"
      message: 'load-balancer-api-external: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.644263ms
      message: 'load-balancer-api-external: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:18:06Z"
    - latency: 6.490529ms
      message: 'load-balancer-api-external: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:18:06Z"
    - latency: 5.497754ms
      message: 'load-balancer-api-external: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:17:06Z"
    - latency: 8.438936ms
      message: 'load-balancer-api-external: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:17:06Z"
    - latency: 4.243043ms
      message: 'load-balancer-api-external: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:16:06Z"
    - latency: 9.760924ms
      message: 'load-balancer-api-external: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:16:06Z"
    - latency: 5.190361ms
      message: 'load-balancer-api-external: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 8.096582ms
      message: 'load-balancer-api-external: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 7.541481ms
      message: 'load-balancer-api-external: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:06Z"
    - latency: 8.615955ms
      message: 'load-balancer-api-external: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.ec2.internal
      uid: 5d9d7478-70fd-43a8-a2b4-7a19f89583cd
    resourceVersion: "38967"
    uid: b203e5b0-2fb7-4a9c-a3f5-8d5f271b2e2a
  spec:
    sourcePod: network-check-source-869dcfcdcd-zn7cd
    targetEndpoint: afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:00:06Z"
      message: 'load-balancer-api-internal: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.26699ms
      message: 'load-balancer-api-internal: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:18:06Z"
    - latency: 6.55884ms
      message: 'load-balancer-api-internal: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:18:06Z"
    - latency: 5.225909ms
      message: 'load-balancer-api-internal: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:17:06Z"
    - latency: 8.49902ms
      message: 'load-balancer-api-internal: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:17:06Z"
    - latency: 4.253749ms
      message: 'load-balancer-api-internal: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:16:06Z"
    - latency: 9.935058ms
      message: 'load-balancer-api-internal: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:16:06Z"
    - latency: 5.410058ms
      message: 'load-balancer-api-internal: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 8.051995ms
      message: 'load-balancer-api-internal: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 7.589717ms
      message: 'load-balancer-api-internal: tcp connection to afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:06Z"
    - latency: 8.565086ms
      message: 'load-balancer-api-internal: resolved host name afa1ab6cb7aaf49b991000ead03425be-5dcad1c3b2be86e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-ip-10-0-129-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.ec2.internal
      uid: 5d9d7478-70fd-43a8-a2b4-7a19f89583cd
    resourceVersion: "36548"
    uid: 8bf9aa65-8c68-49b1-8f72-6c1b90bde5d1
  spec:
    sourcePod: network-check-source-869dcfcdcd-zn7cd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:06Z"
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.397034ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 2.525987ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:06Z"
    - latency: 2.789951ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:06Z"
    - latency: 2.182801ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:06Z"
    - latency: 2.139754ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:06Z"
    - latency: 2.418641ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:06Z"
    - latency: 2.129857ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:06Z"
    - latency: 2.233581ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:06Z"
    - latency: 2.462421ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:06Z"
    - latency: 2.338956ms
      message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-ip-10-0-134-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.ec2.internal
      uid: 5d9d7478-70fd-43a8-a2b4-7a19f89583cd
    resourceVersion: "36546"
    uid: 079e23fa-a0b7-44c2-8b69-802ad3a2f696
  spec:
    sourcePod: network-check-source-869dcfcdcd-zn7cd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:06Z"
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.199µs
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 1.09282ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:06Z"
    - latency: 1.48051ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:06Z"
    - latency: 1.185746ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:06Z"
    - latency: 1.006299ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:06Z"
    - latency: 937.934µs
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:06Z"
    - latency: 1.064423ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:06Z"
    - latency: 1.038916ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:06Z"
    - latency: 1.404147ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:06Z"
    - latency: 1.194232ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-ip-10-0-134-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.ec2.internal
      uid: 5d9d7478-70fd-43a8-a2b4-7a19f89583cd
    resourceVersion: "36547"
    uid: d4358d9f-25c0-4dda-8403-09321a8fd428
  spec:
    sourcePod: network-check-source-869dcfcdcd-zn7cd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:06Z"
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.0757ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 2.491344ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:06Z"
    - latency: 2.343822ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:06Z"
    - latency: 2.092831ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:06Z"
    - latency: 2.160438ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:06Z"
    - latency: 2.597655ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:06Z"
    - latency: 2.425825ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:06Z"
    - latency: 2.229458ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:06Z"
    - latency: 2.375077ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:06Z"
    - latency: 2.292853ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.ec2.internal
      uid: 5d9d7478-70fd-43a8-a2b4-7a19f89583cd
    resourceVersion: "38966"
    uid: 110195e4-c64c-42f6-8176-0f060bcd2150
  spec:
    sourcePod: network-check-source-869dcfcdcd-zn7cd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:00:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.269139ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:18:06Z"
    - latency: 2.026048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:18:06Z"
    - latency: 900.13µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:17:06Z"
    - latency: 1.838332ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:17:06Z"
    - latency: 946.937µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:16:06Z"
    - latency: 1.705616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:16:06Z"
    - latency: 838.046µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 2.319836ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:15:06Z"
    - latency: 852.899µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:06Z"
    - latency: 1.896861ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:14:06Z"
kind: List
metadata:
  resourceVersion: ""