apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:16:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-72-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-72.ec2.internal
      uid: ca131390-2e79-4b5a-9ca7-9533c43ae488
    resourceVersion: "17531"
    uid: 91ac5538-f277-4833-a8be-4fb8e001eb88
  spec:
    sourcePod: network-check-source-dbd9cf844-thzms
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:23:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 828.865µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:30:23Z"
    - latency: 921.162µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:29:23Z"
    - latency: 775.14µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:28:23Z"
    - latency: 1.058511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 1.0633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:26:23Z"
    - latency: 686.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 759.155µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:24:23Z"
    - latency: 798.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:23:23Z"
    - latency: 723.247µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:22:23Z"
    - latency: 838.295µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:16:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-72-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-72.ec2.internal
      uid: ca131390-2e79-4b5a-9ca7-9533c43ae488
    resourceVersion: "15467"
    uid: e8d3e562-52a3-4c92-954e-17c97e940e91
  spec:
    sourcePod: network-check-source-dbd9cf844-thzms
    targetEndpoint: a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:22:24Z"
      message: 'load-balancer-api-external: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.805161ms
      message: 'load-balancer-api-external: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:28:24Z"
    - latency: 8.836621ms
      message: 'load-balancer-api-external: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:28:23Z"
    - latency: 5.534629ms
      message: 'load-balancer-api-external: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:27:24Z"
    - latency: 7.498304ms
      message: 'load-balancer-api-external: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 5.559421ms
      message: 'load-balancer-api-external: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:26:24Z"
    - latency: 8.41401ms
      message: 'load-balancer-api-external: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:26:23Z"
    - latency: 3.766085ms
      message: 'load-balancer-api-external: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:25:24Z"
    - latency: 7.717634ms
      message: 'load-balancer-api-external: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 4.541728ms
      message: 'load-balancer-api-external: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:24:24Z"
    - latency: 7.003505ms
      message: 'load-balancer-api-external: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:24:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:16:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-72-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-72.ec2.internal
      uid: ca131390-2e79-4b5a-9ca7-9533c43ae488
    resourceVersion: "15466"
    uid: 4fd997c2-6b38-462f-b178-7c4a0d5dcf20
  spec:
    sourcePod: network-check-source-dbd9cf844-thzms
    targetEndpoint: a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:22:24Z"
      message: 'load-balancer-api-internal: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.73588ms
      message: 'load-balancer-api-internal: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:28:24Z"
    - latency: 8.904486ms
      message: 'load-balancer-api-internal: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:28:23Z"
    - latency: 5.54634ms
      message: 'load-balancer-api-internal: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:27:24Z"
    - latency: 7.568757ms
      message: 'load-balancer-api-internal: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 6.075217ms
      message: 'load-balancer-api-internal: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:26:24Z"
    - latency: 8.574506ms
      message: 'load-balancer-api-internal: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:26:23Z"
    - latency: 6.200325ms
      message: 'load-balancer-api-internal: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:25:24Z"
    - latency: 7.765167ms
      message: 'load-balancer-api-internal: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 5.655364ms
      message: 'load-balancer-api-internal: tcp connection to a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:24:24Z"
    - latency: 7.134331ms
      message: 'load-balancer-api-internal: resolved host name a4640032089b64766849f80f88ba0be6-0c5151aae2eec776.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:24:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:16:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-72-to-network-check-target-ip-10-0-131-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-72.ec2.internal
      uid: ca131390-2e79-4b5a-9ca7-9533c43ae488
    resourceVersion: "17530"
    uid: ae564d01-f2ed-4598-8912-2b7d00d64e66
  spec:
    sourcePod: network-check-source-dbd9cf844-thzms
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:23:24Z"
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.302153ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:30:23Z"
    - latency: 2.121936ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:29:23Z"
    - latency: 2.38329ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:28:23Z"
    - latency: 2.162525ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 2.647893ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:26:23Z"
    - latency: 2.061833ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 1.80417ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:24:23Z"
    - latency: 2.023029ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:23:23Z"
    - latency: 2.337113ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:22:23Z"
    - latency: 2.287453ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:16:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-72-to-network-check-target-ip-10-0-135-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-72.ec2.internal
      uid: ca131390-2e79-4b5a-9ca7-9533c43ae488
    resourceVersion: "17528"
    uid: 64fc8f81-7792-4fb6-9f5e-2ba3eb57f3df
  spec:
    sourcePod: network-check-source-dbd9cf844-thzms
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:23:23Z"
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.204836ms
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:30:23Z"
    - latency: 804.604µs
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:29:23Z"
    - latency: 1.236355ms
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:28:23Z"
    - latency: 888.897µs
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 1.535042ms
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:26:23Z"
    - latency: 940.792µs
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 769.529µs
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:24:23Z"
    - latency: 844.915µs
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:23:23Z"
    - latency: 1.587783ms
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:22:23Z"
    - latency: 1.347801ms
      message: 'network-check-target-ip-10-0-135-72: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:16:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-72-to-network-check-target-ip-10-0-140-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-72.ec2.internal
      uid: ca131390-2e79-4b5a-9ca7-9533c43ae488
    resourceVersion: "17529"
    uid: 08774201-cd8c-4c00-a064-a0bed403f538
  spec:
    sourcePod: network-check-source-dbd9cf844-thzms
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:23:24Z"
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.323562ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:30:23Z"
    - latency: 1.994043ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:29:23Z"
    - latency: 2.21248ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:28:23Z"
    - latency: 2.118313ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 2.226584ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:26:23Z"
    - latency: 1.937057ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 2.102174ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:24:23Z"
    - latency: 2.118498ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:23:23Z"
    - latency: 2.256165ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:22:23Z"
    - latency: 2.214901ms
      message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:16:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-72-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-72.ec2.internal
      uid: ca131390-2e79-4b5a-9ca7-9533c43ae488
    resourceVersion: "15465"
    uid: 3728a161-cd3e-4dc3-87ae-0c6a0906fedb
  spec:
    sourcePod: network-check-source-dbd9cf844-thzms
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:22:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.043942ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:28:24Z"
    - latency: 1.878521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:28:23Z"
    - latency: 1.067249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 1.599738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:27:23Z"
    - latency: 1.094065ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:26:24Z"
    - latency: 2.009868ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:26:23Z"
    - latency: 948.029µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 1.558449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:25:23Z"
    - latency: 888.833µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:24:24Z"
    - latency: 1.819276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:24:23Z"
kind: List
metadata:
  resourceVersion: ""