apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: 64fc14c0-ae29-4fd8-b9a2-cb870e6fe87b
    resourceVersion: "71416"
    uid: 2cb36b30-5686-4673-8176-9207a8a794a4
  spec:
    sourcePod: network-check-source-7d88cb55d8-4dj68
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:14:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.118µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:46Z"
    - latency: 777.941µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 1.102759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 949.802µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 1.282719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 1.049051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:46Z"
    - latency: 1.187796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:50:46Z"
    - latency: 1.153202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:49:46Z"
    - latency: 833.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:48:46Z"
    - latency: 855.957µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:47:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: 64fc14c0-ae29-4fd8-b9a2-cb870e6fe87b
    resourceVersion: "70548"
    uid: 0a46058d-219f-42f9-883f-843087573aea
  spec:
    sourcePod: network-check-source-7d88cb55d8-4dj68
    targetEndpoint: a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:13:46Z"
      message: 'load-balancer-api-external: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.628745ms
      message: 'load-balancer-api-external: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 7.060633ms
      message: 'load-balancer-api-external: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 3.868471ms
      message: 'load-balancer-api-external: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 6.945477ms
      message: 'load-balancer-api-external: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 3.193783ms
      message: 'load-balancer-api-external: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 9.017229ms
      message: 'load-balancer-api-external: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 3.452755ms
      message: 'load-balancer-api-external: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 7.832989ms
      message: 'load-balancer-api-external: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 3.744423ms
      message: 'load-balancer-api-external: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:46Z"
    - latency: 10.439425ms
      message: 'load-balancer-api-external: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:51:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: 64fc14c0-ae29-4fd8-b9a2-cb870e6fe87b
    resourceVersion: "70547"
    uid: 38a514dd-acee-4c57-b269-5af2af2c57d9
  spec:
    sourcePod: network-check-source-7d88cb55d8-4dj68
    targetEndpoint: a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:13:46Z"
      message: 'load-balancer-api-internal: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.098435ms
      message: 'load-balancer-api-internal: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 7.119421ms
      message: 'load-balancer-api-internal: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 3.881435ms
      message: 'load-balancer-api-internal: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 6.932436ms
      message: 'load-balancer-api-internal: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 4.654509ms
      message: 'load-balancer-api-internal: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 9.000542ms
      message: 'load-balancer-api-internal: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 3.296796ms
      message: 'load-balancer-api-internal: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 7.782925ms
      message: 'load-balancer-api-internal: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 3.862651ms
      message: 'load-balancer-api-internal: tcp connection to a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:46Z"
    - latency: 10.217751ms
      message: 'load-balancer-api-internal: resolved host name a0739143a033b41c9a17fb5f30212ba4-e870238e50cda619.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:51:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-ip-10-0-128-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: 64fc14c0-ae29-4fd8-b9a2-cb870e6fe87b
    resourceVersion: "71412"
    uid: e769ef4d-11c6-4b7e-b581-b796b6824913
  spec:
    sourcePod: network-check-source-7d88cb55d8-4dj68
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:14:46Z"
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 786.764µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:46Z"
    - latency: 824.832µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 796.81µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 943.235µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 830.527µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 1.51086ms
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:46Z"
    - latency: 779.512µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:50:46Z"
    - latency: 1.64883ms
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:49:46Z"
    - latency: 919.174µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:48:46Z"
    - latency: 976.197µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:47:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-ip-10-0-142-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: 64fc14c0-ae29-4fd8-b9a2-cb870e6fe87b
    resourceVersion: "71413"
    uid: dcd733e9-ba4e-413f-9615-4d02c9dff90c
  spec:
    sourcePod: network-check-source-7d88cb55d8-4dj68
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:14:46Z"
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.784526ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:46Z"
    - latency: 2.000293ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 1.932001ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 2.203041ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 2.005763ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 2.294931ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:46Z"
    - latency: 2.152496ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:50:46Z"
    - latency: 2.556419ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:49:46Z"
    - latency: 1.819518ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:48:46Z"
    - latency: 2.055348ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:47:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-ip-10-0-143-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: 64fc14c0-ae29-4fd8-b9a2-cb870e6fe87b
    resourceVersion: "71414"
    uid: bf090529-2ce8-4a3a-9a35-c5f17c89d14e
  spec:
    sourcePod: network-check-source-7d88cb55d8-4dj68
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:14:46Z"
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.921539ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:46Z"
    - latency: 2.200804ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 2.243499ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 2.222964ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 2.205012ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 2.163933ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:46Z"
    - latency: 2.558764ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:50:46Z"
    - latency: 2.486956ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:49:46Z"
    - latency: 2.110997ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:48:46Z"
    - latency: 2.219859ms
      message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:47:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: 64fc14c0-ae29-4fd8-b9a2-cb870e6fe87b
    resourceVersion: "70546"
    uid: 5751f7a1-4f91-4a8a-8a61-f0ea75dd6411
  spec:
    sourcePod: network-check-source-7d88cb55d8-4dj68
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:13:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.799µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 1.757585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:55:46Z"
    - latency: 835.721µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 2.095656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:54:46Z"
    - latency: 783.93µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 1.659721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:53:46Z"
    - latency: 831.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 1.603013ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:52:46Z"
    - latency: 1.013866ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:46Z"
    - latency: 2.18062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:51:46Z"
kind: List
metadata:
  resourceVersion: ""